mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: microcode_ctl vs udev
Date: Wed, 01 Sep 2004 15:23:27 +0000	[thread overview]
Message-ID: <1094052207l.8632l.0l@werewolf.able.es> (raw)
In-Reply-To: <1093950085.32684.3.camel@localhost.localdomain>


On 2004.08.31, Alan Cox wrote:
> On Llu, 2004-08-30 at 23:50, J.A. Magallon wrote:
> > It looks like udev creates /dev/microcode, but microcode_ctl looks for
> > /dev/cpu/microcode.
> > 
> > Which is the right location ?
> 
> /dev/cpu/microcode according to the LANANA registration table
> 


I solved this with a rule in rules.d:

KERNEL="microcode",     NAME="cpu/microcode" 

But where is the default ? Kernel or userspace ? And why is it not created
in the right place ?

TIA

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.1 (Beta 1) for i586
Linux 2.6.8.1-mm2 (gcc 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) #3







      reply	other threads:[~2004-09-01 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 22:50 J.A. Magallon
2004-08-31 11:01 ` Alan Cox
2004-09-01 15:23   ` J.A. Magallon [this message]

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=1094052207l.8632l.0l@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.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®