similar to: [PATCH] Remove leftover in man page and nv_const.h

X-Server versions older than 1.16.3 have bugs in their DRI3/Present implementation which impair nouveau, so it is better to stick to good old DRI2 by default on such servers. E.g., page flipping doesn't work at all under DRI3/Present with older servers, and use of extensions like OML_sync_control, SGI_video_sync or INTEL_swap_events also causes failure of Present. nouveau's glamor accel

That would be great, as long as it does only that and does not go into the "drivername" territory. As the said driver ;-) "A driver name to use can be provided instead of simple boolean value, which will be passed to the GL implementation for it to load the appropriate backend." -Emil On 4 July 2015 at 18:17, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > IMO

The DRI option with the intel ddx can be used to indicate the following - whether dri is disabled - the dri "version" - dri1, dri2, dri3 - the dri module name - doo_dri.so bar_dri.so I'm not sure how exactly it's supposed to work/works, and I believe most of that is due to legacy reasons. I'm just saying let's not do the whole thing - just the dri "version"

On 07/07/2015 09:51 PM, Ilia Mirkin wrote: > Lastly, from some discussions with ajax on IRC, it appears that DRI3 > is half-baked at best wrt sync between server and client. I think we > should just disable it by default for now, until issues are ironed > out. (Rather than what this patch has, which is default-on for Xorg > > some version.) What are the remaining known trouble

I am trying to understand the s3tc init code as nv50 gallium has a problem with that. It looks like some drivers (r300g and llvmpipe) actually inits s3tc in two places : ./src/mesa/main/texcompress_s3tc.c _mesa_init_texture_s3tc() ./src/gallium/auxiliary/util/u_format_s3tc.c util_format_s3tc_init() Here is an extract of the backtrace calls while loading fgfs on llvmpipe : driCreateScreen ->

Is it possible to use sync to vblank / swap control with mesa/gallium (and nouveau) ? I googled it but did not find any clear answers about how it is supposed to be enabled. I also tried to read the code, and I am getting lost. So I didn't find any answers to any of these questions : 1) how are we supposed to enable it ? is there an env var , or ~/.drirc ? is drirc/driconf still valid with

Make it a Bool consistently, as declared in header. Reported-by: Ilia Mirkin <imirkin at alum.mit.edu> Signed-off-by: Mario Kleiner <mario.kleiner.de at gmail.com> --- src/nouveau_present.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/nouveau_present.c b/src/nouveau_present.c index 4de1e6e..699a58d 100644 --- a/src/nouveau_present.c +++

Signed-off-by: Xavier Chantry <chantry.xavier at gmail.com> --- src/nv10_exa.c | 35 +++++++++++++++++++---------------- 1 files changed, 19 insertions(+), 16 deletions(-) diff --git a/src/nv10_exa.c b/src/nv10_exa.c index 1acb583..23a68e3 100644 --- a/src/nv10_exa.c +++ b/src/nv10_exa.c @@ -34,30 +34,33 @@ static struct pict_format { int exa; int hw; } nv10_tex_format_pot[] = { - {

Hi Marek Thanks a lot for your rebasing work. Here is my report : - all my games that broke with temporaries patch (they were either completely black or lot of black screen flash every frame) behave badly, but in different ways : * etracer is very slow and often crash in ttm code [1] (I think this is an old bug that just resurrected, no idea why) * foobillard is very slow and still flash a bit *

7.8 branch (533b7663) : 209/246 master branch (c882c31) : 216/241 In short : 8 fail/warn -> pass 5 fail -> skip 1 pass -> fail So the only regression is glean/clipFlat Output: ---------------------------------------------------------------------- Test clipping with flat shading (provoking vertex). clipFlat: Failure for glBegin/End(GL_QUADS), glFrontFace(GL_CCW) GL_EXT_provoking_vertex

in nv10_exa.c : check_texture does : if (w > 2046 || h > 2046) NOUVEAU_FALLBACK("picture too large, %dx%d\n", w, h); check_render_target does : if (w > 4096 || h > 4096) return FALSE; So we have different size limits for the source and the destination ? Another thing is that nv20 uses nv10_exa.c code, and the limit in

This has two purposes : - cleaner code - reduce the diff between nv30 and nv40 exa for a possible nvfx_exa merge ? The main differences seem to be that nv30 uses rect texture format (and does not support repeat on that). Then there are some minor changes in TX_FORMAT RT_FORMAT and TEX_FILTER usage. And NVAccelInitNVx0TCL look complete different. Tested with: ./rendercheck -t

From: Ville Syrjälä <ville.syrjala at linux.intel.com> Use drm_for_each_connector_encoder_ids() for iterating connector->encoder_ids[]. A bit more convenient not having to deal with the implementation details. Cc: Ben Skeggs <bskeggs at redhat.com> Cc: nouveau at lists.freedesktop.org Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com> ---

First some data errors I get with both nv20 exa and nv20 dri/mesa. 1. RT_FORMAT LINEAR + X8R8G8B8 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x00800080:0x00000105 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x01000100:0x00000105 LINEAR + A8R8G8B8 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x01000100:0x00000108 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x00800080:0x00000108 The only value I found in renouveau dump

12:08 < curro_> shining: hmm, it seems, darktama didn't quite finish the additional reloc checking he started to code 12:11 < curro_> shining: that would have solved your problem, poke him when he's back from vacations :) 12:16 < shining> curro_: hmm I really dont get it, it looks like domain can have both set, and flags can also have both set 12:16 < shining> I

Hi, I'm trying to get the new nouveau kernel driver (2.6.33-rc8) to work with X.Org 1.7.4 (Debian/unstable, all relevant packages updated). The modules load just fine, and the kernel spits out the following upon probe: [ 8.304602] nouveau 0000:06:00.0: PCI INT A -> Link[LNEB] -> GSI 18 (level, low) -> IRQ 18 [ 8.304779] nouveau 0000:06:00.0: setting latency timer to 64 [

On Wed, Feb 17, 2010 at 10:42:43AM +0100, Daniel Mack wrote: > Fix the following compile time error: > > drivers/built-in.o: In function `nouveau_connector_detect': > /home/daniel/src/linux/jup/linux-2.6/drivers/gpu/drm/nouveau/nouveau_connector.c:243: undefined reference to `acpi_lid_open' > > Signed-off-by: Daniel Mack <daniel at caiaq.de> > Cc: David Airlie

While keeping up-to-date the nouveau mesa driver (either classic or gallium), or doing regression testing, the big majority of my rebuilds resulted in segfaults. I am not talking about autogen or configure detection. I believe this also works automatically in other projects and doesn't with mesa, but forgetting to do this usually causes a build failure. Then autogen/configure can be run and

I've got a Linux server with over 1.5 Million files in a single directory, which as you will probably agree is not a good idea. My problem is that the management refuses to accept that it's a bad idea to have that many files in a single directory. To make the problem worse, the folder in question is exported via Samba and NFS! Has anyone come across any references/documents that I could

On Tue, May 18, 2010 at 7:04 PM, Roland Scheidegger <sroland at vmware.com> wrote: > Hi, > > I plan to merge the gallium-msaa branch to master soon. > It's actually a bit of a misnomer since the conceptually more important > changes in there are about blits... > > Here's a short summary what this is about: > blits now operate on resources, not surfaces