search for: chantry

Signed-off-by: Xavier Chantry <chantry.xavier at gmail.com> --- man/nouveau.man | 16 ---------------- src/nv_const.h | 1 - 2 files changed, 0 insertions(+), 17 deletions(-) diff --git a/man/nouveau.man b/man/nouveau.man index 87f645a..cd66e9a 100644 --- a/man/nouveau.man +++ b/man/nouveau.man @@ -70,22 +70,6 @@...

...s3tc_init to their create_screen functions, and util/u_format_s3tc.c apparently contains all the functions that a gallium driver uses. So I suppose that nvfx and nv50 should do the same ? If that's correct, the patch below might not be completely wrong. On Mon, May 3, 2010 at 12:44 AM, Xavier Chantry <chantry.xavier at gmail.com> wrote: > flightgear now dies with : > Mesa warning: external dxt library not available: texstore_rgba_dxt3 > util/u_format_s3tc.c:66:util_format_dxt3_rgba_fetch_stub: Assertion `0' failed. > > I don't really understand what these stubs are...

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

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 *

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 str...

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

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 [

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

...9; > > Signed-off-by: Daniel Mack <daniel at caiaq.de> > Cc: David Airlie <airlied at linux.ie> > Cc: Ben Skeggs <bskeggs at redhat.com> > Cc: Francisco Jerez <currojerez at riseup.net> > Cc: Maarten Maathuis <madman2003 at gmail.com> > Cc: Xavier Chantry <shiningxc at gmail.com> > Cc: Marcin Slusarz <marcin.slusarz at gmail.com> > Cc: dri-devel at lists.sourceforge.net > --- > drivers/gpu/drm/nouveau/nouveau_connector.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/drivers/gpu/drm/...

...e into them? I've not had much luck in finding anything to support my concerns on the web, I assume this is because nobody in their right minds would design an application to work this way. Any help would be greatly appreciated. Brett Maton Linux Consultant RHCE #805007238628267 Anton House Chantry Street Andover SP10 1DE Mobile: 07765 240365 Tel: 01264 353211 ext 2338 brett.maton@simplyhealth.co.uk GBSLinuxAdmin@simplyhealth.co.uk (to include Mark Bradley) ----------------------------------------------------------------------------------------------- This email, and the contents containe...

...b5,a8,a8b8g8r8,x8b8g8r8,x1r5g5b5 -o Clear,Src,Dst,Over,OverReverse,In,InReverse,Out,OutReverse,Atop -t blend (restricted blend test to supported formats and operation. exluded composite,cacomposite,gradients,repeat tests which seem to take forever) Signed-off-by: Xavier Chantry <chantry.xavier at gmail.com> --- src/nv30_exa.c | 393 ++++++++++++++++++++++++-------------------------------- src/nv40_exa.c | 2 +- 2 files changed, 166 insertions(+), 229 deletions(-) diff --git a/src/nv30_exa.c b/src/nv30_exa.c index b736fb3..2cd7d32 100644 --- a/src/nv30_exa.c ++...

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

On Mon, Jan 11, 2010 at 10:13 AM, Xavier <shiningxc at gmail.com> wrote: > [ ?268.666662] reserve_ram_pages_type failed 0x9cba000-0x9cbb000, > track 0x8, req 0x10 > [ ?269.001031] reserve_ram_pages_type failed 0x6ff0000-0x6ff1000, > track 0x8, req 0x10 > [ ?269.474134] reserve_ram_pages_type failed 0x68f2000-0x68f3000, > track 0x8, req 0x10 > [ ?269.767270]

flightgear now dies with : Mesa warning: external dxt library not available: texstore_rgba_dxt3 util/u_format_s3tc.c:66:util_format_dxt3_rgba_fetch_stub: Assertion `0' failed. I don't really understand what these stubs are about, they were introduced by following commit : commit d96e87c3c513f8ed350ae24425edb74b6d6fcc13 Author: Jos? Fonseca <jfonseca at vmware.com> Date: Wed Apr 7