[arch-releng] [RFC] [PATCH] [configs/releng] Make and use amd_ucode.bin for initrd.

Christian Hesse list at eworm.de
Thu Aug 23 09:20:21 UTC 2018


Christian Hesse <list at eworm.de> on Wed, 2018/08/22 11:24:
> Gerardo Exequiel Pozzi via arch-releng <arch-releng at archlinux.org> on Sat,
> 2018/08/18 23:29:
> > +# Prepare amd_ucode
> > +make_amd_ucode_img() {
> > +    mkdir -p ${work_dir}/amd-ucode/kernel/x86/microcode
> > +    cat
> > ${work_dir}/x86_64/airootfs/lib/firmware/amd-ucode/microcode_amd*.bin >
> > ${work_dir}/amd-ucode/kernel/x86/microcode/AuthenticAMD.bin
> > +    pushd ${work_dir}/amd-ucode > /dev/null
> > +    echo kernel/x86/microcode/AuthenticAMD.bin | bsdcpio -o -H newc -R
> > 0:0  
> > > amd-ucode.img  
> > +    popd > /dev/null
> > +    cp ${work_dir}/amd-ucode/amd-ucode.img
> > ${work_dir}/x86_64/airootfs/boot/amd-ucode.img +}  
> 
> Wondering if we should put this into a package... Could be a split package
> of linux-firmware. Any opinion on this?

[ Added Laurent to CC as he maintains the linux-firmware package. ]

I've attached a proposal patch to add a split package amd-ucode-early to
linux-firmware. Any objections? Is the name ok or do we prefer just
'amd-ucode'?

And another note... Did anybody test if microcode is updated properly if both,
intel-ucode.img and amd-ucode, are loaded?
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-releng/attachments/20180823/85dae8f1/attachment.sig>


More information about the arch-releng mailing list