> >
> > The data is probably binary scancodes. I'll get on with that tomorrow.
> It is a struct input_event. (see: <linux/input.h> you always get whole
events.
> I have an example and explaination. Just gve me a day or two.
>
Got it. It'll be great to look at some sample code to read this, thx.
> > However, the data is still being interpreted by the application, what is
> > the most simple way to prevent that ( apart from not enabling the
modules
> > mousedev and keybdev ( in the drivers/input directory )? I know there is
an
> > usb hotplug script which may need some changes? I would like the mouse
> > events to pass through, but the keyboard events to be trapped for this
> > device only. Such that I can use the mouse under X, but lirc for
shortcut
> > keys. Way cool that would be.
> It is not clear what "application" means in this context. X is an
application,
> and there is a special meaning of application in the HID spec (probably
not
> that).
The "application" in this context referes to X applications. Since the
remote control appears to the application as a keyboard and mouse ( although
the following included file lists one driver as <none>, this is due to the
current config ), the events will be interpreted by X as mouse and keyboard
events. Even if I intercept the events at the input layer ( if this is the
right nomenclature ). By 'cat /dev/input/event0' I get garble text, but also
the functionality as keyboard/mouse.
>
> What devices are you planning to have connected under particular
> circumstances? What data from each device is supposed to go to where?
>
Only software that understands lirc will be used. The keys on the remote
will be mapped by lirc for a specific application according to the ~/.lircrc
file, whereas the mouse pointer on the remote will be used in X, configured
as '/dev/input/mice' in XFConfig.
> Can you post the device layout (especially /proc/bus/usb/devices with this
> magic remote control attached?
I'll include the whole file:
--------------
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=d800
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc=118/900 us (13%), #Int= 1, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=d400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0dc6 ProdID=2010 Rev= 1.10
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr= 50mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=hid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=(none)
E: Ad=82(I) Atr=03(Int.) MxPS= 4 Ivl=255ms
----------------------------
In addition, /proc/bus/input/devices. Note that the mouse is not listed this
time. This was rather late last night, so I'll need to get back to you with
the reason why the mouse does not appear at this time.
----------------------------
I: Bus=0003 Vendor=0dc6 Product=2010 Version=0110
N: Name=" IR USB Keyboard "
P: Phys=usb1:1/input0
D: Drivers=event0 keyboard
B: EV=120002
B: KEY=10000 7f ffe7207a c14057ff ffbeffdf ffffffff ffffffff fffffffe
B: LED=1f
----------------------------
I just noted some error on boot
----------------------------
usbfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
----------------------------
Then 12 x
----------------------------
usb-uhci.c: ENXIO 80000280, flags 0, urb cf725120, burb cf725180
mice: PS/2 mouse device common for all mice
----------------------------
There are two other occurences of these 'ENXIO' messages, but with different
'urb' value,, each with four entries:
usb-uhci.c: ENXIO 80000280, flags 0, urb cf033f80, burb cf725180
usb-uhci.c: ENXIO 80000280, flags 0, urb cdf06900, burb cf725180
>
> Concept:
> Attach the X mouse drver to the particular mouse device (eg
/dev/input/mouse0)
> Attach the X core keyboard to the dummy driver
There is already a core keyboard on the system, and this will be used in X
if need be, the keyboard is connected directly to system., and configured
under X as a corekeyboard using device '/dev/console'.
> Don't enable the keybdev driver (or load the module on some selective
basis
> for debugging)
Yes. For the purpose of this project, the keybdev module is not needed.
> Attach the keys interface on the remote control based on reading one or
more
> /dev/input/event devices.
The keys interface will always be managed by the lircd application,
www.lirc.org. It provides a convenient abstraction layer between the remote
control and the application. The application in this case is either xawtv,
cabletv, mplayer or anything else.
>
> Brad
>
>
Note that I will attempt to disable the CONFIG_USB_LONG_TIMEOUT in the
kernel, just to see if I can affect the behavior of not recognizing the
mouse. Yes, this is a wild guess.
Thanx!
Hans E.
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
