23 Aug
2018
23 Aug
'18
9:20 a.m.
Christian Hesse <list@eworm.de> on Wed, 2018/08/22 11:24:
> Gerardo Exequiel Pozzi via arch-releng <arch-releng@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);}