From: Chris Rankin <rankincj@yahoo.com>
To: Ben Clifford <benc@hawaga.org.uk>
Cc: tigran@veritas.com, linux-kernel@vger.kernel.org
Subject: Re: Linux IA32 microcode driver
Date: Sat, 22 Dec 2001 17:38:15 -0800 (PST) [thread overview]
Message-ID: <20011223013815.45902.qmail@web13108.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112221050290.9843-100000@barbarella.hawaga.org.uk>
The msr driver doesn't support devfs at all, and nor
does cpuid come to that. However, microcode creates a
miscellaneous character device, number (10,184), in
the /dev/misc directory. This is why the regular
/dev/cpu/microcode file is so mysterious...
Chris
--- Ben Clifford <benc@hawaga.org.uk> wrote:
> On Sat, 22 Dec 2001, Chris Rankin wrote:
>
> > Am I missing something rather obvious, or is the
> /dev/cpu/microcode
> > device being mis-created under devfs with Linux
> 2.4.x? I have enclosed
> > a patch to ensure that the character device really
> *is* a character
> > device.
>
> On my system, running 2.4.16, I get no devfs entry
> for that or msr at all.
> I just get the mtrr entry.
>
> This is with microcode and msr loaded as modules.
>
> --
> Ben Clifford benc@hawaga.org.uk
> http://www.hawaga.org.uk/ben/ GPG: 30F06950
> webcam:
>
http://barbarella.hawaga.org.uk/~benc/webcam/live.html
>
__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
next prev parent reply other threads:[~2001-12-23 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 12:58 Chris Rankin
2001-12-22 18:53 ` Ben Clifford
2001-12-23 1:38 ` Chris Rankin [this message]
2001-12-23 9:34 ` 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=20011223013815.45902.qmail@web13108.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=benc@hawaga.org.uk \
--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
all inboxes | Powered by JetHome®