Date: Sat, 27 Mar 2010 05:57:24 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: gary.jennejohn@freenet.de Cc: arch@FreeBSD.org, Gleb Smirnoff <glebius@FreeBSD.org> Subject: Re: touch panel support Message-ID: <1269687444.35918.9.camel@balrog.2hip.net> In-Reply-To: <20100327102729.3bb8fba4@ernst.jennejohn.org> References: <20100326211706.GI18894@FreeBSD.org> <20100327102729.3bb8fba4@ernst.jennejohn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2010-03-27 at 10:27 +0100, Gary Jennejohn wrote: > On Sat, 27 Mar 2010 00:17:06 +0300 > Gleb Smirnoff <glebius@FreeBSD.org> wrote: > > > Hello, > > > > I've got a display with touch panel, and I'd like to get in working > > in FreeBSD. The touch panel is supported by NetBSD's uep(4). So far, > > I have written uep(4) for FreeBSD, that successfully reads and parses > > data from the USB touch panel device. > > > > And then I've got a problem. Our mouse subsystem is not ready for > > touch panels. Our mouse(4) protocol does not support mouse driver > > passing _absolute_ coordinates to the mouse(4) subsystem. It only > > expects a relative movement of the mouse. But _absolute_ coordinates > > are principal idea of any touch panel. > > > > The lesser problem is lack of generic support for touch panel > > calibration. > > > > Both of these problems are solved in NetBSD. They've got a wsmux(4) > > device, just like our kbdmux(4), but for mice. This mouse multiplexer > > can also understand absolute coordinates from underlying mice drivers. > > NetBSD also has a generic support for calibration of touch panels. > > > > What is the FreeBSD future way to go: port things for NetBSD? Write > > something different? > > > > IMO we should go for porting what NetBSD has. Well, input device stuff is tricky... From a console perspective, what we do now with kbdmux and moused seems like the right thing. If you look at X though, we would really like to have independent input devices, each with its own set of characteristics. For multi-seat installations, you basically want to allocate some set of input devices to each seat. In other cases, you might want your touchpad to work independently of your mouse, for example. I'm not certain what the best way to achieve this is, but our input layer is currently pretty frustrating to deal with, especially when you throw HAL or DeviceKit into the mix. We have to go to a lot of effort to figure out if mice are using moused or not, and if they should be advertised to X. robert. > -- > Gary Jennejohn > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" -- Robert Noland <rnoland@FreeBSD.org> FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1269687444.35918.9.camel>