search for: 4096x4096

...d the destination ? Another thing is that nv20 uses nv10_exa.c code, and the limit in check_texture could be increased for nv20 according to curro : 01:03 < curro_> shining: btw, about the 2048x2048 fallback, i'm quite sure it's wrong for nv2x 01:05 < curro_> shining: it can do 4096x4096 with no problems, IIRC And finally I saw that nouveau_exa_init does this : if (pNv->Architecture >= NV_ARCH_50) { exa->maxX = 8192; exa->maxY = 8192; } else if (pNv->Architecture >= NV_ARCH_20) { exa->maxX...

...verity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: tomi.pievilainen+freedesktop at iki.fi QAContact: xorg-team at lists.x.org If settings in xorg.conf exceed the maximum render target size (4096x4096 here), the system ends up in a state where X can only be activated again after a reboot. Would be better to notice this and just bailout with an error message. When trying to exceed the size with xrandr (for example when rotating a monitor), another monitor is disabled. Rotating back won't re-...

...ed? no > [ 5.428880] [drm:drm_enable_connectors], connector 13 enabled? yes > [ 5.428887] [drm:drm_target_preferred], looking for cmdline mode on connector 13 > [ 5.428894] [drm:drm_target_preferred], found mode 1024x768 > [ 5.428900] [drm:drm_setup_crtcs], picking CRTCs for 4096x4096 config > [ 5.428910] [drm:drm_setup_crtcs], desired mode 1024x768 set on crtc 10 But at no point does it see the TV-1 connector. I'm guessing something got busted in the nv04_tv stuff :( NV11 should have 2 CRTC's, but even if it had only 1, it should still be exposing the TV-1 connec...

https://bugs.freedesktop.org/show_bug.cgi?id=61069 Priority: medium Bug ID: 61069 Assignee: nouveau at lists.freedesktop.org Summary: Crash while displaying large image QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: dave.mueller at gmx.ch

https://bugs.freedesktop.org/show_bug.cgi?id=29386 Summary: 2D performance drops drastically when enabling a 2nd monitor Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

https://bugs.freedesktop.org/show_bug.cgi?id=90513 Bug ID: 90513 Summary: Odd gray and red flicker in The Talos Principle on GK104 Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

> On Tue, Apr 01, 2014 at 02:53:02PM -0400, Ilia Mirkin wrote: >I believe that ch7006 is the only external encoder that's supposed to >work, so you're in luck. It sounds like it passes the nv04_tv_identify >stage of nv04_tv_create -- perhaps it fails later? Although based on >the prints, it's even doing dpms stuff (but it hits _detect a second >time... odd). Try

..., connector 11 enabled? no [ 5.428880] [drm:drm_enable_connectors], connector 13 enabled? yes [ 5.428887] [drm:drm_target_preferred], looking for cmdline mode on connector 13 [ 5.428894] [drm:drm_target_preferred], found mode 1024x768 [ 5.428900] [drm:drm_setup_crtcs], picking CRTCs for 4096x4096 config [ 5.428910] [drm:drm_setup_crtcs], desired mode 1024x768 set on crtc 10 [ 5.430713] nouveau D[ PGRAPH][0000:01:00.0][0x02000062][dbf38360] created [ 5.430729] nouveau D[ PGRAPH][0000:01:00.0][0x02000062][dbf38360] initialised [ 5.430767] nouveau D[ PGRAPH][0000:01:00.0][0x0200...

*RESEND* due to exceeding the mailinglists limit for attachment size. Hi, I''m trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting. So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter. - When i don''t passthrough the radeon card, the