From: Tigran Aivazian <tigran@veritas.com>
To: "Giacomo A. Catenazzi" <cate@debian.org>
Cc: linux-kernel@vger.kernel.org, <simon@urbanmyth.org>,
"Nakajima, Jun" <jun.nakajima@intel.com>
Subject: Re: RFC: changes to microcode update driver.
Date: Tue, 7 Oct 2003 06:48:09 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.44.0310070639580.18079-100000@south.veritas.com> (raw)
In-Reply-To: <3F82C0EF.1040002@debian.org>
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
next prev parent reply other threads:[~2003-10-07 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 10:58 Tigran Aivazian
2003-10-07 11:02 ` Tigran Aivazian
2003-10-07 13:34 ` Giacomo A. Catenazzi
2003-10-07 13:48 ` Tigran Aivazian [this message]
2003-10-07 13:54 ` Dave Jones
2003-10-08 8:59 ` Tigran Aivazian
2003-10-08 10:07 ` Mikael Pettersson
2003-10-08 19:43 ` Jamie Lokier
2003-10-07 13:56 Nakajima, Jun
2003-10-07 15:56 ` Maciej Zenczykowski
2003-10-07 16:03 ` Tigran Aivazian
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=Pine.GSO.4.44.0310070639580.18079-100000@south.veritas.com \
--to=tigran@veritas.com \
--cc=cate@debian.org \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@urbanmyth.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®