From: Pekka Paalanen <pq-X3B1VOXEql0@public.gmane.org>
To: Uwe Bugla <uwe.bugla-Mmb7MZpHnFY@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Gallium driver and compatibility issues
Date: Fri, 12 Mar 2010 22:25:41 +0200 [thread overview]
Message-ID: <20100312222541.131d8885@farn> (raw)
In-Reply-To: <1268401894.1759.59.camel-nwZTc+tSiniYW16jBriTx7NAH6kLmebB@public.gmane.org>
On Fri, 12 Mar 2010 14:51:34 +0100
Uwe Bugla <uwe.bugla-Mmb7MZpHnFY@public.gmane.org> wrote:
> "Note, that the Nvidia proprietary driver....."
> Lapse No. 3:
> Misleading usage of expressions.
> Everybody talking about the "Nvidia proprietary driver" in the
> graphic card context of Nvidia cards normallly means the blob
> driver shipped by Nvidia (closed source driver!) which does not
> have any problems with stuff like Compiz or other 3D
> applications. I do not like blob drivers for a whole bunch of
> reasons. As you are definitely using the wrong expression it
> remains your personal secret what you are trying to express or
> say.
One of the most common reasons for problems with Nouveau are
the remnants of the proprietary driver. Since you did not
provide kernel log, X log, nor glxinfo output, I of course
assumed the most probable case. A stale libglx from the blob
kills OpenGL, for instance.
Furthermore, you cannot have the Nvidia proprietary 3D
driver running by default, and then use the Nouveau 3D driver
on selected apps. If you use *any* part of Nouveau, you cannot
have *any* part of the proprietary driver, and vice versa.
They cannot live together at all.
I'm sorry I guessed your problem wrong. There was no real
information to begin the diagnosis with.
> "Problems are expected on the OpenGL front....."
> Lapse No. 4:
> I did not mention nearly all driver parts of the Gallium drivers
> carrying the "GL" in their names just by chance. I reflect while
> I am typing messages. I explicitly mentioned that the versions of
> the driver parts carrying the "GL" in their names are NOT
> responsible for the breakage that I reported.
> Thus it still remains your personal secret what you mean by
> "OpenGL front".
Actually, they are. Mesa libGL will try to load nouveau_dri.so
to provide hardware accelerated 3D rendering. At this time
OpenGL (via Mesa) is the only real user of nouveau_dri.so.
nouveau_dri.so may be loaded by the X server (AIGLX) or
the application (direct rendering) when they load libGL.
In short, having nouveau_dri.so will break OpenGL and perhaps
kill the X server in the AIGLX case.
> Lapse No. 6:
> Instead of repeating the core message of my request for 4 times
> in this mail (how insane!) I propose to change this page
> http://nouveau.freedesktop.org/wiki/GalliumHowto
>
> in the following way:
>
> 1. Wipe off the following stupid idiotic crap:
>
> "Warning : Nouveau's developers don't want people to build
> gallium drivers now, and do not support it at all. They also
> don't want bug reports on gallium ATM. This is code in rapid
> development. Bug reports for this are useless, as it's known to
> be broken."
That is rude on purpose. It is supposed to be crystal clear
to everyone, that this is not yet for end users, but apparently
it is not that clear. The time for end users will come, later.
At that time the page will be rewritten to be polite. Right now
it is just a cheatsheet for new developers.
> And once again: The error is not hidden in some library
> file containing the "GL" in its name, and the versioning of those
> GL files is also NOT the problem.
> It's the sources of the nouveau_dri.so file that do contain the
> bug.
True. nouveau_dri.so misses complete features and contains bugs.
I read your two first posts as nothing more than an elaborate
"Fix everything, please". That really is what people are actually
doing on their free time. Trying to kick their butt can only make
them ignorant or angry.
--
Pekka Paalanen
http://www.iki.fi/pq/
next prev parent reply other threads:[~2010-03-12 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 17:42 Gallium driver and compatibility issues Uwe Bugla
[not found] ` <1268329369.2107.14.camel-nwZTc+tSiniYW16jBriTx7NAH6kLmebB@public.gmane.org>
2010-03-11 18:23 ` Younes Manton
[not found] ` <586c2acd1003111023y72ca711at32b69b88252673f3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-11 19:40 ` Uwe Bugla
[not found] ` <1268336434.2397.3.camel-nwZTc+tSiniYW16jBriTx7NAH6kLmebB@public.gmane.org>
2010-03-11 19:57 ` Younes Manton
2010-03-12 10:52 ` Pekka Paalanen
2010-03-12 13:51 ` Uwe Bugla
[not found] ` <1268401894.1759.59.camel-nwZTc+tSiniYW16jBriTx7NAH6kLmebB@public.gmane.org>
2010-03-12 20:25 ` Pekka Paalanen [this message]
2010-03-12 20:58 ` Chicken Shack
2010-03-12 21:22 ` Uwe Bugla
[not found] ` <1268428922.2920.0.camel-nwZTc+tSiniYW16jBriTx7NAH6kLmebB@public.gmane.org>
2010-03-12 22:06 ` Luca Barbieri
[not found] ` <ff13bc9a1003121406x1612c2bfn7a3b4581152f5646-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-15 18:00 ` Uwe Bugla
2010-03-12 15:19 ` Christoph Bumiller
[not found] ` <4B9A5B9E.8090102-oe7qfRrRQffzPE21tAIdciO7C/xPubJB@public.gmane.org>
2010-03-12 16:09 ` Uwe Bugla
[not found] ` <1268410178.2680.20.camel-nwZTc+tSiniYW16jBriTx7NAH6kLmebB@public.gmane.org>
2010-03-12 19:37 ` Pekka Paalanen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100312222541.131d8885@farn \
--to=pq-x3b1voxeql0@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=uwe.bugla-Mmb7MZpHnFY@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.