On Tue, Jul 12, 2016 at 12:13:52PM +0200, Daniel Vetter wrote: > Might be better to just do a request_firmware on driver load, and > simply proceed if it's not there. That is almost never a good idea - if the driver is built-in, then the request_firmware call happens before the real rootfs is mounted, which makes it complicated to get the firmware delivered to the driver. Sure, it works nicely if the drivers are built as modules, but not everyone wants to deal with modules and initramfs images. If we're wanting to just update the firmware, that should be an explicit administrative decision requiring an explicit action by the system administrator, and not done by placing a file in some magic location so that request_firmware() can find it, which then gets picked up at boot time/driver load time. Consider what could happen if linux-firmware picks up the file and places it in the appropriate location by default. -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
