9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] distproto: include the files in /lib/firmware/*
Date: Mon, 08 Mar 2021 17:07:43 +0100	[thread overview]
Message-ID: <ABAAE1A4E3CB7FDD190E40DA09C3BEF2@felloff.net> (raw)
In-Reply-To: <bJrzuFeNSfD-QU-x_BNHksiZjfStxdqwvRaboDJDuqu7ovgKJ4B1GmzJEG4Bi3ujv2ez5onhBtHdMzvfuCt0QGCBumwwQAvCwYwgY2E-vP0=@protonmail.com>

yeah, and with each firmware, the interface and message formats between the
driver and the firmware can completely change. linux solves this with a
gigant message translation layer to the point where it becomes impossible
to understand what exactly it sends to the firmware.

and there is NO DOCUMENTATION for any of this.

while the openbsd (and inspired 9front) driver sticks to a specific firmware
version.

if you want to update the firmware, you also need to revisit the driver
and reverse engineer what linux does with this exact firmware revision
and card.

--
cinap

  parent reply	other threads:[~2021-03-08 16:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 17:02 kemal
2021-03-07 17:20 ` ori
2021-03-07 17:36   ` kemal
2021-03-07 18:20     ` ori
2021-03-07 18:58       ` kemal
2021-03-07 19:11       ` kemal
2021-03-08 10:59         ` kemal
2021-03-08 11:10           ` hiro
2021-03-08 11:58             ` sirjofri
2021-03-08 12:15               ` Sigrid Solveig Haflínudóttir
2021-03-08 12:34                 ` Julien Blanchard
2021-03-08 12:44                 ` kemal
2021-03-08 12:55                   ` hiro
2021-03-08 13:18                     ` kemal
2021-03-08 13:28                       ` hiro
2021-03-08 13:58                         ` kemal
2021-03-08 14:03                           ` hiro
2021-03-08 15:32                     ` Stanley Lieber
2021-03-08 16:07                   ` cinap_lenrek [this message]
2021-03-08 17:58                     ` kemal
2021-03-08 15:29               ` Stanley Lieber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ABAAE1A4E3CB7FDD190E40DA09C3BEF2@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).