>Now could someone clue me in as to what happened to the frame buffer
>driver on the Assabet? It was working fine back in the
>2.3.99-pre-something days, but lately I've noticed that every other scan
>line is blank even though the screen geometry over all is correct (no,
>it's not hardware, the phase 4 Assabet does it, too).
I am not having that problem, with a 2.4.0-test1-etcetera kernel and using
NanoX and Microwindows. Are you having this problem when Tux is drawn?
>X and MicroWindows don't find the touch screen. "Error 2 opening touch
>panel; Cannot initialise mouse" is what the nano-X driver says. The major
>number is assigned dynamically. I stuck a device in /dev anyway and
>pointed "mouse" to it, still no joy. This one's a little light on
>documentation.
>Hints, anyone, please?
This is what Greg Haerr has to say on the NanoGUI mailing list (found at
www.microwindows.org):
"The microwindows touch screen drivers work on the MIPS Linux-VR
kernels and the StrongARM ADS graphics client boxes only right now.
I think Monta Vista has been working on a driver for the Assabet."
I'm not sure how close Monta Vista is to finishing the driver, or if they
are writing one at all (I'd assume that they are, seeing that they are
marketing a product with a working touchscreen and X on the SA-1110).
It's possible that a whole Assabet touchscreen driver might have to be
written from scratch for Microwindows if the Monta Vista rumor is
untrue, or at least the current driver will have to be modified...
Marco Carbone
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
