LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Shaohua Li" <shaohua.li@intel.com>
Cc: "Daniel J Blueman" <daniel.blueman@gmail.com>,
jamagallon@ono.com, tigran@aivazian.fsnet.co.uk,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: New format Intel microcode...
Date: Mon, 2 Jul 2007 10:56:04 +0200 [thread overview]
Message-ID: <81b0412b0707020156q2dedde7fw6c46e8d626ed34a7@mail.gmail.com> (raw)
In-Reply-To: <1174610594.6598.3.camel@sli10-conroe.sh.intel.com>
On 3/23/07, Shaohua Li <shaohua.li@intel.com> wrote:
> On Thu, 2007-03-22 at 23:45 +0000, Daniel J Blueman wrote:
> > 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.
Well, is it ready yet?
next prev parent reply other threads:[~2007-07-02 8:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 23:45 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
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 [this message]
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=81b0412b0707020156q2dedde7fw6c46e8d626ed34a7@mail.gmail.com \
--to=raa.lkml@gmail.com \
--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 \
--subject='Re: New format Intel microcode...' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).