nanogui: a question about flnx on framebuffer
Subject:
Re: Re: a question about flnx on framebuffer
From:
Jordan Crouse ####@####.####
Date:
1 May 2001 13:57:38 -0000
Message-Id: <01050107581500.00882@cosmic>
I respectively disagree. The only thing we *do* need to write Microwindows
drivers are for touch screens that do not obey a standard format. For all
others, I have no reason to think that GPM will not be able to fit the bill
in most situations - for those that don't, by all means, write a driver. But
for example, USB is *far* better served by GPM (especially since we can
multiplex PS2 mice on the same port), than we could ever do by writing
multiple drivers and trying to reinvent the wheel.
Now there are some functions on some mice that GPM doesn't support. But then
we should ask ourselves - why do *we* need them if GPM doesn't?
Jordan
On Tuesday 01 May 2001 02:27, Alex Holden mentioned:
> On Mon, 30 Apr 2001, John Zulauf wrote:
> > Touchscreen too?
>
> I'll start off by writing drivers for the pointing devices that I actually
> own and want to be able to use with Nano-X. Ie. PS/2 three button, PS/2
> IntelliMouse with wheel (actually a Logitech trackball), serial MS
> protocol two button, USB, Mac ADB, possibly Acorn (if I can get it to boot
> a recent version of Linux), possibly SUN (if I can find or improvise an
> optical mouse pad for it). I'll probably also implement some way to allow
> multiple drivers to be compiled in and selected at run time (all optional
> at build time of course). For something like a touchscreen that doesn't
> already have a GPM driver (as in the Ipaq) I see no good reason not to
> write a native Nano-X driver for it.
>
> > (hello Alex, how's your last term treating you)
>
> Not too bad, I'm just trying to get my final year project working...
