From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] linux: enable MICROCODE_INTEL if intel-microcode is selected
Date: Sun, 4 Nov 2018 19:02:38 -0200 [thread overview]
Message-ID: <20181104210241.20237-2-casantos@datacom.com.br> (raw)
In-Reply-To: <20181104210241.20237-1-casantos@datacom.com.br>
We already turn on kernel features for several packages, so let's do it
for intel-microcode too, otherwise it's impossible to load the microcode
(by means of iucode-tools).
Signed-off-by: Carlos Santos <casantos@datacom.com.br>
---
linux/linux.mk | 3 +++
1 file changed, 3 insertions(+)
diff --git a/linux/linux.mk b/linux/linux.mk
index 476ff16329..b0cdbe933d 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -323,6 +323,9 @@ define LINUX_KCONFIG_FIXUP_CMDS
$(if $(BR2_PACKAGE_AUDIT),
$(call KCONFIG_ENABLE_OPT,CONFIG_NET,$(@D)/.config)
$(call KCONFIG_ENABLE_OPT,CONFIG_AUDIT,$(@D)/.config))
+ $(if $(BR2_PACKAGE_INTEL_MICROCODE),
+ $(call KCONFIG_ENABLE_OPT,CONFIG_MICROCODE,$(@D)/.config)
+ $(call KCONFIG_ENABLE_OPT,CONFIG_MICROCODE_INTEL,$(@D)/.config))
$(if $(BR2_PACKAGE_KTAP),
$(call KCONFIG_ENABLE_OPT,CONFIG_DEBUG_FS,$(@D)/.config)
$(call KCONFIG_ENABLE_OPT,CONFIG_ENABLE_DEFAULT_TRACERS,$(@D)/.config)
--
2.17.1
next prev parent 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 [Buildroot] [PATCH 0/4] update/improve intel-microcode and iucode-tool Carlos Santos
2018-11-04 21:02 ` Carlos Santos [this message]
2018-11-12 21:37 ` [Buildroot] [PATCH 1/4] linux: enable MICROCODE_INTEL if intel-microcode is selected 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-2-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