On Tue, Jul 09, 2024 at 06:36:08PM GMT, Dragan Simic wrote: > > > > > As I already wrote earlier, and as the above-linked discussions > > > > > conclude, solving these issues doesn't belong to any specific driver. > > > > > It should be resolved within the kernel's firmware loading mechanism > > > > > instead, and no driver should be specific in that regard. > > > > > > > > IT would be good if it can be resolved within the kernel's firmware > > > > loading mechanism. > > > > > > ... we'll need this as a systemic solution. > > > > The general policy has been to put drivers that need a firmware as a > > module, and just never build them statically. > > I totally agree, but if Buildroot builds them statically and provides > no initial ramdisk, we need a better solution than having various drivers > attempt to implement their own workarounds. Buildroot typically allows custom kernel configurations, so it's not really "enforcing" anything like another distro does. It is definitely targetted towards very stripped down systems, so I guess building the drivers statically is a natural choice, but it works fine with modules too. Maxime
Attachment:
signature.asc
Description: PGP signature
