Date: Mon, 27 Jan 2025 08:50:03 -0800 From: Mark Millard <marklmi@yahoo.com> To: Adrian Chadd <adrian@freebsd.org>, Emmanuel Vadot <manu@freebsd.org> Cc: Stefan Esser <se@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: "don't know how to make /usr/main-src/sys/contrib/dev/iwm/iwm-3160-17.fw.uu. Stop" Message-ID: <B6C9EEA6-7EB4-4C19-AA19-76C76A0E721A@yahoo.com> In-Reply-To: <CAJ-VmomNZ9dLE2XxYz9z_2AjGMDWBB0BVq%2BCr8MvvhxS=RJ0Kw@mail.gmail.com> References: <CD107BA5-1168-4A75-9323-9A4B7E90825E@yahoo.com> <978176f7-270c-4603-b80a-e29c3b1b4b73@FreeBSD.org> <4FC807EC-10DD-49FD-AACE-9026B4925923@yahoo.com> <1B14894C-78E3-4696-9E4F-FBA97A356BF1@yahoo.com> <CAJ-VmomNZ9dLE2XxYz9z_2AjGMDWBB0BVq%2BCr8MvvhxS=RJ0Kw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Jan 26, 2025, at 20:51, Adrian Chadd <adrian@freebsd.org> wrote: > Hi! Hello. > So, there's no longer a build target for the firmware uuencoded files -> kernel module. Yea. But there are the sys/conf/files dependency lines in main that still list .fw.uu files. That includes a reference related to the error I get in my context unless I avoid "device iwmfw" in the kernel configuration: /. . ./sys/conf/files: dependency "$S/contrib/dev/iwm/iwm-3160-17.fw.uu" \ It makes things look like the .fw.uu removal activity is still incomplete. > Being able to build iwm in the kernel rather than a module is broken. > > Now, the real issue(s) are that iwm needs firmware to initialise, and the firmware needs to exist, and thus it needs access to the rootfs for firmware_get() to find the now binary files in /boot/firmware instead of the kernel module old way, and that whole pipeline is broken if it's loaded at boot time or included in the kernel directly. There isn't a nice way to defer the firmware load attempt until /after/ rootfs is up. > Yep. === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B6C9EEA6-7EB4-4C19-AA19-76C76A0E721A>