From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] update/improve intel-microcode and iucode-tool
Date: Sun, 4 Nov 2018 19:02:37 -0200 [thread overview]
Message-ID: <20181104210241.20237-1-casantos@datacom.com.br> (raw)
Patch 1 enables MICROCODE_INTEL if intel-microcode is selected, since
otherwise it's impossible to load microcode (by means of iucode-tools).
Patch 2 updates intel-microcode to the latest version and moves its
installation path from /usr/share/misc/ to /lib/firmware/, along with
the files installed by linux-firmware. That path is also used by other
Linux distros (e.g. Ubuntu). Notice that the package now installs 100
binary files under /lib/firmware/intel-ucode/ instead of a big text file
at /usr/share/misc/intel-microcode.dat.
Patch 3 updates iucode-tool to the latest version.
Patch 4 updates the iucode-tool init script. That's what I was doing
initially. All other patches are just a consequence ot the "plucking a
feather brings a hen" effect.
Patches 1, 2 and 3 can be applied in any order (I tested this) but patch
4 is on top of patch 2.
Carlos Santos (4):
linux: enable MICROCODE_INTEL if intel-microcode is selected
intel-microcode: bump to version 20180807a
iucode-tool: bump to version 2.3.1
iucode-tool: rewrite init script
linux/linux.mk | 3 ++
package/intel-microcode/intel-microcode.hash | 4 +-
package/intel-microcode/intel-microcode.mk | 16 +++-----
package/iucode-tool/S00iucode-tool | 39 ++++++++++++--------
package/iucode-tool/iucode-tool.hash | 2 +-
package/iucode-tool/iucode-tool.mk | 2 +-
6 files changed, 36 insertions(+), 30 deletions(-)
--
2.17.1
next reply other threads:[~2018-11-04 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 21:02 Carlos Santos [this message]
2018-11-04 21:02 ` [Buildroot] [PATCH 1/4] linux: enable MICROCODE_INTEL if intel-microcode is selected Carlos Santos
2018-11-12 21:37 ` Peter Korsgaard
2018-11-04 21:02 ` [Buildroot] [PATCH 2/4] intel-microcode: bump to version 20180807a Carlos Santos
2018-11-12 21:39 ` Peter Korsgaard
2018-11-04 21:02 ` [Buildroot] [PATCH 3/4] iucode-tool: bump to version 2.3.1 Carlos Santos
2018-11-12 21:39 ` Peter Korsgaard
2018-11-04 21:02 ` [Buildroot] [PATCH 4/4] iucode-tool: rewrite init script Carlos Santos
2018-11-12 21:47 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181104210241.20237-1-casantos@datacom.com.br \
--to=casantos@datacom.com.br \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox