Re: [nouveau] a million little pieces affecting nvidia drivers

2007-01-15 Thread Stephane Marchesin
Alexy Khrabrov wrote:
> Philipp, Mark --
>
> Thanks for the concise and extremely useful explanation!  This is
> worthy of being on the front page of a wiki.
>
>   
Also, there is that :
http://people.freedesktop.org/~ajax/dri-explanation.txt

Stephane



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [nouveau] a million little pieces affecting nvidia drivers

2007-01-15 Thread Alexy Khrabrov
Philipp, Mark --

Thanks for the concise and extremely useful explanation!  This is
worthy of being on the front page of a wiki.

Cheers,
Alexy

On 1/15/07, Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Sun, 2007-01-14 at 00:22 +0100, Philipp Klaus Krause wrote:
> >
> > GLX canbe used over a network, but currently the free drivers don't support
> > hardware-acceleration in this case.
>
> That's no longer true since the introduction of AIGLX in X.org 7.1.
>
>
> --
> Earthling Michel Dänzer   |  http://tungstengraphics.com
> Libre software enthusiast |  Debian, X and DRI developer
>
>

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [nouveau] a million little pieces affecting nvidia drivers

2007-01-15 Thread Michel Dänzer
On Sun, 2007-01-14 at 00:22 +0100, Philipp Klaus Krause wrote:
> 
> GLX canbe used over a network, but currently the free drivers don't support
> hardware-acceleration in this case.

That's no longer true since the introduction of AIGLX in X.org 7.1.


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [nouveau] a million little pieces affecting nvidia drivers

2007-01-13 Thread Philipp Klaus Krause
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Alexy Khrabrov schrieb:
> When trying to make nvidia drivers sleep, and then later get nouveau
> to work, I got hopelessly confused about various pieces of video
> hardware/software and their mutual entanglements.  I'd much
> appreciates if one of you esteemed video sages takes a few steps
> towards deconfusion.
> 
> The TLAs floating in this soup are
> 
> AGP
> DRI
> DRM
> 
> Obviously, we need a new DRM driver for nouveau as it says to compile
> it.  This installs library libdrm.so -- who uses it?  We're talking of
> DRM, while X refers to DRI?

DRM is the part of the 3D driver that is part of the kernel. For AGP
cards it depends on the AGP driver in the kernel.
Mesa does the OpenGL rendering. It contains both a software
implementation and some other backends, the most important one is DRI,
3D hardware drivers, which use libdrm to acces the kernel part.

So the AGP driver is at the lowest layer, the DRM accesses the AGP
driver and the hardware. libdrm is used by DRI (which is part of Mesa)
to access the DRM in the kernel. X uses Mesa for OpenGL rendering. GLX
is the part of X that is accessed by OpenGL applications. GLX canbe used
over a network, but currently the free drivers don't support
hardware-acceleration in this case. Nvidia's proprietary drivers do
(though somewhat limited).

The situation is similar with ATI's proprietary drivers, but Nvidia's
proprietary drivers are different.

The framebuffer drivers in the kernel are something different. They are
used for advanced graphics stuff on the console (as opposed to X).
Different numer of lines and columns on the console and such. They
access the same hardware as the DRM does, which sometimes leads to problems.

Philipp
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFqWnDbtUV+xsoLpoRAvnLAJsFEqkTzXrYB9uKpXTuwzT5h2JC3gCgiDWz
CqTJwMA9XlpM+DCKVkV42Ag=
=iviY
-END PGP SIGNATURE-

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel