From: "Jo l'Indien" <l_indien@magic.fr>
To: tigran@sco.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: A little patch for i386/kernel/microcode.c
Date: Wed, 24 Jan 2001 06:28:35 +0100 [thread overview]
Message-ID: <3A6E6803.943E7033@magic.fr> (raw)
With a 2.4.1-pre10 kernel, I noticed that /dev/cpu/microcode
was created as a file, and note as a node in the devfs.
So, I made this very little patch to correct this:
--- microcode.c Thu Dec 28 06:28:29 2000
+++ microcode.c Wed Jan 24 04:47:08 2001
@@ -120,7 +120,7 @@
MICROCODE_MINOR);
devfs_handle = devfs_register(NULL, "cpu/microcode",
- DEVFS_FL_DEFAULT, 0, 0, S_IFREG | S_IRUSR | S_IWUSR,
+ DEVFS_FL_DEFAULT, MISC_MAJOR, MICROCODE_MINOR, S_IFCHR | S_IRUSR |
S_IWUSR,
µcode_fops, NULL);
if (devfs_handle == NULL && error) {
printk(KERN_ERR "microcode: failed to devfs_register()\n");
This should be OK...
I cannot test this feature as I don't have a PIII,
but a K6-II... I'll try... Just to know...
I was wondering why /dev/cpu/mtrr was created as a file, not a node,
when I found this... For mtrr, it seems to be normal, as I didn't find
any informations relative of Major/Minor for this device...
Regards.
Jocelyn Mayer
ý:.˱Êâmçë¢kaÉb²ßìzwm
ébïî˱Êâmébìÿêçz_âØ^nr¡ö¦zË\x1aëh¨èÚ&£ûàz¿äz¹Þú+ù^jÇ«y§m
á@A«a¶Úÿÿü0ÃûnÇú+ùd
reply other threads:[~2001-01-24 5:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A6E6803.943E7033@magic.fr \
--to=l_indien@magic.fr \
--cc=jma@netgem.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@sco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.