From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24403 invoked from network); 8 Mar 2021 16:15:58 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 8 Mar 2021 16:15:58 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 1ess; Mon Mar 8 11:07:53 -0500 2021 Message-ID: Date: Mon, 08 Mar 2021 17:07:43 +0100 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: realtime cloud Subject: Re: [9front] distproto: include the files in /lib/firmware/* Reply-To: 9front@9front.org Precedence: bulk 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