[PATCH] build in microcode driver on x86

[Bill Nottingham]

Dave Jones (davej at redhat.com) said: 
> On Wed, Jan 14, 2009 at 01:17:38PM -0500, Bill Nottingham wrote:
>  > It doesn't really gain anything from being static, aside from requiring
>  > odd udev rules and/or init scripts to load it.
> 
> We had this discussion yesterday on irc, but I never really got this in my head.
> 
> It works ok with microcode.dat, but what happens if Intel release
> an update in /lib/firmware/intel-ucode/$f-$m-$s format ?
> 
> The driver will do a request_firmware, but if we build the driver in,
> we'll be in the initrd, where that file won't exist.
> To make it work, we'll either have to..
> 
> - have the firmware in the initramfs
> 
> or 
> 
> - pretend the request_firmware didn't happen, and have the initscript
>   continue to do the microcode_ctl
> 
> Which direction are we moving in ?

AIUI, the driver's firmware request will get kicked off again when
udev triggers all the normal coldplug events. So, that should be handled
OK.

Bill