Comment 25 for bug 120434

Brian, the code already supports packaging both the firmware and the actual kernel module separately, provided the firmware ends up in the correct path (generally /lib/firmware) since we're using request_firmware().

Note that it'll just error when loading the module saying the firmware isn't on-disk and point the user to a page on the wiki saying they need to get the microcode.

I imagine the firmware could be uploaded to -restricted or something, while the actual module could be included elsewhere.

Thanks bistory for packaging the 0.11.1 release. :)