multi-touch-dev team mailing list archive

[Manuel Schölling <manuel.schoelling@xxxxxx>]

Hi Henrik,

I'm using an Acer Aspire 1420P which also has a MosArt Touchscreen:
> Bus 004 Device 002: ID 062a:7100 Creative Labs
Although it's detected as a Creative Labs device by lsusb this
corresponds to

{ HID_USB_DEVICE(USB_VENDOR_ID_TURBOX,
USB_DEVICE_ID_TURBOX_TOUCHSCREEN_MOSART) },

I would very much appreciate if you would add

a) the definition of this device to the hid-dkms's hid-ids.h file:
#define USB_DEVICE_ID_TURBOX_TOUCHSCREEN_MOSART       0x7100


b) add it to the blacklisted devices in the hid-dkms's hid-core.c file:
static const struct hid_device_id hid_blacklist[] = {
	{ HID_USB_DEVICE(USB_VENDOR_ID_TURBOX,
USB_DEVICE_ID_TURBOX_TOUCHSCREEN_MOSART) },
[...]


c) add it to the supported devices in the hid-mosart-dkms's hid-mosart.c
file:
static const struct hid_device_id mosart_devices[] =
{ { HID_USB_DEVICE(USB_VENDOR_ID_TURBOX,
USB_DEVICE_ID_TURBOX_TOUCHSCREEN_MOSART) },
[...]


Note that it's definition is already included in the hid-mosart-dkms's
hid-ids.h file.

That would be perfect!! Thanks for the drivers! They are great!

Cheers,

Manuel


Am Montag, den 01.11.2010, 16:37 +0100 schrieb Henrik Rydberg:
> Hi Benjamin,
> 
> > this week end, I have in my hands an EeePC T91MT from Asus. The support of the
> 
> > dual touch screen is not working out of the box in Maverick.
> 
> 
> Thanks for the patches. Would you mind installing the attached dkms packages
> (hid-dkms first, hid-mosart second), and see if it works out well? The packages
> contain your patches, and will be put in the utouch ppa as soon as confirmed
> working.
> 
> Thanks,
> Henrik
> _______________________________________________
> Mailing list: https://launchpad.net/~multi-touch-dev
> Post to     : multi-touch-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~multi-touch-dev
> More help   : https://help.launchpad.net/ListHelp