RE: RFC: changes to microcode update driver.

From: Nakajima, Jun
Date: Tue Oct 07 2003 - 08:57:33 EST


As Tigran pointed out, we are active in this area too. At this point we
want to add support of the extended update format to the driver, before
we ship the latest microcode data. Some of them require the new format.

Jun
> -----Original Message-----
> From: Tigran Aivazian [mailto:tigran@xxxxxxxxxxx]
> Sent: Tuesday, October 07, 2003 6:48 AM
> To: Giacomo A. Catenazzi
> Cc: linux-kernel@xxxxxxxxxxxxxxx; simon@xxxxxxxxxxxxx; Nakajima, Jun
> Subject: Re: RFC: changes to microcode update driver.
>
> On Tue, 7 Oct 2003, Giacomo A. Catenazzi wrote:
> > Is microcode_ctl still maintained? I've made some
correction/extentions
> but now
> > new from the maintainer.
>
> Yes, I believe Simon is alive and well. (but busy, as we all are)
>
> > Intel give us the new microcode? I had contact with the new
> contact/maintainer/?
> > person in Intel, but still no new microcode since summer 2001. So
maybe
> before
> > changing the driver, could you check the Intel vision about Linux
and
> microcode?
>
> I am communicating with Intel guys from time to time and there are
some
> interesting changes from Intel in the pipeline to update the driver,
but I
> thought it is worthwhile to cleanup and throw away unnecessary bits
before
> applying a major update (otherwise we would be wasting time debugging
an
> update to code which is no longer needed).
>
> As for the microcode data itself, no, I haven't received anything new
from
> Intel yet but please be patient. I have received unofficial latest
> "hacked" version of microcode data from someone (outside Intel) but
it
> will not be uploaded because it will cause support problems both to
Intel
> and myself.
>
> I find it is wiser to be friendly with Intel than to annoy them with
> constant questions "where is the latest microcode data" :)
>
> Kind regards
> Tigran
>
>
>
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/