From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 00B41138330 for ; Tue, 9 Jan 2018 01:26:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 24E47E081A; Tue, 9 Jan 2018 01:25:39 +0000 (UTC) Received: from mail-oi0-f65.google.com (mail-oi0-f65.google.com [209.85.218.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9BC5FE07AE for ; Tue, 9 Jan 2018 01:25:37 +0000 (UTC) Received: by mail-oi0-f65.google.com with SMTP id e144so4020221oib.4 for ; Mon, 08 Jan 2018 17:25:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=emvKkfASafOrx+it6KkTLssjing8GI46UEubmAi7d+M=; b=Ll7VA8h4xtRlUShWIxkf9oOHwxn/ioG0Iy2NmzjiXILYP+Oqg7MD+8VyqMYzK8vk9e PFfJqthKnW90uKCj3ws0oQUM0viGWZQ4aKs2TNWF2SoR0RtIZfEe/wK1zvQO74MH+s4T JPooo5NiTiCsHUL17bicvOJfc3fYKPH0zVwgFO9yWbAIggogqYqzehtDjJsqyVavRZ5o Npv2FsXXdQNzr/GMkp1mOVeCuOtmJjpmYGwVU27jVhsQsKkUfjWBSpcT7sUNrDqecrN7 q41pTc+mXDKeOGLMtoyVFdcGhOHa4goU8iGryqvFQwy5w9RExcNOzcIeU2/3R97EQe9b n47Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=emvKkfASafOrx+it6KkTLssjing8GI46UEubmAi7d+M=; b=lwzrTZCuq/1E0+gdNqfC/H/F+40tZe54vZiXC4FpmY0FZkv/aw/5gcJvehTdm3xFQb VvoryWNWImqOSTqWnDC37m4YV1D5i8imMg6oyidZ5G53jWvtSEJ9PnWy7GVdWMNe/HLZ C/BkQwWgotRavt4Bn2BWvzMDSm/boQYAU/uCLZ++uj1PF7UdVtG0TfEvFmFcVF4f+2R2 lo9GULfjwUPoKxUuSDwNEnTCBq61sIBCYJu9gkOq3MblSYY+Hi2757uO27FT3hKOYxSO ROqDURXS+89IwlTbY3ZEe4B/O17u90+Wqkelv4BIY5FqEEq1rjuknMDGYD1bE+oe+8cU dZ+w== X-Gm-Message-State: AKwxytcuo7oKK0YRk9sTKJoVlhOfwEIIWoKh4oYUt3G0MAXCr8O+J/ge 1OUAoEpa42wxfoGQ83FDkSfv9meQDozuv6l+y4G6jb82 X-Google-Smtp-Source: ACJfBouTHhTyfhltU2hFxcT7H+MI5r1UR3+1Vt1HBuSTkwgICdcL/PxmxwYs5tVYA8R8SucrnVN+yW7bzrs7NrPoXmw= X-Received: by 10.157.12.221 with SMTP id o29mr7922917otd.191.1515446580172; Mon, 08 Jan 2018 13:23:00 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.157.19.65 with HTTP; Mon, 8 Jan 2018 13:22:59 -0800 (PST) In-Reply-To: <7043537.tTOGm0sStG@peak> References: <7043537.tTOGm0sStG@peak> From: Adam Carter Date: Tue, 9 Jan 2018 08:22:59 +1100 Message-ID: Subject: Re: [gentoo-user] microcode applied? To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="001a1139072c165b0c05624a6700" X-Archives-Salt: 0ee38ff7-e5fc-4d51-8986-bf537255871a X-Archives-Hash: 6fc6db1d3aa969f348eb25551cab732a --001a1139072c165b0c05624a6700 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jan 8, 2018 at 9:14 PM, Peter Humphrey wrote: > On Monday, 8 January 2018 04:55:58 GMT Max Zettlmei=C3=9Fl wrote: > > > You can either use an initrd or build the microcode into your kernel > > image. I prefer the latter. > > I'm confused now. How do you build the microcode into the kernel? The onl= y > place I can see to do that in menuconfig is under Device Drivers; there's > no > such field under Firmware. > Device Drivers -> Generic Driver Options -> Include in-kernel firmware blobs in kernel binary which is CONFIG_FIRMWARE_IN_KERNEL=3Dy --001a1139072c165b0c05624a6700 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On M= on, Jan 8, 2018 at 9:14 PM, Peter Humphrey <peter@prh.myzen.co.uk&= gt; wrote:
On Monday, 8 January 2018 04:55:58 GMT Max Zettlmei=C3= =9Fl wrote:

> You can either use an initrd or build the microcode into your kernel > image. I prefer the latter.

I'm confused now. How do you build the microcode into the kernel= ? The only
place I can see to do that in menuconfig is under Device Drivers; there'= ;s no
such field under Firmware.

Device Drivers -> Generic Driver Options -&g= t; Include in-kernel firmware blobs in kernel binary

which is CONFIG_FIRMWARE_IN_= KERNEL=3Dy

--001a1139072c165b0c05624a6700--