On Wed, Feb 15, 2017 at 12:28:42PM +0200, Jani Nikula wrote: > On Tue, 14 Feb 2017, Seth Forshee <seth.forshee@xxxxxxxxxxxxx> wrote: > > Hi, > > > > I've noted that kbl_guc_ver9_14.bin and bxt_guc_ver8_7.bin are not in > > linux-firmware despite being available here: > > > > https://01.org/linuxgraphics/downloads/firmware > > > > Is there some reason they haven't been pusehd out to linux-firmware, > > e.g. are they not yet stable or something like that? Any reason we > > shouldn't ship those files in Ubuntu's linux-firmware? > > None that I know of. Rodrigo, please send the pull request to > linux-firmware if you haven't already. > > > Frankly, the practice of adding MODULE_FIRMWARE statements to i915 for > > files which aren't in linux-firmware has become a significant annoyance > > to me as Ubuntu's linux-firmware package maintainer. I'm getting a > > steady stream of bug reports from users about the "Possible missing > > firmware ..." messages from mkinitramfs, to the point that I've started > > removing the MODULE_FIRMWARE statements for those files from our > > kernels. > > Admittedly we've probably done that even before the firmware has hit > 01.org, and we should fix this. We don't have a long history of dealing > with firmware blobs, and your feedback is appreciated. > > I think my main question is, what are the downsides of requesting a > firmware even if it hasn't been declared using a MODULE_FIRMWARE > statement? I don't see anything preventing that. Is MODULE_FIRMWARE > purely informational, to help ensure the packaging gets it right? > > We do need to have the firmware loading code in place long before we > actually publish the firmware, to test the stuff. Could we get away with > adding the MODULE_FIRMWARE statements only after the blobs have hit > linux-firmware? The only downside I know of is this. mkinitramfs uses the modinfo firmware field to copy firmware into the initrd along with the kernel module, so when i915.ko is copied to the initrd that firmware would not be copied along with it. There may be other tools using that modinfo field that I'm not aware of though. Maybe it would be good to have something like MODULE_OPTIONAL_FIRMWARE to identify firmware that isn't required but will be used by the driver if available. Then mkinitramfs can try to copy those files along with the module but know that there's no need to produce a warning if it's not present. Thanks, Seth _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
