Comment 30 for bug 218671

On Tue, Mar 3, 2009 at 11:38 PM, Bryce Harrington
<email address hidden> wrote:
> Basically I agree with comment #10.  This bug should go upstream for
> review.  I have a suspicion that there is something hardware-specific
> about this bug, but unfortunately none of the many people who have
> confirmed this issue have indicated what hardware they have, so it's
> impossible to determine this as the case, nor to develop a proper fix
> that conditionalizes the y-axis swap for that specific hardware.

Bryce - several of us have indicated it worked fine previously, and is
reversed in hardy. How can that be specific hardware with a swapped y
axis?

> So, before we can even upstream the bug, we must have this information.
> Attach the detailed lshal / lsusb / lsinput data that identifies the
> hardware you're using with -elographics.

I will attempt to get the lshal info if you think it will help.
AFAIK from reading reports everyone reporting this is using a serial
interface and we have given that information already -

From the earlier entries

 Elographics touchscreen is a AccuTouch, connected through a serial link.
 The controller is a model E271-2210, firmware revision 1.4

Elographics touchscreen is a AccuTouch, connected through a serial link.
The controller is a model E271-2200, firmware revision 2.0

Elographics touchscreen is a AccuTouch, connected through a serial link.
The controller is a model E271-2200, firmware revision 1.0.

I don't see however how the heck you expect us to prove whether it's
just some of the hardware or all of it. We can only test what we've
got in front of us.

Please, let me what else we can do to move this along!

Brian