On Sat, Mar 24, 2012 at 09:17:21PM -0700, H. Peter Anvin wrote:
> The more I think about it the more I really think this is the right
> approach. For microcode, this means we don't have to worry about
> creating a super-container for the various microcode formats; we can
> simply have:
>
> kernel/x86/microcode/GenuineIntel
> kernel/x86/microcode/AuthenticAMD
>
> ... which solves the problem neatly.
Yes, this is actually pretty neat. Basically, distro vendors will get
ucode images from the resp. hw vendors, put them in the proper hierarchy
as above and generate the cpio archive, easy.
> It does beg the question if you want to be able to have multiple:
>
> kernel/acpi/...
>
> ... files, to make managing different tables easier, or is that overkill?
Well, like the above, different sub-namespaces...
--
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
