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>
Subject: RE: Loading Pentium III microcode under Linux - catch 22!
Date: Tue, 13 Jan 2004 19:00:41 +0000 [thread overview]
Message-ID: <1074020440.30531.13.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017304AE75@scsmsx402.sc.intel.com>
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.
next prev parent reply other threads:[~2004-01-13 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 17:40 Nakajima, Jun
2003-08-09 19:28 ` Loading Pentium III microcode under Linux - catch 22! BOARD NOW STABLE! Chris Rankin
2004-01-13 19:00 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-07 12:28 Loading Pentium III microcode under Linux - catch 22! Chris Rankin
2003-08-07 13:04 ` Måns Rullgård
2003-08-07 13:58 ` Alan Cox
2003-08-07 14:38 ` Chris Rankin
2003-08-07 14:53 ` Alan Cox
2003-08-07 15:21 ` Tomas Szepe
2003-08-07 15:41 ` Chris Rankin
2003-08-07 23:12 ` Eyal Lebedinsky
2003-08-07 15:57 ` Tigran Aivazian
2003-08-07 15:55 ` Alan Cox
2003-08-08 8:24 ` Chris Rankin
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=1074020440.30531.13.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rankincj@yahoo.com \
--cc=tigran@veritas.com \
/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
all inboxes | Powered by JetHome®