atom feed17 messages in org.freebsd.freebsd-multimediaRe: nvidia binary drivers
FromSent OnAttachments
Marc van WoerkomApr 2, 2001 5:57 am 
Matthew ReimerApr 2, 2001 10:15 am 
Marc van WoerkomApr 2, 2001 10:38 am 
Coleman KaneApr 2, 2001 2:43 pm 
Marc van WoerkomApr 3, 2001 4:33 am 
Alexander LeidingerApr 3, 2001 8:08 am 
Marc van WoerkomApr 3, 2001 10:29 am 
Matthew ReimerApr 3, 2001 10:46 am 
Alexander LeidingerApr 3, 2001 12:06 pm 
Alexander LeidingerApr 3, 2001 12:07 pm 
Matthew ReimerApr 3, 2001 12:39 pm 
Marc van WoerkomApr 3, 2001 2:03 pm 
Marc van WoerkomApr 3, 2001 2:08 pm 
Coleman KaneApr 6, 2001 9:17 pm 
Alexander LeidingerApr 7, 2001 6:03 am 
Matthew ReimerApr 7, 2001 11:22 am 
Marc van WoerkomApr 9, 2001 7:15 am 
Subject:Re: nvidia binary drivers
From:Marc van Woerkom (van.@netcologne.de)
Date:Apr 3, 2001 2:08:01 pm
List:org.freebsd.freebsd-multimedia

Does nvidia_drv.o really _requieres_ the kernel module to put _something_ on the screen (do you have tried it yourself)?

I expect unresolved symbols while linking the glx module..

I didn't have the PI description about the architecture here, but if I remember correctly there are two ways to put 3D on the screen. A way which uses DMA and a way without DMA.

You probably refer to direct rendering (banging on the graphics iron directly) and indirect rendering (transmitting all graphics primitives via sockets), using the GL over X protocol (=GLX the protocol).

The latter has been realized with the Utah glx module for 3.3.x servers - but it is slow due to protocol overhead and of course because the driver does not use low level features of the nvidia chips, like DMA.

Regards, Marc

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message