search for: nv4a

The NV4A (aka NV44A) is an oddity in the family. It only comes in AGP and PCI varieties, rather than a core PCIE chip with a bridge for AGP/PCI as necessary. As a result, it appears that the MMU is also non-functional. For AGP cards, the vast majority of the NV4A lineup, this worked out since we force AGP c...

https://bugs.freedesktop.org/show_bug.cgi?id=49142 Bug #: 49142 Summary: [NV4A] OpengGL content corruption when width >= 2048 Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau...

https://bugs.freedesktop.org/show_bug.cgi?id=56721 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Nouveau driver fails on |[NV4A] Nouveau driver fails |nv40 with error -12 (out of |on nv40 with error -12 (out |memory) |of memory) --- Comment #2 from Ilia Mirkin <imirkin at alum.mit.edu> --- Has this improved on the latest kernels? If not, could you try a 3.2 ke...

https://bugs.freedesktop.org/show_bug.cgi?id=56721 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Ilia Mirkin <imirkin at

I have a Dell 2007FP monitor. NV43 (GeForce 6600) can not use the native resolution. 1600x1200 is listed under "DDC gathered Modelines" with the rest of the info, but then is missing from "probed modes". I have a secondary card, NV4a (GeForce 6200, PCI). It works with this card. This card does not show "DDC gathered modelines" at all, and 1600x1200 is listed under "probed modes". Does this mean the NV4a card is not using the DDC info? Is it a bug preventing 1600x1200 being used with the NV43, or some con...

https://bugs.freedesktop.org/show_bug.cgi?id=99584 Bug ID: 99584 Summary: XVMC on nv43 class card broken with recent mesa + kernel. Product: Mesa Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Hi, I'm considering submitting a project for this year's Google Summer of Code program that would involve making progress on hardware accelerated video decoding for the nouveau driver and wanted some feedback. I know that this isn't a big priority at the moment amongst the regular contributors, but I think it would make a good GSOC project because of it's somewhat narrow scope. I

...NV41:NV50 according to rnndb, which probably means that it's safe to use msi on nv41+ (via the 88068 address, since the 1800 stuff disappears on nv50+). [Based purely on speculation, btw, not on hardware experimentation. I assume pci_enable_msi() would implicitly fail on any non-pcie card, e.g. nv4a which is an agp version of nv44, and all the pci versions of the 6200 (and later) cards... i think there are some 8-series pci cards too.] -ilia

...>> probably means that it's safe to use msi on nv41+ (via the 88068 >> address, since the 1800 stuff disappears on nv50+). [Based purely on >> speculation, btw, not on hardware experimentation. I assume >> pci_enable_msi() would implicitly fail on any non-pcie card, e.g. nv4a >> which is an agp version of nv44, and all the pci versions of the 6200 >> (and later) cards... i think there are some 8-series pci cards too.] > Yeah, I suspect the only case we need to explicitly detect is the > BR02-using pretend PCIE cards. > > What's the pccid of y...

...t it's safe to use msi on nv41+ (via the 88068 > >>> address, since the 1800 stuff disappears on nv50+). [Based purely on > >>> speculation, btw, not on hardware experimentation. I assume > >>> pci_enable_msi() would implicitly fail on any non-pcie card, e.g. nv4a > >>> which is an agp version of nv44, and all the pci versions of the 6200 > >>> (and later) cards... i think there are some 8-series pci cards too.] > >> Yeah, I suspect the only case we need to explicitly detect is the > >> BR02-using pretend PCIE cards....

...are set apart by their YUV formats). Further, I simplify some error-checking details for both nv4 and nv10+ framebuffers as well as using the pitch properly instead of making wild assumptions (how did that every work... not sure). This has seen some modest modetest testing on NV5, NV17, NV34, and NV4A. I noticed some odd issues on NV5 with certain scaling factors, but I'm somewhat sure that those issues were there before - either the hw can't keep up or we're not twiddling some clocks. Ilia Mirkin (4): drm/nouveau/display: prevent undisplayable framebuffers from creation drm/nou...

...to rnndb, which > probably means that it's safe to use msi on nv41+ (via the 88068 > address, since the 1800 stuff disappears on nv50+). [Based purely on > speculation, btw, not on hardware experimentation. I assume > pci_enable_msi() would implicitly fail on any non-pcie card, e.g. nv4a > which is an agp version of nv44, and all the pci versions of the 6200 > (and later) cards... i think there are some 8-series pci cards too.] Yeah, I suspect the only case we need to explicitly detect is the BR02-using pretend PCIE cards. What's the pccid of your nv3x board? > >...

...bably means that it's safe to use msi on nv41+ (via the 88068 >>> address, since the 1800 stuff disappears on nv50+). [Based purely on >>> speculation, btw, not on hardware experimentation. I assume >>> pci_enable_msi() would implicitly fail on any non-pcie card, e.g. nv4a >>> which is an agp version of nv44, and all the pci versions of the 6200 >>> (and later) cards... i think there are some 8-series pci cards too.] >> Yeah, I suspect the only case we need to explicitly detect is the >> BR02-using pretend PCIE cards. >> >> W...

...afe to use msi on nv41+ (via the 88068 >> >>> address, since the 1800 stuff disappears on nv50+). [Based purely on >> >>> speculation, btw, not on hardware experimentation. I assume >> >>> pci_enable_msi() would implicitly fail on any non-pcie card, e.g. nv4a >> >>> which is an agp version of nv44, and all the pci versions of the 6200 >> >>> (and later) cards... i think there are some 8-series pci cards too.] >> >> Yeah, I suspect the only case we need to explicitly detect is the >> >> BR02-using pre...

Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nouveau_drv.h | 23 +++++ drivers/gpu/drm/nouveau/nouveau_reg.h | 16 ++-- drivers/gpu/drm/nouveau/nouveau_state.c | 8 ++ drivers/gpu/drm/nouveau/nv10_fb.c | 32 ++++++-- drivers/gpu/drm/nouveau/nv10_graph.c | 47 ++++++++--- drivers/gpu/drm/nouveau/nv20_graph.c | 80

...e msi on nv41+ (via the 88068 >>>>>> address, since the 1800 stuff disappears on nv50+). [Based purely on >>>>>> speculation, btw, not on hardware experimentation. I assume >>>>>> pci_enable_msi() would implicitly fail on any non-pcie card, e.g. nv4a >>>>>> which is an agp version of nv44, and all the pci versions of the 6200 >>>>>> (and later) cards... i think there are some 8-series pci cards too.] >>>>> Yeah, I suspect the only case we need to explicitly detect is the >>>>> BR...

https://bugs.freedesktop.org/show_bug.cgi?id=70388 Priority: medium Bug ID: 70388 Assignee: nouveau at lists.freedesktop.org Summary: [NV34] failed to idle channel 0xcccc0000 Severity: critical Classification: Unclassified OS: Linux (All) Reporter: rosti.bsd at gmail.com Hardware: x86 (IA32)

On Thu, Aug 29, 2013 at 12:45 AM, Ben Skeggs <skeggsb at gmail.com> wrote: > On Thu, Aug 29, 2013 at 12:20 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> On Wed, Aug 28, 2013 at 8:07 PM, Ben Skeggs <skeggsb at gmail.com> wrote: >>> On Wed, Aug 28, 2013 at 11:54 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>>> On Wed, Aug 28, 2013 at

https://bugs.freedesktop.org/show_bug.cgi?id=40747 Summary: The new nouveau kernel module fails to use my monitor's native resolution Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=99400 Bug ID: 99400 Summary: [nouveau] garbled rending with glamor on G71 Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at