All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "Daniel J Blueman" <daniel.blueman@gmail.com>
Cc: "Shaohua Li" <shaohua.li@intel.com>,
	jamagallon@ono.com, tigran@aivazian.fsnet.co.uk,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: New format Intel microcode...
Date: 27 Jun 2007 01:29:35 +0200	[thread overview]
Message-ID: <p731wfy5m74.fsf@bingen.suse.de> (raw)
In-Reply-To: <6278d2220706261442u9b137c5xb6225b3f56605554@mail.gmail.com>

"Daniel J Blueman" <daniel.blueman@gmail.com> writes:

> On 23/03/07, Shaohua Li <shaohua.li@intel.com> wrote:
> > On Thu, 2007-03-22 at 23:45 +0000, Daniel J Blueman wrote:
> > > Hi Shao-hua,
> > >
> > > Is the tool you mentioned last June [1] available for splitting up the
> > > old firmware files to the new format (eg
> > > /lib/firmware/intel-ucode/06-0d-06), or are updates available from
> > > Intel (or otherwise) in this new format?
> > Yes, we are preparing the new format data files and maybe put it into a
> > new website. We will announce it when it's ready.
> 
> It's been a while; is there any sign of the ucode updates being
> available, especially in light of the C2D/Q incorrect TLB invalidation
> + recent ucode to fix this?

That microcode update is not needed on any recent Linux kernel; it flushes
the TLBs in a way that is fine.

-Andi

  reply	other threads:[~2007-06-26 22:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 23:45 New format Intel microcode Daniel J Blueman
2007-03-23  0:43 ` Shaohua Li
2007-03-23  9:43   ` Marcel Holtmann
2007-03-23  9:03     ` Arjan van de Ven
2007-03-26  8:34       ` Marcel Holtmann
2007-03-26  8:52         ` Arjan van de Ven
2007-06-26 21:42   ` Daniel J Blueman
2007-06-26 23:29     ` Andi Kleen [this message]
2007-06-28 13:53       ` Bill Davidsen
2007-06-28 14:12         ` Arjan van de Ven
2007-06-28 15:48           ` Alex Riesen
2007-06-28 17:27           ` Chuck Ebbert
2007-06-28 17:29             ` Arjan van de Ven
2007-06-28 17:54             ` Daniel J Blueman
2007-06-28 15:27         ` Andi Kleen
2007-06-28 15:44           ` Chuck Ebbert
2007-06-28 22:55             ` Bill Davidsen
2007-06-28 22:23           ` Bill Davidsen
2007-06-28 22:30             ` Arjan van de Ven
2007-06-28 23:09             ` Andi Kleen
2007-07-02  8:56   ` Alex Riesen
2007-07-02 17:18     ` Arjan van de Ven
2007-07-02 18:22       ` Alex Riesen

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=p731wfy5m74.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=daniel.blueman@gmail.com \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=tigran@aivazian.fsnet.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.