David S. Miller writes:
> Console driver: I assume the keyboard/mouse is driven off the Zilog
> uarts, if so this should be relatively simple as I can
> adapt most of the code from my Sparc stuff and how I
> layed that code out. As for the screen I just need
> to figure out where the frame buffer lives and how to
> play with the palette registers and I'm set. Also
> should be cakewalk to do serial console as well. This
> might be a 4 or 5 day job depending upon how things
> go initially.
The keyboard and mouse, on the Indy and Indigo2, are driven by
a PS2-style keyboard and mouse controller. Aside from the different
way of addressing the registers, the driver should pretty much be the
same as the Linux PS2 keyboard and mouse controller.
The frame buffer is not directly addressable. Most operations
are performed via commands written to the pixel pipeline, although
one can DMA pixels from main memory to the frame buffer. I will
arrange for you to talk with the people who do IRIX X and GL
It will probably be a good idea to boot up on a serial console
first, since the graphics interface is a bit more complex than a dumb
frame buffer. That is how we usually port IRIX to a new system.
Since there are two serial ports, one can run the console on the first
port and the remote debugger on the second port, with very little
working beside the serial driver and bsaic exception handling
(assuming you start by booting using bootp() and the standard PROM).