LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Shaohua Li <shaohua.li@intel.com>,
	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 20:22:05 +0200	[thread overview]
Message-ID: <20070702182205.GA15458@steel.home> (raw)
In-Reply-To: <1183396710.2691.0.camel@laptopd505.fenrus.org>

Arjan van de Ven, Mon, Jul 02, 2007 19:18:29 +0200:
> On Mon, 2007-07-02 at 10:56 +0200, Alex Riesen wrote:
> > 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?
> 
> you can use the old format still as well without any problems...
> 

only with microcode utility. The microcode driver does not load it
through firmware helper.

It is by no means a problem. It's just there is this driver, which
tries to load its firmware, does not find it and complains about it in
logs... Just an annoying message in logs, that's all:

main: error loading '/lib/firmware/intel-ucode/06-09-05' for device \
'/devices/platform/microcode/firmware/microcode' with driver \
'(unknown'

If it does not work, than maybe just remove it? They driver, or maybe
the warning.


      reply	other threads:[~2007-07-02 18:22 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
2007-07-02 17:18     ` Arjan van de Ven
2007-07-02 18:22       ` Alex Riesen [this message]

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=20070702182205.GA15458@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=arjan@infradead.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 \
    --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).