On Tue, Mar 8, 2011 at 14:29, Henrik Rydberg <rydberg@xxxxxxxxxxx> wrote: >> > This reminds me that we have to switch the other drivers to >> > hid-multitouch too. >> >> That would be nice. I don't see this really being done for the upcoming >> merge window, right Benjamin? > > There has been no activity in that direction here either... I've got Stantum, Cando and 3m that can be merged right now. I mean that they have been tested and do not have regressions (crossing fingers). This let Quanta and Mosart. I'm sure they worked some weeks ago, but I'm not sure (tested the last few days) ATM. If you want, I can send the three that goes well, and for the other, we'll see for 2.6.40. I have the auto-detection of contact counts that could go for 2.6.39 as well. Cheers, Benjamin > >> > Actually, I was not in favor of porting this driver into hid-multitouch. >> > eGalax has two differents protocols: one for resistive technology (which >> > is compatible with hid-multitouch in its current form), and one for >> > capacitive technology (which requires the "corrupt packet length" >> > quirk). >> > >> > Apparently, according to the kernel logs the Samsung MB30 is a resistive >> > technology (correct me if I'm wrong). This means that we also need >> > testings for the capacitive one. >> > >> > I'll let the community decide whether we should include this in >> > hid-multitouch. Henrik, Jiri, any idea? >> >> Either directly hid-multitouch, or hid-multitouch-capacitive sub-module >> should be fine. > > Maybe it is obvious already, but I think the patch is great. There is > really no reason to split the driver - in particular given that the > manufacturer has ensured similar behavior from both types. > > Thanks, > Henrik > -- 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
