search for: nouveau_vieux

This fixes issues where get_rt_format would see a 0 format because the nouveau_surface had not been properly initialized. Fixes crash on supertuxkart startup (which still fails due to out-of-vram issues). Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/mesa/drivers/dri/nouveau/nouveau_texture.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git

https://bugs.freedesktop.org/show_bug.cgi?id=71438 Priority: medium Bug ID: 71438 Assignee: nouveau at lists.freedesktop.org Summary: Application Konqueror crashes when connecting to asus.com QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

https://bugs.freedesktop.org/show_bug.cgi?id=65576 Priority: medium Bug ID: 65576 Assignee: nouveau at lists.freedesktop.org Summary: [NV11] no EGL with nouveau_vieux_dri - no DRI_IMAGE Severity: normal Classification: Unclassified OS: Linux (All) Reporter: chris at edesix.com Hardware: x86 (IA32) Status: NEW Version: git Component: Drivers/DRI/nouveau Product: Mesa If...

.... Making it so that the additional >> functionality can be loaded on demand (i.e. Y/M/N) may be much >> trickier, to the point of it not being worth it for the additional >> complexity. >> >> -ilia > > > In mesa, it is possible to build the driver you want (nouveau_vieux, nv30, > nv50 or nvc0) so the feature is already there. Really? How do you compile only nv50? (Hint: you can't. nv30/nv50/nvc0 are all linked together in the nouveau driver, no way to split them out, largely because of the nouveau_drm_screen_create function.) > There is no point for the...

On Tue, Jul 30, 2013 at 6:31 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote: > On 30/07/13 21:39, Christ-Jan Wijtmans wrote: >> Hi, my apologies if this is the wrong place to post this. >> I had the desire to turn on or off support for certain chipsets. >> Because i felt like the nouveau drivers are (relatively) quite large and >> depends on some kernel code

...be loaded on demand (i.e. Y/M/N) may be much >>>> trickier, to the point of it not being worth it for the additional >>>> complexity. >>>> >>>> -ilia >>>> >>> >>> In mesa, it is possible to build the driver you want (nouveau_vieux, >>> nv30, >>> nv50 or nvc0) so the feature is already there. >>> >> Really? How do you compile only nv50? (Hint: you can't. nv30/nv50/nvc0 >> are all linked together in the nouveau driver, no way to split them >> out, largely because of the nouveau_...

...Go card (NV11). The nouveau framebuffer is working fine (KMS enabled), but X won't start with the nouveau driver (it's okay with fbdev): [ 54.231] (II) NOUVEAU(0): Opened GPU channel 1 [ 54.231] (II) NOUVEAU(0): [DRI2] Setup complete [ 54.231] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau_vieux [ 54.231] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau_vieux [ 54.233] (EE) NOUVEAU(0): Error allocating scanout buffer: 0 [ 54.233] Fatal server error: [ 54.233] AddScreen/ScreenInit failed for driver 0 I'm on Fedora 15 and I have tried with the latest packaged driver and with...

...e > init code to do Y/N selects. Making it so that the additional > functionality can be loaded on demand (i.e. Y/M/N) may be much > trickier, to the point of it not being worth it for the additional > complexity. > > -ilia In mesa, it is possible to build the driver you want (nouveau_vieux, nv30, nv50 or nvc0) so the feature is already there. There is no point for the ddx. As for drm, I sure would use this feature as this would cut down compilation time a lot when doing out of the tree builds. With the core arch, in theory, it shouldn't be that hard if you want plan on using old...

Hi, I have a geforce 4mx 440 agp 8x, and I'm trying to use the GBM library, (as jbarnes in: http://virtuousgeek.org/blog/index.php/jbarnes/2011/10/ and David Hermann in KMSCON: https://github.com/dvdhrm/kmscon), without success. when I try to create a gbm_device, I get: (below the code.) nouveau_drm_screen_create: unknown chipset nv18 dri_init_screen_helper: failed to create pipe_screen

...additional >>> functionality can be loaded on demand (i.e. Y/M/N) may be much >>> trickier, to the point of it not being worth it for the additional >>> complexity. >>> >>> -ilia >> >> In mesa, it is possible to build the driver you want (nouveau_vieux, nv30, >> nv50 or nvc0) so the feature is already there. > Really? How do you compile only nv50? (Hint: you can't. nv30/nv50/nvc0 > are all linked together in the nouveau driver, no way to split them > out, largely because of the nouveau_drm_screen_create function.) Hmm, as I nee...

.../M/N) may be much >>>>> trickier, to the point of it not being worth it for the additional >>>>> complexity. >>>>> >>>>> -ilia >>>>> >>>> >>>> In mesa, it is possible to build the driver you want (nouveau_vieux, >>>> nv30, >>>> nv50 or nvc0) so the feature is already there. >>>> >>> Really? How do you compile only nv50? (Hint: you can't. nv30/nv50/nvc0 >>> are all linked together in the nouveau driver, no way to split them >>> out, largely...

https://bugs.freedesktop.org/show_bug.cgi?id=51409 Bug #: 51409 Summary: when ubuntu tests the gnome environment the nouveau_vieux_dri (ver) segfaults Classification: Unclassified Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assign...

https://bugs.freedesktop.org/show_bug.cgi?id=54700 Bug #: 54700 Summary: Distorted graphics (double cursor) with GeForce 4200Go (NV28) Classification: Unclassified Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal

https://bugs.freedesktop.org/show_bug.cgi?id=63481 Priority: medium Bug ID: 63481 Assignee: nouveau at lists.freedesktop.org Summary: Nouveau driver - No monitor signal on chipset NV1A (family NV10) since bisected bad commit ebb945a94bba2ce8dff7b0942ff2b3f2a52a0a69 in kernel 3.7.9 QA

...99.901, module version = 1.0.0 [ 4325.501] ABI class: X.Org ANSI C Emulation, version 0.4 [ 4325.501] (--) Depth 24 pixmap format is 32 bpp [ 4325.503] (II) NOUVEAU(0): Opened GPU channel 1 [ 4325.503] (II) NOUVEAU(0): [DRI2] Setup complete [ 4325.503] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau_vieux [ 4325.503] (II) NOUVEAU(0): GART: 64MiB available [ 4325.506] (II) NOUVEAU(0): GART: Allocated 16MiB as a scratch buffer [ 4325.506] (**) NOUVEAU(0): Option "MigrationHeuristic" "always" [ 4325.506] (**) NOUVEAU(0): Option "EXANoComposite" "false" [ 432...