It seems now the updates of the microcode are distributed separately from the updates to the microcode loader code. My proposal is to either split the package into e.g. microcode-ctl and microcode-data, or overload the current 1.17 version with -rx, to distribute the latest microcode update (September 2007)
Created attachment 132298 [details] microcode-ctl-1.17.ebuild Easiest method.
(In reply to comment #1) > Created an attachment (id=132298) [edit] > microcode-ctl-1.17.ebuild > > Easiest method. > this would require user-interaction to get the latest microcode ... imho it would be best to use the -rx way!
splitting the ebuilds are fine ... but we'll need a microcode-data ebuild to handle the new intel setup
Created attachment 150775 [details, diff] ebuild for sys-apps/microcode-data-20080401.ebuild (latest at this time) This ebuild blocks <microcode-ctl-1.17-r1, because older versions of microcode-ctl will collide with a file provided by microcode-data. patch for microcode-ctl ebuild will follow. Note: the URI for the microcode itself contains what appears to be the arbitrary number "14303". I've had no trouble using this path from different machines, but I don't know if that component of the path might change with future releases. Though I don't see anything on intel.com indicating that users are required to download manually, there's a possibility that this arbitrary number does rotate between releases. I hope not, but if it does, this ebuild would require a fetch restriction so that users are forced to locate the file manually.
Created attachment 150777 [details, diff] patch from microcode-ctl-1.17.ebuild to microcode-ctl-1.17-r1.ebuild This patches microcode-ctl-1.17.ebuild to work with (and require) the microcode-data ebuild above. It must be revbumped to at least 1.17-r1 in order to satisy the blocker contained in the microcode-data ebuild. Note that there are no changes to the contents of FILESDIR.
Created attachment 150778 [details] Modified version of previous that just adds a pkg_postinst It occurred to me that we should let users know when new microcode has been installed, so I added a pkg_postinst to do that. My "Note" from the original version of this ebuild still applies.
Yes, sorry, to be clear - comment #6 is a modifed microcode-data-20080401.ebuild.
Created attachment 150780 [details, diff] Fixed microcode-ctl-1.17-r1.ebuild.diff And I also realized I flubbed up the previous patch to microcode-ctl-1.17-r1.ebuild (no copy-and-pasting diffs! Bad user!). This one is corrected. All notes from comment #5 still apply.
thanks, things should be added to the tree now
