On Wednesday 11 June 2003 10:19 am, Dave Jones wrote:
> On Wed, Jun 11, 2003 at 10:09:10AM +0100, Doug Rabson wrote:
> > This is more-or-less how the FreeBSD agp driver works for what its
> > worth. The chipset minidrivers are responsible for initialising
> > the aperture and inserting/removing entries. Common code in the
> > main driver handles the ioctl and kernel programming interfaces.
>
> To be honest, I looked at the FreeBSD agpgart driver a while after I
> had split out the Linux one into seperate subdrivers, and thought
> "Shit, they got it right first time, why didn't we?"
> It's a *lot* cleaner than the Linux one used to be, and in some
> parts, still is.
Don't beat yourself up - the FreeBSD driver is that way because I
studied the Linux driver first. It isn't really 'first time'..
>
> > > It's sad when the helper functions end up being more bother than
> > > help.
> >
> > You are welcome to use the FreeBSD driver as a starting point -
> > just leave my copyright in there :-)
>
> In an ideal world, we would have had a common codebase with wrappers
> for Linux/BSD functionality. The DRI folks seem to have got that bit
> right at least. Had this happened, FreeBSD would now have AGP3
> support too 8-)
If I had any systems which used AGP3, I might have done the work
already. I write this stuff for fun so stuff doesn't always happen
until I actually want it.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Phone: +44 20 8348 6160
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
