On Thu, 17 Feb 2005, Paulo Marques wrote: >Dan Streetman wrote: >> Bottom line points: >> >> -nothing is gained from passing raw coordinates to evdev > >Nothing is gained either, since the information is the same (or less, in >case the hardware was mis-calibrated)
Yes, something is gained - I don't have to do software calibration! :) >> -passing calibrated coordinates to evdev makes software calibration >> optional. > >Optional doesn't save us any developing effort. On the contrary, we'll >have to make the software calibration *and* hardware calibration instead >of having just software calibration. Absolutely. No development effort is saved, I agree 100%. But development effort has never been the point! >> I do not want to have to do software calibration. If you want to, fine, >> you can do it just as well using hardware-calibration coordinates as raw >> coordinates. You won't ever notice the difference. > >That would be the worst of both worlds... Can you tell me _why_? >> Please, can we pass hardware-calibrated coordinates up from the 3M touch >> screen? :) > >If you want to develop the necessary software and convince the users to >calibrate twice, then sure, go ahead :) You are completely missing the point. Only one calibration will be done. 1. I'll do hardware calibration, _not_ software calibration. In order for this to be possible, the mtouchusb driver _has_ to pass calibrated coordinates up, not raw. 2. You do software calibration, _not_ hardware calibration. You should not care at all whether mtouchusb passes up raw or calibrated coordinates. >Lets get this into perspective, so that we can reach some conclusions. > >Am I missing something? It seems that the clear winner is the second >option. If you have some new points to add or don't agree with some of >the points above, please state your points clearly. Yes you are - you are missing the fact that you can do software calibration as much as you want, using hardware-calibrated coordinates. Software calibration does _not_ care whether the driver is passing raw or hardware-calibrated coordinates. The software calibration will do the conversion correctly _either way_. My point is, from a software calibration perspective, you should _not care_ whether the coordinates you get are raw or pre-calibrated. But from my perspective (of using just hardware calibration), I care _very much_. So since you shouldn't care and I do care, doesn't it make sense to just pass up the hardware-calibrated coordinates? -- Dan Streetman [EMAIL PROTECTED] --------------------- 186,272 miles per second: It isn't just a good idea, it's the law! ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
