Subject: RE: Loading Pentium III microcode under Linux - catch 22!
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Tigran Aivazian <tigran@veritas.com>, Chris Rankin <rankincj@yahoo.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <7F740D512C7C1046AB53446D3720017304AE75@scsmsx402.sc.intel.com>
References: <7F740D512C7C1046AB53446D3720017304AE75@scsmsx402.sc.intel.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1074020440.30531.13.camel@dhcp23.swansea.linux.org.uk>
Mime-Version: 1.0
Date: Tue, 13 Jan 2004 19:00:41 +0000
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 727
Lines: 16

On Iau, 2003-08-07 at 18:40, Nakajima, Jun wrote:
> One issue with doing it in lilo or grub is that we need to apply
> microcode update to each (physical) CPU. So we need to change the
> current driver structure if we want to move it to the boot loader.

Not really. The boot loader loads the kernel and initrd image and runs
the kernel. The initrd is a file system which can contain things like
the microcode loader and the microcode sets, just like it can contain
anything else.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/