Will this Xserver work on the CATS too? Will it support
more graphics cards than the S3 ViRGE-based?

----
Jes=FAs Eugenio S=E1nchez Pe=F1a (eugenio.sanchez@avantel.com.mx)
Avantel, S.A. x5868, v273-5868, (8) 153-5868
B=EDper: 01-800-112-4737 cve. 8303075
I've a StrongARM computer and you don't.


-----Original Message-----
From: Mark Brinicombe [mailto:mark@causality.com]
Sent: Monday, September 21, 1998 8:10 PM
To: NetBSD/arm32 Mailing List
Subject: Re: Source changes on the horizon


[stuff deleted]

So my current source hacking to-do list looks something like the
following. (order subject to regular shuffling)

o  Merge CATS support into -current
o  Commit MI seeq800x ethernet driver and new podulebus attachments as
   soon as I am happy with it.
o  Adapt all the podulebus SCSI driver that use the SFAS216 or NCR
compat
   chips to use the MI NCR53c9x driver. (I need to fix a couple of
panics
   I current am getting with the ptsc driver and merge in Markus's csc
   driver changes.)
o  Implement a VIDC driver for WSCONS framework and switch the
   RiscPC/A7000 over to wscons.
o  Switch shark to WSCONS.
o  Get new RiscPC Xserver debugged and commited to the xsrc tree.
o  Implement framework for cache and TLB ops rescheduling and implement
   for all supported ARM processors.
o  Complete and merge Neil's userland cache nuke tracking.
o  Complete versions of the wdc attachments for the bouyer-ide branch.

[stuff deleted]