Dmitry Torokhov wrote:
Hmm, I am concerned because not only you don't have an input device created, you don't even see the driver being registered with usbcore. Could you please try booting with debug_initcall to see with what error code usbtouchscreen initialization fails?
Here is the dmesg from a boot with debug_initcall. I can't see any messages from usbtouchscreen. For me, it looks like the touchscreen is discovered and then nothing happens to it. Helge Hafting
Attachment:
debug_initcall.gz
Description: application/gzip
- Follow-Ups:
- Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?
- From: "Dmitry Torokhov" <[email protected]>
- Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?
- References:
- usb touchscreen breakage in 2.6.21-rc5-mm4 ?
- From: Helge Hafting <[email protected]>
- Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?
- From: Dmitry Torokhov <[email protected]>
- Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?
- From: Helge Hafting <[email protected]>
- Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?
- From: Dmitry Torokhov <[email protected]>
- usb touchscreen breakage in 2.6.21-rc5-mm4 ?
- Prev by Date: Re: [PATCH] Add spaces on either side of case "..." operator.
- Next by Date: RE: Help Understanding Linux memory management
- Previous by thread: Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?
- Next by thread: Re: usb touchscreen breakage in 2.6.21-rc5-mm4 ?
- Index(es):