From: "Giacomo A. Catenazzi" <cate@debian.org>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: changes to microcode update driver.
Date: Tue, 07 Oct 2003 15:34:39 +0200 [thread overview]
Message-ID: <3F82C0EF.1040002@debian.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0310070352590.16056-100000@south.veritas.com>
Tigran Aivazian wrote:
> Hi guys,
>
> It's been a long time that I was going to send to Linux the patch with the
> following changes, but the birth of my first child intervened and caused
> delays (though can't call them "unexpected" :). Now, if I hear from people
> "no, no! we are using this feature!" then I will reconsider:
> Please let me know your thoughts.
Hello.
I would like to have a common model to load microcodes (and in the new boot
procedure), but I've lost the status of such project, I think things for 2.7.
Any news?
Is microcode_ctl still maintained? I've made some correction/extentions but now
new from the maintainer.
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?
ciao
giacomo
next prev parent reply other threads:[~2003-10-07 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 10:58 RFC: changes to microcode update driver Tigran Aivazian
2003-10-07 11:02 ` Tigran Aivazian
2003-10-07 13:34 ` Giacomo A. Catenazzi [this message]
2003-10-07 13:48 ` Tigran Aivazian
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
-- strict thread matches above, loose matches on Subject: below --
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=3F82C0EF.1040002@debian.org \
--to=cate@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
/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