Package: microcode.ctl
Version: 1.17-13
Severity: normal

This would usually be wishlist, but CPU microcode fixes *need* to be
applied as early as possible (preferably by the BIOS itself).

microcode.ctl should:

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.

2. Change the initscript to run *early* (as soon as the required device
is available), even if that means moving microcode to /lib.

3. Verify whether it is needed to supply a udev hook or not.  Depends on
what the kernel driver does during S5-based hibernation, and CPU
hotplug.  If the kernel doesn't retain the last uploaded microcode by
itself, we probably should start using /lib/firmware (which would
actually allow us to simply not bother with initscripts or special udev
scripts anymore).

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32.19 (SMP w/8 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages microcode.ctl depends on:
ii  debconf [debconf-2.0]         1.5.35     Debian configuration management sy
ii  libc6                         2.11.2-2   Embedded GNU C Library: Shared lib
ii  makedev                       2.3.1-89   creates device files in /dev
ii  module-init-tools             3.12-1     tools for managing Linux kernel mo
ii  udev                          160-1      /dev/ and hotplug management daemo

Versions of packages microcode.ctl recommends:
ii  intel-microcode             0.20090927-1 Processor microcode data file for 
ii  wget                        1.12-2       retrieves files from the web

microcode.ctl suggests no packages.

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to