On Sun, 3 Oct 2004 11:50:50 -0400 (EDT), Vladimir Dergachev
<[EMAIL PROTECTED]> wrote:
> On Sun, 3 Oct 2004, Jon Smirl wrote:
>
> > If we could all just concentrate on fixing the radeondrm driver we
> > could build a complete driver for the radeon cards instead of the ten
> > half finished ones we have today. Once we get a complete driver the
> > incentive for people to write new ones will be gone.
>
> > My model....
> >
> > radeon - attached to hardware
> > drm - library
> > fb - library
> > fbcon - library
>
> Can we add to this "km" library ? (That's the GATOS v4l module)
>
> In particular, I can contribute the code that does Framebuffer->System Ram
> transfers over PCI/AGP. It is currently GPL licensed, but there is no
> problem if BSD folks want it too.
>
> This is also potentially useful for any Mesa functions that want to
> transfer data back from video RAM - using plain reads for this is really slow.
Drivers are free to call as many libraries as they want....
radeon - attached to hardware
drm - library
fb - library
fbcon - library
km - library
Libraries are kernel modules that don't attach to any specific
hardware, they just supply routines for other drivers to call. We
might want to change the name of these to libdrm, libfb, libkm.
I haven't looked into Gatos yet but I'd like to see the radeon
converted to follow the model of all of the other vl4 cards instead of
having it's own system. In the X on GL world the 2D XAA radeon driver
is gone. Gatos support will need to live somewhere else.
--
Jon Smirl
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
