From: Padfoot <padfoot@exemail.com.au>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: PROBLEM: Kernel version 3.2.1 usb touchscreen device not recognised [UDEV? USBINPUT? HOOK]
Date: Sat, 21 Jan 2012 07:13:58 +1100 [thread overview]
Message-ID: <4F19CB06.6040801@exemail.com.au> (raw)
In-Reply-To: <20120120160210.GA21565@kroah.com>
On 21/01/12 03:02, Greg KH wrote:
> On Fri, Jan 20, 2012 at 07:13:54PM +1100, Padfoot wrote:
>> Upgrade from kernel 3.1.9 to 3.2.1 eGalax usb touchscreen device is
>> no longer recognised.
>>
>> Device is an Acer Iconia Tab w501 with inbuilt touchscreen. Screen
>> is a pci device but is connected on boot as a usb input device.
>> Issue appears to be with either UDEV or USBINPUT boot hook failing
>> to recognise the device as can be seen in the dmesg.3.2.1
>> attachment.
>>
>> Downgrading to kernel 3.1.9 corrects the issue.
> Can you run 'git bisect' between 3.1.0 and 3.2.0 to find the problem
> commit here?
>
> Also, you might want to cc: the linux-input developers, they can help
> you out much better than the general list can.
>
> greg k-h
>
Hi Greg,
I am not a kernel dev, nor have I ever compiled a kernel, so I don't
think I am able to help with a git bisect to locate the offending
commit. I am just a regular user running pre-compiled packages on my
Arch Linux distro. But, of course I am happy to assist wherever I can.
Cheers.
Lachlan
next prev parent reply other threads:[~2012-01-20 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 8:13 PROBLEM: Kernel version 3.2.1 usb touchscreen device not recognised [UDEV? USBINPUT? HOOK] Padfoot
2012-01-20 16:02 ` Greg KH
2012-01-20 20:13 ` Padfoot [this message]
2012-01-20 20:44 ` Greg KH
2012-01-20 21:53 ` Padfoot
2012-01-20 20:50 ` Benjamin Tissoires
2012-01-20 20:50 ` Benjamin Tissoires
2012-01-20 21:57 ` Padfoot
2012-01-23 9:50 ` Benjamin Tissoires
2012-01-23 9:50 ` Benjamin Tissoires
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F19CB06.6040801@exemail.com.au \
--to=padfoot@exemail.com.au \
--cc=greg@kroah.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.