On Sat, 21 Aug 2010, Henrique de Moraes Holschuh wrote: > 1. Provide facilities to upload microcode from the initrd. Since a big > initrd is annoying, it should retain in the initrd only the microcode > for the CPU update-initramfs was run in. The root filesystem boot > process can try to reapply microcode updates to cover the CPU upgrade > scenario.
This has been addressed by the amd64-microcode (>= 1) and intel-microcode (>= 1) uploads, currently in unstable. microcode.ctl is going to be deprecated (unless upstream decides to change it to do something like what iucode-tool does). cpu-upgrade scenarios are not handled automatically by default. > 2. Change the initscript to run *early* (as soon as the required device > is available), even if that means moving microcode to /lib. Addressed by the new intel-microcode/amd64-microcode and /etc/modules (really!), doesn't require an initscript anymore. > 3. Verify whether it is needed to supply a udev hook or not. Depends on The answer is "no". -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
