Re: [opensuse-factory] Wanted: Correct power-switch for ARM based Chromebook
Hi, just to be noted, that is not required to boot with openSUSE. Any nmodern Linux is enough, that is that there should be is the /sys file system and the filled /dev/input/ directory. I'd like to know the output of for n in /dev/input/event*; do udevadm info -a --name=$n done then we might catch the input device for gpio-keys.8 and the power switch therein. Werner
Le 01/10/2014 14:35, Andreas Färber a écrit :
Hi, Let's CC opensuse-arm for such ARM questions... Am 30.09.2014 um 09:29 schrieb Dr. Werner Fink:
Hi, just to be noted that the patch rules-add-lid-switch-of-ARM-based-Chromebook-as-a-power-sw.patch which includes the line SUBSYSTEM=="input", KERNEL=="event*", KERNELS=="gpio-keys.8", TAG+="power-switch" in the 70-power-switch.rules can not be fully corect. This because the "gpio-keys.8" is much to general and may cause trouble with other keyboard layouts. Therefore I'd like to see the output of such a Chromebook of the command: udevadm info -a /dev/input/by-path/*kbd which may give the more specific name of the power button.
Werner
Alex? Guillaume? Can any of you provide the requested information for the Samsung Chromebook?
From Chrome OS (kernel 3.8.11), "udevadm info -a --name=/dev/input/by-path/*kbd" returns: ********************************************************************** Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device.
looking at device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0/event0': KERNEL=="event0" SUBSYSTEM=="input" DRIVER==""
looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0': KERNELS=="input0" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="cros-ec-i2c" ATTRS{phys}=="i2c-4-mux (chan_id 0)" ATTRS{uniq}=="" ATTRS{properties}=="0"
looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3': KERNELS=="cros-ec-keyb.3" SUBSYSTEMS=="platform" DRIVERS=="cros-ec-keyb"
looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e': KERNELS=="104-001e" SUBSYSTEMS=="i2c" DRIVERS=="cros-ec-i2c" ATTRS{name}=="cros-ec-i2c"
looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104': KERNELS=="i2c-104" SUBSYSTEMS=="i2c" DRIVERS=="" ATTRS{name}=="i2c-4-mux (chan_id 0)"
looking at parent device '/devices/12ca0000.i2c/i2c-4': KERNELS=="i2c-4" SUBSYSTEMS=="i2c" DRIVERS=="" ATTRS{name}=="s3c2410-i2c"
looking at parent device '/devices/12ca0000.i2c': KERNELS=="12ca0000.i2c" SUBSYSTEMS=="platform" DRIVERS=="s3c-i2c" **********************************************************************
My openSUSE SD card is currently broken, so I cannot test under openSUSE.
Independent of the exact GPIO key, the term "ARM based Chromebook" in the subject and patch name seems to be rather broad given that there's the original Samsung Chromebook, plus the HP Chromebook 11, plus an Acer Chromebook based on Tegra, plus some based on Rockchip, etc. which likely all use different GPIO configurations.
Mine is a Samsung Chromebook.
Guillaume
-- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
Le 02/10/2014 12:47, Dr. Werner Fink a écrit :
Hi,
just to be noted, that is not required to boot with openSUSE. Any nmodern Linux is enough, that is that there should be is the /sys file system and the filled /dev/input/ directory.
I'd like to know the output of
for n in /dev/input/event*; do udevadm info -a --name=$n done
then we might catch the input device for gpio-keys.8 and the power switch therein.
Here are the results (from ChromeOS): Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0/event0': KERNEL=="event0" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0': KERNELS=="input0" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="cros-ec-i2c" ATTRS{phys}=="i2c-4-mux (chan_id 0)" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3': KERNELS=="cros-ec-keyb.3" SUBSYSTEMS=="platform" DRIVERS=="cros-ec-keyb" looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e': KERNELS=="104-001e" SUBSYSTEMS=="i2c" DRIVERS=="cros-ec-i2c" ATTRS{name}=="cros-ec-i2c" looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104': KERNELS=="i2c-104" SUBSYSTEMS=="i2c" DRIVERS=="" ATTRS{name}=="i2c-4-mux (chan_id 0)" looking at parent device '/devices/12ca0000.i2c/i2c-4': KERNELS=="i2c-4" SUBSYSTEMS=="i2c" DRIVERS=="" ATTRS{name}=="s3c2410-i2c" looking at parent device '/devices/12ca0000.i2c': KERNELS=="12ca0000.i2c" SUBSYSTEMS=="platform" DRIVERS=="s3c-i2c" Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/12c70000.i2c/i2c-1/1-0067/input/input1/event1': KERNEL=="event1" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/12c70000.i2c/i2c-1/1-0067/input/input1': KERNELS=="input1" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="Cypress APA Trackpad (cyapa)" ATTRS{phys}=="i2c-1-0067/input0" ATTRS{uniq}=="" ATTRS{properties}=="5" looking at parent device '/devices/12c70000.i2c/i2c-1/1-0067': KERNELS=="1-0067" SUBSYSTEMS=="i2c" DRIVERS=="cyapa" ATTRS{product_id}=="CYTRA-116002-00" ATTRS{name}=="cyapa" ATTRS{firmware_version}=="2.13" ATTRS{baseline}=="107 92" looking at parent device '/devices/12c70000.i2c/i2c-1': KERNELS=="i2c-1" SUBSYSTEMS=="i2c" DRIVERS=="" ATTRS{name}=="s3c2410-i2c" looking at parent device '/devices/12c70000.i2c': KERNELS=="12c70000.i2c" SUBSYSTEMS=="platform" DRIVERS=="s3c-i2c" Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/sound.8/sound/card0/input2/event2': KERNEL=="event2" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/sound.8/sound/card0/input2': KERNELS=="input2" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="DAISY-I2S HDMI Jack" ATTRS{phys}=="ALSA" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/sound.8/sound/card0': KERNELS=="card0" SUBSYSTEMS=="sound" DRIVERS=="" ATTRS{id}=="DAISYI2S" ATTRS{number}=="0" looking at parent device '/devices/sound.8': KERNELS=="sound.8" SUBSYSTEMS=="platform" DRIVERS=="daisy-snd-max98095" Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/sound.8/sound/card0/input3/event3': KERNEL=="event3" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/sound.8/sound/card0/input3': KERNELS=="input3" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="DAISY-I2S Headphone Jack" ATTRS{phys}=="ALSA" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/sound.8/sound/card0': KERNELS=="card0" SUBSYSTEMS=="sound" DRIVERS=="" ATTRS{id}=="DAISYI2S" ATTRS{number}=="0" looking at parent device '/devices/sound.8': KERNELS=="sound.8" SUBSYSTEMS=="platform" DRIVERS=="daisy-snd-max98095" Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/sound.8/sound/card0/input4/event4': KERNEL=="event4" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/sound.8/sound/card0/input4': KERNELS=="input4" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="DAISY-I2S Mic Jack" ATTRS{phys}=="ALSA" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/sound.8/sound/card0': KERNELS=="card0" SUBSYSTEMS=="sound" DRIVERS=="" ATTRS{id}=="DAISYI2S" ATTRS{number}=="0" looking at parent device '/devices/sound.8': KERNELS=="sound.8" SUBSYSTEMS=="platform" DRIVERS=="daisy-snd-max98095" Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/gpio-keys.7/input/input5/event5': KERNEL=="event5" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/gpio-keys.7/input/input5': KERNELS=="input5" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="gpio-keys.7" ATTRS{phys}=="gpio-keys/input0" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/gpio-keys.7': KERNELS=="gpio-keys.7" SUBSYSTEMS=="platform" DRIVERS=="gpio-keys" ATTRS{keys}=="116" ATTRS{switches}=="0" ATTRS{disabled_keys}=="" ATTRS{disabled_switches}=="" Guillaume -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le 03/12/2014 16:48, Guillaume Gardet a écrit :
Le 02/10/2014 12:47, Dr. Werner Fink a écrit :
Hi,
just to be noted, that is not required to boot with openSUSE. Any nmodern Linux is enough, that is that there should be is the /sys file system and the filled /dev/input/ directory.
I'd like to know the output of
for n in /dev/input/event*; do udevadm info -a --name=$n done
then we might catch the input device for gpio-keys.8 and the power switch therein.
Here are the results (from ChromeOS):
I finally get openSUSE running again on my Chromebook ARM. I think you are looking for GPIO key 116 (/dev/input/event1). Note that my onboard keyboard is not working (except power switch). Here are the results (I have a USB keyboard connected): ******************************************************************************** Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/12c70000.i2c/i2c-1/1-0067/input/input0/event0': KERNEL=="event0" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/12c70000.i2c/i2c-1/1-0067/input/input0': KERNELS=="input0" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="Cypress APA Trackpad (cyapa)" ATTRS{phys}=="i2c-1-0067/input0" ATTRS{uniq}=="" ATTRS{properties}=="5" looking at parent device '/devices/12c70000.i2c/i2c-1/1-0067': KERNELS=="1-0067" SUBSYSTEMS=="i2c" DRIVERS=="cyapa" ATTRS{name}=="cyapa" looking at parent device '/devices/12c70000.i2c/i2c-1': KERNELS=="i2c-1" SUBSYSTEMS=="i2c" DRIVERS=="" ATTRS{name}=="s3c2410-i2c" looking at parent device '/devices/12c70000.i2c': KERNELS=="12c70000.i2c" SUBSYSTEMS=="platform" DRIVERS=="s3c-i2c" ATTRS{driver_override}=="(null)" Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/gpio-keys/input/input1/event1': KERNEL=="event1" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/gpio-keys/input/input1': KERNELS=="input1" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="gpio-keys" ATTRS{phys}=="gpio-keys/input0" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/gpio-keys': KERNELS=="gpio-keys" SUBSYSTEMS=="platform" DRIVERS=="gpio-keys" ATTRS{keys}=="116" ATTRS{switches}=="0" ATTRS{driver_override}=="(null)" ATTRS{disabled_keys}=="" ATTRS{disabled_switches}=="" Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/0003:045E:002B.0001/input/input2/event2': KERNEL=="event2" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/0003:045E:002B.0001/input/input2': KERNELS=="input2" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="Microsoft Internet Keyboard Pro" ATTRS{phys}=="usb-12110000.usb-1.3.1/input0" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/0003:045E:002B.0001': KERNELS=="0003:045E:002B.0001" SUBSYSTEMS=="hid" DRIVERS=="hid-generic" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0': KERNELS=="1-1.3.1:1.0" SUBSYSTEMS=="usb" DRIVERS=="usbhid" ATTRS{bInterfaceClass}=="03" ATTRS{bInterfaceSubClass}=="01" ATTRS{bInterfaceProtocol}=="01" ATTRS{bNumEndpoints}=="01" ATTRS{supports_autosuspend}=="1" ATTRS{bAlternateSetting}==" 0" ATTRS{bInterfaceNumber}=="00" ATTRS{interface}=="Microsoft Internet Keyboard Pro" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1': KERNELS=="1-1.3.1" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="00" ATTRS{devpath}=="1.3.1" ATTRS{idVendor}=="045e" ATTRS{speed}=="1.5" ATTRS{bNumInterfaces}==" 2" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="8" ATTRS{busnum}=="1" ATTRS{devnum}=="5" ATTRS{configuration}=="Microsoft Internet Keyboard Pro" ATTRS{bMaxPower}=="100mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="a0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="0" ATTRS{bcdDevice}=="0114" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{version}==" 1.10" ATTRS{urbnum}=="772" ATTRS{ltm_capable}=="no" ATTRS{removable}=="fixed" ATTRS{idProduct}=="002b" ATTRS{bDeviceClass}=="00" ATTRS{product}=="Microsoft Internet Keyboard Pro" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3': KERNELS=="1-1.3" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="00" ATTRS{devpath}=="1.3" ATTRS{idVendor}=="045e" ATTRS{speed}=="12" ATTRS{bNumInterfaces}==" 1" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="8" ATTRS{busnum}=="1" ATTRS{devnum}=="4" ATTRS{configuration}=="" ATTRS{bMaxPower}=="64mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="a0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="3" ATTRS{bcdDevice}=="0500" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{version}==" 1.10" ATTRS{urbnum}=="26" ATTRS{ltm_capable}=="no" ATTRS{removable}=="unknown" ATTRS{idProduct}=="001c" ATTRS{bDeviceClass}=="09" looking at parent device '/devices/12110000.usb/usb1/1-1': KERNELS=="1-1" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="01" ATTRS{devpath}=="1" ATTRS{idVendor}=="0409" ATTRS{speed}=="480" ATTRS{bNumInterfaces}==" 1" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="64" ATTRS{busnum}=="1" ATTRS{devnum}=="2" ATTRS{configuration}=="" ATTRS{bMaxPower}=="100mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="e0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="3" ATTRS{bcdDevice}=="0100" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{version}==" 2.00" ATTRS{urbnum}=="46" ATTRS{ltm_capable}=="no" ATTRS{removable}=="unknown" ATTRS{idProduct}=="005a" ATTRS{bDeviceClass}=="09" looking at parent device '/devices/12110000.usb/usb1': KERNELS=="usb1" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="00" ATTRS{devpath}=="0" ATTRS{idVendor}=="1d6b" ATTRS{speed}=="480" ATTRS{bNumInterfaces}==" 1" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="64" ATTRS{authorized_default}=="1" ATTRS{busnum}=="1" ATTRS{devnum}=="1" ATTRS{configuration}=="" ATTRS{bMaxPower}=="0mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="e0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="3" ATTRS{bcdDevice}=="0317" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{serial}=="12110000.usb" ATTRS{version}==" 2.00" ATTRS{urbnum}=="26" ATTRS{ltm_capable}=="no" ATTRS{manufacturer}=="Linux 3.17.4-1-lpae ehci_hcd" ATTRS{removable}=="unknown" ATTRS{idProduct}=="0002" ATTRS{bDeviceClass}=="09" ATTRS{product}=="EHCI Host Controller" looking at parent device '/devices/12110000.usb': KERNELS=="12110000.usb" SUBSYSTEMS=="platform" DRIVERS=="exynos-ehci" ATTRS{companion}=="" ATTRS{driver_override}=="(null)" ATTRS{uframe_periodic_max}=="100" Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1/0003:045E:002B.0002/input/input3/event3': KERNEL=="event3" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1/0003:045E:002B.0002/input/input3': KERNELS=="input3" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="Microsoft Internet Keyboard Pro" ATTRS{phys}=="usb-12110000.usb-1.3.1/input1" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1/0003:045E:002B.0002': KERNELS=="0003:045E:002B.0002" SUBSYSTEMS=="hid" DRIVERS=="hid-generic" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1': KERNELS=="1-1.3.1:1.1" SUBSYSTEMS=="usb" DRIVERS=="usbhid" ATTRS{bInterfaceClass}=="03" ATTRS{bInterfaceSubClass}=="00" ATTRS{bInterfaceProtocol}=="00" ATTRS{bNumEndpoints}=="01" ATTRS{supports_autosuspend}=="1" ATTRS{bAlternateSetting}==" 0" ATTRS{bInterfaceNumber}=="01" ATTRS{interface}=="Microsoft Internet Keyboard Pro" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3/1-1.3.1': KERNELS=="1-1.3.1" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="00" ATTRS{devpath}=="1.3.1" ATTRS{idVendor}=="045e" ATTRS{speed}=="1.5" ATTRS{bNumInterfaces}==" 2" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="8" ATTRS{busnum}=="1" ATTRS{devnum}=="5" ATTRS{configuration}=="Microsoft Internet Keyboard Pro" ATTRS{bMaxPower}=="100mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="a0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="0" ATTRS{bcdDevice}=="0114" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{version}==" 1.10" ATTRS{urbnum}=="772" ATTRS{ltm_capable}=="no" ATTRS{removable}=="fixed" ATTRS{idProduct}=="002b" ATTRS{bDeviceClass}=="00" ATTRS{product}=="Microsoft Internet Keyboard Pro" looking at parent device '/devices/12110000.usb/usb1/1-1/1-1.3': KERNELS=="1-1.3" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="00" ATTRS{devpath}=="1.3" ATTRS{idVendor}=="045e" ATTRS{speed}=="12" ATTRS{bNumInterfaces}==" 1" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="8" ATTRS{busnum}=="1" ATTRS{devnum}=="4" ATTRS{configuration}=="" ATTRS{bMaxPower}=="64mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="a0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="3" ATTRS{bcdDevice}=="0500" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{version}==" 1.10" ATTRS{urbnum}=="26" ATTRS{ltm_capable}=="no" ATTRS{removable}=="unknown" ATTRS{idProduct}=="001c" ATTRS{bDeviceClass}=="09" looking at parent device '/devices/12110000.usb/usb1/1-1': KERNELS=="1-1" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="01" ATTRS{devpath}=="1" ATTRS{idVendor}=="0409" ATTRS{speed}=="480" ATTRS{bNumInterfaces}==" 1" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="64" ATTRS{busnum}=="1" ATTRS{devnum}=="2" ATTRS{configuration}=="" ATTRS{bMaxPower}=="100mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="e0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="3" ATTRS{bcdDevice}=="0100" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{version}==" 2.00" ATTRS{urbnum}=="46" ATTRS{ltm_capable}=="no" ATTRS{removable}=="unknown" ATTRS{idProduct}=="005a" ATTRS{bDeviceClass}=="09" looking at parent device '/devices/12110000.usb/usb1': KERNELS=="usb1" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="00" ATTRS{devpath}=="0" ATTRS{idVendor}=="1d6b" ATTRS{speed}=="480" ATTRS{bNumInterfaces}==" 1" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="64" ATTRS{authorized_default}=="1" ATTRS{busnum}=="1" ATTRS{devnum}=="1" ATTRS{configuration}=="" ATTRS{bMaxPower}=="0mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="e0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="3" ATTRS{bcdDevice}=="0317" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{serial}=="12110000.usb" ATTRS{version}==" 2.00" ATTRS{urbnum}=="26" ATTRS{ltm_capable}=="no" ATTRS{manufacturer}=="Linux 3.17.4-1-lpae ehci_hcd" ATTRS{removable}=="unknown" ATTRS{idProduct}=="0002" ATTRS{bDeviceClass}=="09" ATTRS{product}=="EHCI Host Controller" looking at parent device '/devices/12110000.usb': KERNELS=="12110000.usb" SUBSYSTEMS=="platform" DRIVERS=="exynos-ehci" ATTRS{companion}=="" ATTRS{driver_override}=="(null)" ATTRS{uframe_periodic_max}=="100" ******************************************************************************** Guillaume -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Dr. Werner Fink -
Guillaume Gardet