[ANNOUNCE] intel-gpu-tools 1.0.1

This release was inspired by going to roll a debian package for intel-gpu-tools and realizing I had no manpages. Whoops. And since I was in the directory, I decided to clean up some things that were bothering me about intel_gpu_dump output. Eric Anholt (6): Add gem_largeobject to ignore.

[PATCH] Lower required VBE version from 2.0 to 1.2

Evgeny M. Zubok evgeny.zu...@tochka.ru writes: So I conclude that the VBE version in vbeDoEDID can be lowered to 1.2 as soon as the procedure for verifying the presence of subfunction (15h in the case of DDC) is defined in VESA 1.2 and VESA 2.0 specs. If my arguments are right then the

Intel KMS Cannot runin framebuffer mode

I'm trying to run a KMS xorg without any config file (that seems like the way things are going, anyhow). I enabled KMS to be running by default in the kernel, I removed all framebuffer drivers, leaving only framebuffer support, and I got rid of my xorg.conf. When I try to run X, I get the

Re: Intel KMS Cannot runin framebuffer mode

It looks like konqueror can't do attachments through gmail, so here's another try with firefox... 2009/5/19 tsuraan tsur...@gmail.com: I'm trying to run a KMS xorg without any config file (that seems like the way things are going, anyhow).  I enabled KMS to be running by default in the kernel,

Re: Intel KMS Cannot runin framebuffer mode

and a re-send, both to the list and (hopefully) with the attachment. If I use my (previously working) xorg.conf, I get a moment of X, followed by the screen that I normally get before X sets the mode (blank, with a blinking cursor in the upper-left corner), but the cursor doesn't blink, and

VBE, int10 yeilds 0000:f8da: 00 ILLEGAL EXTENDED X86 OPCODE

Apparently I'm having trouble with int10. I'm running xorg-1.6.1,1 on FreeBSD-7.2 using xorg-7.4. Driver openchrome VendorName VIA Technologies, Inc. BoardName CN896/VN896/P4M900 [Chrome 9 HC] This works fine with the via driver in xorg-6.9, which is now

My savage test machine is now dead - last resend of patches

Two weeks ago, my home computer with the integrated ProSavageDDR video chipset died on me. After several attempts to diagnose the problem, it seems that the mainboard itself is damaged. So I built myself a new machine with an Intel i915 video chipset. Therefore I am no longer able to develop

Re: Intel KMS Cannot runin framebuffer mode

My guess is that my xorg.conf somehow conflicts with KMS, so, since X is now supposed to work without a config file, I'd give that a try. The xorg.conf that I'm trying to use is attached (if I'm lucky...). As it turns out, the xorg.conf isn't relevant. I removed the fbdev and vesa drivers

Re: [ANNOUNCE] xf86-video-intel 2.7.1

On Wed, 2009-05-13 at 00:12 -0400, Benjamin M. Schwartz wrote: Carl Worth wrote: * Fix crash with XV with large virtual display ( 2049). [Albert Damen al...@gmx.net] It's not what I would call fixed. With 2.6.*, XV with large virtual display would crash the server. With 2.7.1,

Re: [ANNOUNCE] xf86-video-intel 2.7.1

Carl Worth wrote: On Wed, 2009-05-13 at 00:12 -0400, Benjamin M. Schwartz wrote: Carl Worth wrote: * Fix crash with XV with large virtual display ( 2049). [Albert Damen al...@gmx.net] It's not what I would call fixed. With 2.6.*, XV with large virtual display would crash the

Mouse issues with Dual Head setup

I have a dual head setup on Kubuntu 9.04 (which means I am using 1.6) and I can't seem to type on the second head. I have KDE running on 1 screen, but am not running a window manager on the other screen - Only a virtualbox VM. I CAN move my mouse between screens and manage windows using it,

Re: [ANNOUNCE] xf86-video-intel 2.7.1

There is probably also a textured Xv adapter, have you double checked which one you are using? Maarten. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg

Current tinderbox regression (pixman, ppc only)

http://tinderbox.x.org/builds/2009-05-19-0022/logs/pixman/#build In file included from pixman-pict.c:35: pixman-vmx.h:40: warning: 'vmx_fast_paths' initialized and declared 'extern' pixman-vmx.h:40: error: 'vmx_fast_path_array' undeclared here (not in a function) -- Chris Ball

Re: Current tinderbox regression (pixman, ppc only)

Hi, pixman-vmx.h:40: error: 'vmx_fast_path_array' undeclared here (not in a function) I think this patch is sufficient; the assignment happens in pixman-vmx.c. diff --git a/pixman/pixman-vmx.h b/pixman/pixman-vmx.h index 2672004..47885f4 100644 --- a/pixman/pixman-vmx.h +++

[ANNOUNCE] intel-gpu-tools 1.0.1

This release was inspired by going to roll a debian package for intel-gpu-tools and realizing I had no manpages. Whoops. And since I was in the directory, I decided to clean up some things that were bothering me about intel_gpu_dump output. Eric Anholt (6): Add gem_largeobject to ignore.

Vesa driver support custom resolution?

Can anyone tell me if the Vesa driver can be used to set up a custom mode for a resolution not included in the supported mode table of a video card? I know that VBE 3.0 defines an interface to set the CRTC values rather than using a predefined mode, but I am not sure how many video cards actually