nanogui: More...Porting to a custom video device
Subject:
Re: [nanogui] More...Porting to a custom video device
From:
Jordan Crouse ####@####.####
Date:
24 May 2001 14:59:45 -0000
Message-Id: <01052408584303.22437@cosmic>
There are several reasons why I wouldn't do this:
1. Without the kernel interface, you have to resort to somewhat ticky tack
methods of determine screen size, depth, colormap, etc, etc.. The kernel
gives you a universal method to determine everything you need to know about
the display.
2. Any way you slice it, you will still need some sort of kernel driver to
initalize and communicate with the hardware. (Unless of course your hardware
can be initalized by the BIOS and access through the standard VGA memory
window - but then if it could, why not use VESA?)
Jordan
On Thursday 24 May 2001 08:16, Simon Wood mentioned:
> > -----Original Message-----
> > From: Jordan Crouse ####@####.####
> > Sent: Thursday, May 24, 2001 3:02 PM
> > To: Gordon Minns; ####@####.####
> > Subject: Re: [nanogui] More...Porting to a custom video device
> >
> > When you can just do:
> >
> > [ Microwindows ] ---> [ Video driver ] ---> [ Video hardware ]
>
> [Simon Wood]
> I'd just like to point out you can also do:-
>
> [ Microwindows ] ---> [ Video hardware ]
>
> and cut out any kernel driver as well.
>
> It's very simple to take a 'scr_???.c' and modify it for your
> own hardware (I even had a mickey-mouse 'ascii' one writting
> directly to memory to fault find some stuff I was doing).
>
> Obviously you'll lose the pretty kernel messages, but you
> might not want these....
>
> Simon W.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
