[PATCH 0/9] handle detailed timing and short video descriptor of CEA extension

Hi All, I re-updated the patches which are intended to handle detailed timing blocks in EDID and E-EDID. In order not to pollute xf86MonPtr interface, based on Ajax's suggestion I used unified interface. And in patch 8, we select appropriate modes from video blocks of CEA extension, then

[PATCH 1/9] Includes new structures and defined MACRO

declare new structures and MACRO related with CEA extension. --- hw/xfree86/ddc/edid.h | 90 + 1 files changed, 90 insertions(+), 0 deletions(-) diff --git a/hw/xfree86/ddc/edid.h b/hw/xfree86/ddc/edid.h index b556003..0af9e59 100644 ---

[PATCH 2/9] construct detailed timing unified interface

construct unified interface, anytime when program need detailed timing block, it always dynamically parse and handle it through the interface. --- hw/xfree86/ddc/interpret_edid.c | 182 +++ hw/xfree86/ddc/xf86DDC.h|5 + 2 files changed, 132

[PATCH 4/9] handle detailed timing operation in xf86EdidModes.c

handle detailed timing quirks and insert detailed timing modes into mode list --- hw/xfree86/ddc/xf86DDC.h | 39 + hw/xfree86/modes/xf86EdidModes.c | 284 -- 2 files changed, 190 insertions(+), 133 deletions(-) diff --git

[PATCH 5/9] handle detailed timing operation in xf86Crtc.c

through unified interface handle monitor record and physical size of detailed timing block --- hw/xfree86/modes/xf86Crtc.c | 132 --- 1 files changed, 87 insertions(+), 45 deletions(-) diff --git a/hw/xfree86/modes/xf86Crtc.c

[PATCH 8/9] handle cea-ext data block and insert mode into mode list.

select appropriate mode form video data blocks of CEA extension, then insert them into mode list. --- hw/xfree86/ddc/interpret_edid.c | 56 + hw/xfree86/ddc/xf86DDC.h |3 + hw/xfree86/modes/xf86EdidModes.c | 102 ++ 3 files

XKB - xkbcomp can't find keycode includes (Bug?)

Hi All, xkbcomp fail with message: The XKEYBOARD keymap compiler (xkbcomp) reports: Error:Can't find file xfree86 for keycodes include Exiting Abandoning keycodes file default Errors from xkbcomp are not fatal to the X server (EE) Error

Re: [PATCH] glx: Replace broken GLX visual setup with a fixed all mode.

On Sun, 2009-02-08 at 13:00 +0100, Eric Anholt wrote: With trying to match depths so that you didn't end up with a depth 24 fbconfig for the 32-bit composite visual, I broke the alpha bits on the depth 24 X visual, which angered other applications. But in fixing that, the pickFBconfigs code

Re: [PATCH 8/9] fb: move some code to mi

commit 734b23e5982e171031077a2d5d6b5dc2a12e1a70 should fix the problem. Maarten. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg

How To Disable input driver

Hi I am using Xorg version - 1.5.2 I am developing kernel driver which create /dev/eventX - file. when i insert the kernel driver X11 thinks it's a mouse. how can i configure the X11 to ignore the driver (/dev/eventX) thanks ___ xorg mailing list

Re: How To Disable input driver

On Wed, Feb 11, 2009 at 04:38:41PM +0200, linux multitouch wrote: Hi I am using Xorg version - 1.5.2 I am developing kernel driver which create /dev/eventX - file. when i insert the kernel driver X11 thinks it's a mouse. how can i configure the X11 to ignore the driver

Re: [RFC] XI2 draft protocol specification (v 0.1)

Peter Hutterer wrote: Thanks for the comments. All your suggestions have been added, but I'll refrain from commenting on them much (the spec has to work on it's own eventually). No prob. Some details follow though. FP1616 -Fixed point decimal in 16.16 format as 32 bit integer. The

USB Touchscreen

Hi, I'm using Xfbdev with TSlib and the Linux input event interface. The command line I'm using to launch X is: Xfbdev :0 -br -pn -mouse tslib,,device=/dev/input/event2 -noreset -screen 800x600x16 This is my problem, when I disconnect the touch some library (TSlib or X itself) lost the

Re: Fedora 10, Belkin KVM, USB Mouse/Keyboard, NVIDIA Card, OpenOffice

Thanks -- I did just that (after a few trial and errors) and was able to get it to crash: Received signal SIGSEGV, Segmentation fault. XkbStringText (str=0x21 Address 0x21 out of bounds, format=2) at xkbtext.c:526 526for (ok= True,len=0,in=str;*in!='\0';in++,len++) { (gdb) Continuing.

Current tinderbox regression (mesa)

http://tinderbox.x.org/builds/2009-02-10-0034/logs/libGL/#build In file included from nv04_surface_2d.c:5: ../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:8:32: error: nouveau/nouveau_bo.h: No such file or directory ../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:9:37:

Re: [PATCH 8/9] handle cea-ext data block and insert mode into mode list.

On Wed, 2009-02-11 at 17:17 +0800, Ma Ling wrote: +void xf86FetchDataBlock(xf86MonPtr mon, +int ext_type, int data_type, +void *data) +{ +int i; +Uchar *ext; + +if (mon == NULL) + return; + +for (i = 0; i

Re: [PATCH 4/9] handle detailed timing operation in xf86EdidModes.c

On Wed, 2009-02-11 at 17:15 +0800, Ma Ling wrote: +struct det_modes_parameter { +xf86MonPtr DDC; +ddc_quirk_t quirks; +DisplayModePtr * Modes; +Bool rb; +Bool preferred; +int timing_level; +}; Why the double pointer on Modes? (Admittedly, X's love of pointer

Re: How To Disable input driver

On Wednesday 11 February 2009, linux multitouch wrote: Hi I am using Xorg version - 1.5.2 I am developing kernel driver which create /dev/eventX - file. when i insert the kernel driver X11 thinks it's a mouse. how can i configure the X11 to ignore the driver (/dev/eventX) thanks Assuming

Re: [PATCH 8/9] fb: move some code to mi

On Wednesday 11 February 2009, Maarten Maathuis wrote: commit 734b23e5982e171031077a2d5d6b5dc2a12e1a70 should fix the problem. Thanks, Maarten. In the meantime Eric Anholt committed 5009127de7d9527ae329d1c2fbc7283648bde2e6 (http://cgit.freedesktop.org/xorg/driver/xf86-video-

Re: How To Disable input driver

On Wed, Feb 11, 2009 at 08:37:44PM +, Magnus Kessler wrote: On Wednesday 11 February 2009, linux multitouch wrote: Hi I am using Xorg version - 1.5.2 I am developing kernel driver which create /dev/eventX - file. when i insert the kernel driver X11 thinks it's a mouse. how can i

xmodmap: different keys have different keycode semantics?

Hello, I noticed a very strange thing about xmodmap. Apparently, the semantics of the keycode nr = keysyms command depend on the keycode. For example, when I assign the keysyms like this: keycode 25 = 0 1 2 3 4 5 6 7 8 9 keycode 38 = a b c d e f g h i j I get the following results

[PATCH] app/xinit: make startx's $? a useful value

When startx fails to start X, it's most likely xinit that failed. xinit returns a proper return code (1), but that gets clobbed in the startx script by clean-up commands. This patch saves $? from xinit and forces startx to exit with that value. This way, if startx actually fails to start X, $?

[Xlib] Saving state before an unmap

Hi all, Basically I want to unmap a window, fiddle with it a bit (like removing the border, removing the maximize button, etc...) and then remap it. The problem I'm running into is that unmapping the window results in unintended side-effects. Take the _NET_WM_STATE property for example,

Re: [PATCH] glx: Replace broken GLX visual setup with a fixed all mode.

On Wed, 2009-02-11 at 12:07 +, Peter Clifton wrote: On Sun, 2009-02-08 at 13:00 +0100, Eric Anholt wrote: With trying to match depths so that you didn't end up with a depth 24 fbconfig for the 32-bit composite visual, I broke the alpha bits on the depth 24 X visual, which angered

Re: Fedora 10, Belkin KVM, USB Mouse/Keyboard, NVIDIA Card, OpenOffice

On Wed, Feb 11, 2009 at 10:51:25AM -0500, Kevin Johnson wrote: Thanks -- I did just that (after a few trial and errors) and was able to get it to crash: Received signal SIGSEGV, Segmentation fault. XkbStringText (str=0x21 Address 0x21 out of bounds, format=2) at xkbtext.c:526 526

What is the role of drawable parameter in XCreatePixmap()

Hi, We pass a drawable parameter as input while calling XCreatePixmap().Now this drawable can be either a X window Id(which we got from a previous call to XCreateWindow) Or, this drawable could be a X pixmap id(which we got from a previous XCreatePixmap() call). I checked the xlib manual and

Re: [PATCH 1/9] Includes new structures and defined MACRO

Hi ajax based on your suggestion, I will fix them you mentioned in next version. Thanks a lot! Ma Ling On Thu, 2009-02-12 at 03:19 +0800, Adam Jackson wrote: On Wed, 2009-02-11 at 17:12 +0800, Ma Ling wrote: +struct cea_audio_blk { + Uchar descs[3]; +}; I think you have this

Re: [PATCH 4/9] handle detailed timing operation in xf86EdidModes.c

On Thu, 2009-02-12 at 03:30 +0800, Adam Jackson wrote: On Wed, 2009-02-11 at 17:15 +0800, Ma Ling wrote: +struct det_modes_parameter { +xf86MonPtr DDC; +ddc_quirk_t quirks; +DisplayModePtr * Modes; +Bool rb; +Bool preferred; +int timing_level; +}; Why

Re: [PATCH 8/9] handle cea-ext data block and insert mode into mode list.

On Thu, 2009-02-12 at 03:11 +0800, Adam Jackson wrote: On Wed, 2009-02-11 at 17:17 +0800, Ma Ling wrote: +void xf86FetchDataBlock(xf86MonPtr mon, +int ext_type, int data_type, +void *data) +{ +int i; +Uchar *ext; + +if

Re: Xvesa black magic

Apparently xinit was eating a lot of potentially useful output. Anybody able to extract anything meaningful from this session? # Xvesa -mode 0x117 -kb -mouse mouse,/dev/input/mice Int 10h (0x4F10) failed: 0x014F (function call failed) No DPMS Support -1 FreeFontPath: FPE build-ins refcount is 2,

Re: [PATCH 8/9] handle cea-ext data block and insert mode into mode list.

Sorry, please use this one to replace last email. Thanks Ma Ling On Thu, 2009-02-12 at 03:11 +0800, Adam Jackson wrote: On Wed, 2009-02-11 at 17:17 +0800, Ma Ling wrote: +void xf86FetchDataBlock(xf86MonPtr mon, +int ext_type, int data_type, +

Re: Xvesa black magic

Also, for completeness, not that I expect it to be helpful: # Xvesa -mode 0x117 -kb -mouse mouse,/dev/input/mice -keybd keyboard Int 10h (0x4F10) failed: 0x014F (function call failed) No DPMS Support -1 FreeFontPath: FPE build-ins refcount is 2, should be 1; fixing. -- William Tracy

Re: How To Disable input driver

Hi thanks for the fast reply. i want this option because i am developing the kernel driver. when the X11 see a new input device connected. it recognize it like a mouse, and X11 behave wired. I didn't develop any X11 driver. The X11 detect the the device as (type: MOUSE), and if remove

Re: xmodmap: different keys have different keycode semantics?

On Wed, Feb 11, 2009 at 04:19:57PM -0500, Nikolaus Rath wrote: I noticed a very strange thing about xmodmap. Apparently, the semantics of the keycode nr = keysyms command depend on the keycode. Yes. You may find reading about XKB enlightening: http://pascal.tsu.ru/en/xkb/ or