microcode, devfs: Wrong interface change in 2.4.25
From: Giacomo A. Catenazzi
Date: Mon Feb 23 2004 - 10:03:13 EST
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/