> is a rather Bad Hack (seeing as it was built rather blindly to mimic the
> behaviour of the Windows driver, and has IRQ/port hardcoded in), but it
> works for me with the 2.2.16 kernel.
Thats pretty much how we did the pc110 pad driver too.
> The device outputs 5 byte packets - 1 status byte, 2 bytes each for X & Y
> coordinates. The devel branch of GTK+ has support for /dev/fidmour in the
That also sounds suprisingly familiar. I wonder, I wonder 8)
> I'm wondering if anyone has a resource that would provide information on
> porting this driver to the 2.4 kernel.
Two approaches. #1 You leave it as its own misc device and XInput device as
the pc110 pad does (the pc110pad reports ps/2 codes and does drag/tap in
the driver - might be worth a look to steal that)
> I would welcome comments on this driver, or on the MPC-501 and Linux in
> general. Bonus points to anyone who actually understands why the driver
> works and how the hardware works. :)
You might want to let the guys at www.amherst.co.uk know about it so they can
add it to their resources on the fiva
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Feb 15 2001 - 21:00:24 EST