similar to: XRandR 180

This patch does 3 things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a

Ben- I like the idea but I don''t understand how this patch can work: 1) You never put a name into `serial_devices[]'' for the summa port. The loop in `main'' that initializes the serial devices only calls `qemu_chr_open'' if there''s a string name in `serial_devices''. How did you get this to work? 2) Minor point, I don''t see the need

Hi everyone, My name is Pascal Schoenhardt. I am working on a SOC project to add XRandR 1.2 support to GNOME, and I use a laptop with an Nvidia card. Therefore, I also use Nouveau. First of all, great work guys. I am extremely excited about this project, and I'm amazed by the progress you are making with such a difficult task. I am posting this message to report my success with the nouveau

This is a slightly modified version of the original VGA patch that removes changes to the configure script to check for SSE2 capabilities. SSE2 is now only checked at run time. Signed-off-by: Don Dugger <donald.d.dugger@intel.com> -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Donald.D.Dugger@intel.com Ph: (303)440-1368 diff -r c445d4a0dd76

----- Forwarded message from Keir Fraser <keir.fraser at eu.citrix.com> ----- From: Keir Fraser <keir.fraser at eu.citrix.com> To: "xen-devel at lists.xensource.com" <xen-devel at lists.xensource.com> Cc: "Dugger, Donald D" <donald.d.dugger at intel.com> Date: Fri, 21 Nov 2008 13:02:26 +0000 Subject: [Xen-devel] Linux 2.6.27 temporary tree on xenbits

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 +++

Hi, I was wondering if you guys are working on a linux-image-2.6.27-amd64-xen? That would be great! Thomas

- map should handle this. --- src/nouveau_exa.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/nouveau_exa.c b/src/nouveau_exa.c index b656ca7..20ad380 100644 --- a/src/nouveau_exa.c +++ b/src/nouveau_exa.c @@ -259,7 +259,7 @@ nouveau_exa_mark_sync(ScreenPtr pScreen) static void nouveau_exa_wait_marker(ScreenPtr pScreen, int marker) { -

After syncing to the latest xen-unstable sources, I am getting following compilation error : make[3]: *** No rule to make target `/data/xen-sources/xen-unstable.hg/stubdom/ioemu/i386-stubdom/qemu.a'', needed by `/data/xen-sources/xen-unstable.hg/stubdom/mini-os-x86_32-ioemu/mini-os_app.o''. Stop. make[3]: Leaving directory

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

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

http://bugs.freedesktop.org/show_bug.cgi?id=15792 Summary: nv04 (TNT2) video blitter problem. Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

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"

This got broken with commit 86024cee back in 2014! drmmode_pixmap/nouveau_pixmap expect there to be EXA wrapping around the pixmap now, which is not there without accel. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/drmmode_display.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/drmmode_display.c b/src/drmmode_display.c index 89927a4..69421e1 100644

http://bugs.freedesktop.org/show_bug.cgi?id=24831 Summary: XRandR multihead fails on NV50 Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

http://bugs.freedesktop.org/show_bug.cgi?id=10927 Summary: segmentation fault in NVUploadToScreen, called from exaPutImage Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hi all, I just started using nouveau yesterday (after I lost my temper with the Nvidia 'driver' for the last time) and have found it *excellent* so far --- it works as well as nv on my card (GeForce 6150 Go) with xrandr1.2 as well, which is brilliant. One weird bug I noticed, which seems to be related to using the nouveau drivers, is that any bold text appears with abnormally-large letter

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

* Kill the A8+A8 hack. Recent enough X servers (>=1.7) fall back to ARGB glyphs for drivers not supporting A8 render targets. * Kill all the global state. It doesn't matter a lot yet but it might if we get multicard working at some point. * Other random clean-ups with no functional changes. Some numbers from x11perf -aa10text -aa24text -comppixwin10 -comppixwin500: * Before, with A