> > When I get the intvid code done I think we can finally look forward to a day
> > when color support is a standard feature.
> 
> So how is this coming along?  I really have no idea when the 1.3 code

Pretty well. I've got the most important parts of the hardware independant
parts of the driver debugged (what X needs), the IIvx driver looks as
done as its going to get, and I'm close to getting a working DAFB driver.
I've got some old chicken scratches of mine about how the RBV works but
it turns out it wasn't quite enough. That, and I lost the IIsi I was testing
on. I'm going to look if I can borrow a friend's IIci and get that going.
I've also got a CIVIC driver in the works but I think that might be a bit
hedgy and I'm looking into the Valkyrie controller for the 630's using
the Valkyrie video driver from linux-pmac.

So with a little more work I've pretty much got all of the desktop machines
that I can think of, off hand. I would do PB support but I just don't have
any access to those machines! It shouldn't be too bad. Most PB's use the
same GSC chip which does very little in and of it self and the color PB's
all use the CSC for the most part with the exception of the 550 and, I think,
the 190 (which we don't seem to have a machine_id for) use the Ariel and
Keystone which I believe are like the intvid of some powermacs.

I'm close but far away. I think in the first alpha releases we're going to
look at IIvx, Quadra, and possibly CIVIC support. The DAFB and the CIVIC
support alot of extra features that I'm looking to implement that go above
and beyond what we currently support (like on the fly resolution switching
and page flipping). You'll be able to run X without them but the drivers
won't be "complete" until I add all that functionality. Those things
require fixes and changes to the kernel so those could take longer to
appear. Those features aren't going to be immediately advantageous but
an X server that supports hardware page flipping is absolutely going to
*fly* compared to it's no page-flipping brother.

> freeze will be (other than sooner than later :-) but it would be nice to
> make this much progress by the time that 1.3 rolls around.

Probably not likely. Scott has informed me that we're going to 1.3 fairly
soon and he's prob. going to do a feature freeze. Besides, we're currently
not mapping in device memory correctly on AV macs which is preventing me
from testing my very early CIVIC driver. Scott might be able to fix this
in 1.3.

I'm a bit busy now but I think we can expect at some point after 1.3 comes
out.