| View previous topic :: View next topic |
| Author |
Message |
Matteo Azzali
Retired Dev
Joined: 23 Sep 2004
Posts: 1133
|
 Posted: Mon Jul 25, 2005 10:36 am Post subject: Symlinking the event for remote control |
 |
|
Since I use both remote and joypad /joypads,
I would need to simlink my /dev/input/event3 (but event2 sometimes)
in /etc/udev in a way similar to:
| Code: |
KERNEL=="mice", NAME="input/%k", MODE="0644"
KERNEL=="mouse*", NAME="input/%k", MODE="0644"
KERNEL=="event*", NAME="input/%k", MODE="0600"
KERNEL=="js*", NAME="input/%k", MODE="664"
KERNEL=="ts*", NAME="input/%k", MODE="0600"
|
only I would need to know where to get the kernel label
(eg: "mice" or "js*" in the example...)
lspci and lsusb don't help. Do someone knows how to do?
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/ |
|
| Back to top |
|
 |
alkan
Guru
Joined: 06 Aug 2004
Posts: 385
Location: kasimlar yaylasi
|
| Posted: Mon Jul 25, 2005 1:22 pm Post subject: |
|
|
| udev matches those name aagainst /sys filesytem, so hava look at in /sys to figure out what to use. 'man udev' explains it. |
|
| Back to top |
|
|
Matteo Azzali
Retired Dev
Joined: 23 Sep 2004
Posts: 1133
|
| Posted: Tue Jul 26, 2005 12:46 pm Post subject: |
|
|
Sorry this did not helped me. I need a way to inspect/get info on /dev/input/event3 to
get wich kernel name to use in a general way (I'm writing an howto...) and can't use
bus connection . Can't use driver name also, since same driver is applying to my DVB-T
decoder (givin me a total of 5 devices)
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/ |
|
| Back to top |
|
|
alkan
Guru
Joined: 06 Aug 2004
Posts: 385
Location: kasimlar yaylasi
|
| Posted: Tue Jul 26, 2005 2:42 pm Post subject: |
|
|
| There must be some attribute that separates one device from other, like SYSFS in udev for product id, device id, vendor id? |
|
| Back to top |
|
|
Matteo Azzali
Retired Dev
Joined: 23 Sep 2004
Posts: 1133
|
| Posted: Tue Jul 26, 2005 7:39 pm Post subject: |
|
|
I dunno. in /sys folder I only found bus position (eg: xx:yy) info.
The same driver is givin me 4 devices in /dev/dvb/adapter0/
and one device in /dev/input/ (event3 in my case).
The device is generated, I think, by evdev module.
The only infos I found were given by
| Code: |
Bus 001 Device 002: ID 0ccd:0038 TerraTec Electronic GmbH Cinergy T^2 DVB-T Receiver
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0ccd TerraTec Electronic GmbH
idProduct 0x0038 Cinergy T^2 DVB-T Receiver
bcdDevice 1.06
iManufacturer 1 TerraTec GmbH
iProduct 2 Cinergy T²
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 476mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 3 Highspeed Bulk Transfer
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
|
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/ |
|
| Back to top |
|
|
Matteo Azzali
Retired Dev
Joined: 23 Sep 2004
Posts: 1133
|
| Posted: Tue Jul 26, 2005 9:58 pm Post subject: |
|
|
ouch... discovered the issue :
Following this howto for udev rules
| Code: | +udevinfo -a -p $(udevinfo -q path -n /dev/input/event3)
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
device '/sys/class/input/event3' has major:minor 13:67
looking at class device '/sys/class/input/event3':
SUBSYSTEM=="input"
SYSFS{dev}=="13:67"
|
It stops here cause there is'nt device-link to physical device.
Cannot create a rule for udev 
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/ |
|
| Back to top |
|
|
|
Kernel & Hardware
