Re: 2.6.14-rc4-mm1: udev/sysfs wierdness

["Mathieu Segaud" <matt@regala.cx>]

Greg KH <greg@kroah.com> disait dernièrement que :

> On Mon, Oct 17, 2005 at 10:50:03PM -0700, Greg KH wrote:
>> On Mon, Oct 17, 2005 at 09:35:13PM -0700, Aaron Gyes wrote:
>> > For some reason this rule stopped working:
>> > 
>> > KERNEL=="event*", SYSFS{manufacturer}="Logitech", SYSFS{product}="USB
>> > Receiver", NAME="input/mx1000", MODE="0644"
>> > 
>> > Did stuff in /sys/ change? Do I need to change all my rules to make up
>> > for this? udevs fault? I do have the correct /dev/input/event0 node.
>> 
>> You have that node?  That's a good start :)
>> 
>> I think the "name" might have changed, it looks like I messed that up
>> somehow.  What does:
>> 	 udevinfo -p /sys/class/input/input0/event0/ -a
>> 
>> show (or whatever that sysfs path is.)
>> 
>> Oops, heh, that dies on my box too.  Ok, I think that's the issue,
>> sorry.  I'm working on it...
>
> Can you try the patch below to see if that fixes the issue?  That should
> keep udevinfo from dieing.

huh, it doesn't apply to 2.6.14-rc4-mm1....
for which tree is it exactly ?

patching file drivers/input/input.c
Hunk #1 succeeded at 641 (offset 119 lines).
Hunk #2 FAILED at 818.
Hunk #3 succeeded at 769 (offset 33 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/input/input.c.rej

best regards,

-- 
Mathieu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/