http://lwn.net/Articles/284104/ This is a special feed containing comments posted to the individual LWN article titled "Using the firmware loader for static data". hourly 2 http://lwn.net/Articles/284462/rss 2008-05-29T21:49:20+00:00 vonbrand <p> I'd prefer to have filesystem data (if available) take precedence; or, at least, be able to tell the kernel not to load the builtin stuff. Just for sanity, so if the firmware gets corrupted or I want to try a new version a full new kernel isn't required. http://lwn.net/Articles/284309/rss 2008-05-29T12:28:38+00:00 rvfh <p><i>In those cases, though, both the compressed and uncompressed data will be in memory while the driver is downloading it.</i></p> <p>Well, not really: you only need a buffer for the decompression mechanism, the size of which does not need to be big (not as big as todays firmwares at least!).</p> http://lwn.net/Articles/284282/rss 2008-05-29T09:19:44+00:00 dwmw2 I think I've decided to kill off <TT>DECLARE_BUILTIN_FIRMWARE</TT>.<P>Instead, we're shifting the firmware blobs to ihex files in the <TT>firmware/</TT> subdirectory. Having them standalone means that we can also have a '<TT>make firmware_install</TT>' target which puts the same firmware files into <TT>/lib/firmware</TT> where udev can find them.<P> With <TT>DECLARE_BUILTIN_FIRMWARE</TT> that wasn't feasible -- we could <em>only</em> build it in, and didn't easily have the option to have it loaded by userspace.