On Wednesday, April 21, 2010 01:01:58 am Dmitry Torokhov wrote:
> On Mon, Apr 19, 2010 at 11:46:14AM +0200, Jan-Hendrik Zab wrote:
> > On 14/04/10 16:34 -0700, Dmitry Torokhov wrote:
> > > Sorry for the delay. I wonder if we simply do not recognize PNP ID for
> > > the touchpad. Coudl you give me output of:
> > >
> > > for i in /sys/bus/pnp/devices/*; do echo $i; cat $i/id; done
> > >
> > > and also your dsdt.
> >
> > Hey,
> > I attached the DSDT and uploaded it to [0] for everyone on the
> > mailing list.
> >
>
> *sigh*
>
>
> Device (PS2M)
> {
> Name (_HID, "SNYSYN0003")
> Name (_CID, EisaId ("PNP0F13"))
> Name (_CRS, ResourceTemplate ()
>
> PNP ID should be 7 characters...
It'd be nice to know how Windows handles this situation. If we can
tell from the Device Manager that Windows actually exposes this
invalid _HID somehow, we might want to think about handling it
similarly in Linux.
If Linux completely ignores invalid _HIDs like this, we can only
use the _CID to bind a driver. If a device doesn't supply a _CID,
we'd be unable to bind a driver at all.
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
