mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tigran Aivazian <tigran@veritas.com>
To: "Giacomo A. Catenazzi" <cate@debian.org>
Cc: Ryan Underwood <nemesis@icequake.net>, <224355@bugs.debian.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: microcode, devfs: Wrong interface change in 2.4.25
Date: Mon, 23 Feb 2004 07:27:48 -0800 (PST)	[thread overview]
Message-ID: <Pine.GSO.4.44.0402230725590.8603-100000@south.veritas.com> (raw)
In-Reply-To: <403A15E5.6010705@debian.org>

Hi Giacomo,

Thank you. Leave it with me and I'll verify what's going on in the
2.4.25 version thereof and correct it.

Kind regards
Tigran

On Mon, 23 Feb 2004, Giacomo A. Catenazzi wrote:

> Hello!
>
>  From the 2.4.25, devfs doesn't create anymore the microcode
> device in /dev/cpu/microcode (as expected from in devices.txt
> and LANANA) but in /dev/misc/microcode. The /dev/cpu/microcode
> path is also hardcoded also in microcode_ctl and distributions
> create only /dev/cpu/microcode.
>
> So last microcode patch (in 2.4.25) is wrong.
> You should add again the /dev/cpu/microcode support in devfs, so
> that the normal and stable interface is maintained (in stable
> kernel serie)
>
> ciao
> 	giacomo
>
>
>
> Ryan Underwood wrote:
>
> > On Mon, Feb 23, 2004 at 09:47:58AM +0100, Giacomo A. Catenazzi wrote:
> >
> >>>What I meant is that the name "/dev/misc/microcode" must be used instead
> >>>of "/dev/cpu/microcode", because the microcode driver in 2.4.25 no
> >>>longer registers with devfs.
> >>
> >>I don't undestand.
> >>Do you say that devfs will register only /dev/misc/microcode ?
> >
> >
> > No, the microcode driver only registers with misc.
> >
> >
> >>So if devfs will register misc/microcode, it is probably
> >>a kernel bug (interface should not change!) or a problem
> >>with LANANA (in this case I should change misc microcode
> >> in drivers, but after an update to 'makedev' package.
> >
> >
> > Examine microcode.c driver diff between 2.4.23 and 2.4.25 in the init
> > function.  The removed code is obvious.
> >
>


  reply	other threads:[~2004-02-23 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Auyi3-0000Up-00@dbz>
     [not found] ` <4039BE3E.5070302@debian.org>
     [not found]   ` <20040223142838.GA26601@dbz.icequake.net>
2004-02-23 15:01     ` Giacomo A. Catenazzi
2004-02-23 15:27       ` Tigran Aivazian [this message]
2004-02-23 17:52         ` [patch-2.4.25] microcode.c fix (wasRe: " Tigran Aivazian
2004-02-24  8:29           ` Giacomo A. Catenazzi

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.0402230725590.8603-100000@south.veritas.com \
    --to=tigran@veritas.com \
    --cc=224355@bugs.debian.org \
    --cc=cate@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nemesis@icequake.net \
    /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®