On Sat, 29 Sep 2012, Eric Valette wrote: > On 29/09/2012 04:11, Henrique de Moraes Holschuh wrote: > >Why should it? It is the kernel's job. An initscript would just slow the > >boot. And the wheezy kernel does its job better when the microcode driver > >is a module. > > I disagree on this sentence. There are kernel modules that do load > firmware automatically when build-in (I have for wifi, dvb tunners). > This is not the case for the microcode driver so you shall not rely > on the fact its or not a module.
Autoload-on-boot support will not be added to the iucode-tool package at this time. Autoloading support IS available through the intel-microcode package, and it does support non-modular microcode, *as long as* you use an initramfs. This is quite throughoutly explained in the README files for intel-microcode. If you don't use an initramfs AND you don't use modular microcode, autoloading will not work out-of-the-box. The packages have enough instructions to let you configure your custom system to autoload the microcode update in their README files, though. -- "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
