On Fri, May 31, 2013 at 01:26:49AM -0300, Henrique de Moraes Holschuh wrote: > On Thu, 30 May 2013, Jacob Shin wrote: > > mkdir initrd > > cd initrd > > -mkdir kernel > > -mkdir kernel/x86 > > -mkdir kernel/x86/microcode > > -cp ../microcode.bin kernel/x86/microcode/GenuineIntel.bin > > -find .|cpio -oc >../ucode.cpio > > +mkdir -p kernel/x86/microcode > > +cp ../microcode.bin kernel/x86/microcode/GenuineIntel.bin (or > > AuthenticAMD.bin) > > Can I just > 'cat /lib/firmware/amd-ucode/*bin >kernel/x86/microcode/AuthenticAMD.bin' > to get a valid microcode container for all amd processors? > > The answer for Intel is "yes". I sure hope it is the same for AMD...
No, this doesn't work for AMD. The container file includes a header section with information how to map CPU F/M/S to microcode revisions provided with a container file. Concatenating several container files will not create an all-embracing header section. More details were available on the amd64.org web pages. But it seems that the web site is not available anymore ... Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/