2.6.23 /proc/bus/input/devices content question

2.6.23 /proc/bus/input/devices content question

[Michael Guntsche]

Hi,

After upgrading to 2.6.23-rc7 for testing purposes I noticed that the  
contents of /proc/bus/input/devices changed a little bit.

I now have the following entries for my USB-keyboard

....
P: Phys=usb-0000:00:1d.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/input/input2
....

with kernel < 2.6.23 I saw

....
P: Phys=/input0
S: Sysfs=/class/input/input0
....

I this a "wanted" change or should I still see the same with 2.6.23?

Kind regards,
Michael

Re: 2.6.23 /proc/bus/input/devices content question

[Dmitry Torokhov]

Hi Michael,

On 9/25/07, Michael Guntsche <mike@it-loops.com> wrote:
> Hi,
>
> After upgrading to 2.6.23-rc7 for testing purposes I noticed that the
> contents of /proc/bus/input/devices changed a little bit.
>
> I now have the following entries for my USB-keyboard
>
> ....
> P: Phys=usb-0000:00:1d.0-2/input0
> S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/input/input2
> ....
>
> with kernel < 2.6.23 I saw
>
> ....
> P: Phys=/input0
> S: Sysfs=/class/input/input0
> ....
>
> I this a "wanted" change or should I still see the same with 2.6.23?
>

Is this with CONFIG_SYSFS_DEPRECATED=y?

-- 
Dmitry

Re: 2.6.23 /proc/bus/input/devices content question

[Michael Guntsche]

On Sep 25, 2007, at 19:51, Dmitry Torokhov wrote:

> Hi Michael,
>
>> ...
>> I this a "wanted" change or should I still see the same with 2.6.23?
>>
>
> Is this with CONFIG_SYSFS_DEPRECATED=y?

No, CONFIG_SYSFS_DEPRECATED is not set with both kernels. I had a  
closer look and noticed that I for some reason usbhid AND usbkbd were  
loaded.
I removed them both and loaded usbhid again. Now I had two entries  
for my keyboard.

I: Bus=0003 Vendor=08d4 Product=0006 Version=0110
N: Name="Fujitsu Siemens Computers Fujitsu Siemens Computers GmbH USB/ 
PS2 Keyboard v1.1"
P: Phys=usb-0000:00:1d.0-2/input0
S: Sysfs=/class/input/input4
U: Uniq=
H: Handlers=kbd event0
B: EV=120003
B: KEY=e080ffdf 1cfffff ffffffff fffffffe
B: LED=1f

I: Bus=0003 Vendor=08d4 Product=0006 Version=0110
N: Name="Fujitsu Siemens Computers Fujitsu Siemens Computers GmbH USB/ 
PS2 Keyboard v1.1"
P: Phys=usb-0000:00:1d.0-2/input1
S: Sysfs=/class/input/input5
U: Uniq=
H: Handlers=kbd event1
B: EV=3
B: KEY=1078 800c000 1e0000 0 0 0

Notice that Sysfs still shows /class/input...

With 2.6.23-rc7 ONLY usbhid got loaded and I got

I: Bus=0003 Vendor=08d4 Product=0006 Version=0110
N: Name="Fujitsu Siemens Computers Fujitsu Siemens Computers GmbH USB/ 
PS2 Keyboard v1.1"
P: Phys=usb-0000:00:1d.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/input/input4
U: Uniq=
H: Handlers=kbd event2
B: EV=120003
B: KEY=e080ffdf 1cfffff ffffffff fffffffe
B: LED=1f

I: Bus=0003 Vendor=08d4 Product=0006 Version=0110
N: Name="Fujitsu Siemens Computers Fujitsu Siemens Computers GmbH USB/ 
PS2 Keyboard v1.1"
P: Phys=usb-0000:00:1d.0-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.1/input/input5
U: Uniq=
H: Handlers=kbd event3
B: EV=3
B: KEY=1078 800c000 1e0000 0 0 0

So actually Phys is the same, just Sysfs got changed.


Hope that helps,
Michael

Re: 2.6.23 /proc/bus/input/devices content question

[Dmitry Torokhov]

On 9/25/07, Michael Guntsche <mike@it-loops.com> wrote:
>
> On Sep 25, 2007, at 19:51, Dmitry Torokhov wrote:
>
> > Hi Michael,
> >
> >> ...
> >> I this a "wanted" change or should I still see the same with 2.6.23?
> >>
> >
> > Is this with CONFIG_SYSFS_DEPRECATED=y?
>
> No, CONFIG_SYSFS_DEPRECATED is not set with both kernels.

Ok, this is expected. Input devices were converted form class devices
into standard devices. Unless SYSFS_DEPRECTAED is set to Y sysfs
changes are expected.

-- 
Dmitry

Re: 2.6.23 /proc/bus/input/devices content question

[Michael Guntsche]

On Sep 25, 2007, at 22:41, Dmitry Torokhov wrote:

>
> Ok, this is expected. Input devices were converted form class devices
> into standard devices. Unless SYSFS_DEPRECTAED is set to Y sysfs
> changes are expected.
>

Ah ok, so this is a known change. I thought about enabling it for  
testing but did not do it because I did not do it with 2.6.22 either.
Thanks for the clarification Dmitry.

Kind regards,
Michael