[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20070702182205.GA15458@steel.home>
Date: Mon, 2 Jul 2007 20:22:05 +0200
From: Alex Riesen <raa.lkml@...il.com>
To: Arjan van de Ven <arjan@...radead.org>
Cc: Shaohua Li <shaohua.li@...el.com>,
Daniel J Blueman <daniel.blueman@...il.com>,
jamagallon@....com, tigran@...azian.fsnet.co.uk,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: New format Intel microcode...
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@...el.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists