nanogui: More...Porting to a custom video device
Subject:
RE: [nanogui] More...Porting to a custom video device
From:
Simon Wood ####@####.####
Date:
24 May 2001 16:12:49 -0000
Message-Id: <44632C76B97BD211AF6B00805FADCAB208790654@exchange.saltaire.pace.co.uk>
> -----Original Message-----
> From: Gray, Tim ####@####.####
> Sent: Thursday, May 24, 2001 4:50 PM
> To: ####@####.####
> Subject: RE: [nanogui] More...Porting to a custom video device
>
> Ok I think I have an Idea of what he means.
>
> Example: I grab a standard parallel input LCD that is
> 240X64 pixels 1bpp only. This device sits on either the parallel port or a
> General purpose I/O bus.
[Simon Wood]
Yes this is the sort of thing I mean (and perhaps Gordon
wants to do it this way as well...)
> would it be feasible to write a framebuffer driver for the linux kernel for
> such a device, or would it be easier to just write a driver for microwindows
> that just dumps the display to a block of ram and then have a daemon running
> that snags that block of ram and shovel it to the device....
[Simon Wood]
Why would you need to store it in RAM? Doesn't each window
keep a local copy of itself any way?
Shouldn't Microwindows wiggle the PIO pins directly?
(Oh any you shouldn't assume that it's running on top of
Linux, or any other kernel. It could be a single statically
linked application.)
> On a side note, this is very interesting to me, as a project I am currently
> working on follows these same lines...
[Simon Wood]
Go on, spill the beans.... we ought to setup up an appliance
list of all the targets Microwindows is used on - you know a
shameless bit of self promotion wouldn't go a miss.
What's the smallest device (processing power) that people have
ported Microwindows to????
Anyway putting all this aside, the sun is shining, the work day
is over and I can hear an ice-cream calling!!
