On Mon, Aug 23, 2010 at 7:30 AM, Henrik Rydberg <rydberg@xxxxxxxxxxx> wrote: > Hi Ping, > [...] >>> 1) It uses the MT slot protocol > >>> 2) It creates two input devices, but only one is useful >> >> I would like to keep the same wacom_features and usb_device_id >> wacom_ids structures for Bamboo as we did for all the other models, >> i.e., we define one entry for Bamboo although there could be more than >> one logical devices (touch and pen) associated with it. >> >> This may not make a difference for your Bamboo (a touch only device). >> It would make the code easy to maintain for the other Bamboos (Product >> ID: 0xd1, 0xd2, 0xd3, and 0xd4). >> >> If you are not sure what I am talking about, please let me know. > > > The problem I had with this is how that additional input device is presented > in userland. Pen and touch data are reported to the user space by different logical ports. So, there is no confusion among the data between the ports. MT X driver only needs to talk to the touch port. > As long as the capabilities are set properly for each input device, I > have no problem using one catch-all match in the device id list. I think we are safe here. It has been working like this for sometime... Ping -- 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
