Re: Xinerama cursor problem

2010-06-27 Thread FloraGui
On Friday 25 June 2010 03:07:18 am flora...@viatech.com.cn wrote:

 Dear All:

 

  Does anyone still use Xinerama mode?

 

Yes they do as there are some combinations of system hardware/drivers
and user requirements that sill require the use of xinerama.  For
example if you have a multi monitor system with an Nvidia card using the
nvidia driver and you also do color critical work you MUST use xinerama
since no other supported multi screen setup will allow you to calibrate
the VCGT for each individual screen.

 

 

  Section ServerLayout

 

 Identifier X.org Configured

 

 OptionRandR false

 

 Screen  0  Screen0 0 0

 

 Screen  1  Screen1 RightOf Screen0

 

 Option Xineramaon

 

 InputDeviceMouse0 CorePointer

 

 InputDeviceKeyboard0 CoreKeyboard

 

 EndSection

 

 

 

 If  Screen  1  Screen1 RightOf Screen0,  Screen  1

 Screen1 Below Screen0 the cursor is OK

 

 If  Screen  1  Screen1 LeftOf Screen0, you move cursor to
the

 left, the cursor will abnormal, cursor jump in the edge, can not move


 to center

 

 The xorg print error info:

 

 Backtrace:

 

 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e937b]

 

 1: /usr/bin/X (mieqEnqueue+0x1ab) [0x80e8b6b]

 

 2: /usr/bin/X (xf86PostMotionEventP+0xd2) [0x80c2d02]

 

 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x4ad000+0x48a1) 

 [0x4b18a1]

 

 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x4ad000+0x4b96) 

 [0x4b1b96]

 

 5: /usr/bin/X (0x8048000+0x6d5bf) [0x80b55bf]

 

 6: /usr/bin/X (0x8048000+0x122794) [0x816a794]

 

 7: (vdso) (__kernel_sigreturn+0x0) [0x429400]

 

 8: /usr/bin/X (0x8048000+0x144d5e) [0x818cd5e]

 

 9: /usr/bin/X (0x8048000+0x1441cc) [0x818c1cc]

 

 10: /usr/bin/X (miPointerUpdateSprite+0x172) [0x80a04b2]

 

 11: /usr/bin/X (0x8048000+0x5863d) [0x80a063d]

 

 12: /usr/bin/X (0x8048000+0x170957) [0x81b8957]

 

 13: /usr/bin/X (0x8048000+0x33a2b) [0x807ba2b]

 

 14: /usr/bin/X (0x8048000+0x38a8c) [0x8080a8c]

 

 15: /usr/bin/X (0x8048000+0xe00c2) [0x81280c2]

 

 16: /usr/bin/X (0x8048000+0x103678) [0x814b678]

 

 17: /usr/bin/X (mieqProcessDeviceEvent+0x1e4) [0x80e8744]

 

 18: /usr/bin/X (mieqProcessInputEvents+0x6c) [0x80e87dc]

 

 19: /usr/bin/X (ProcessInputEvents+0x17) [0x80b57e7]

 

 20: /usr/bin/X (0x8048000+0x2a1a0) [0x80721a0]

 

 21: /usr/bin/X (0x8048000+0x1ed7a) [0x8066d7a]

 

 22: /lib/tls/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0x1d0bd6]

 

 23: /usr/bin/X (0x8048000+0x1e961) [0x8066961]

 

 [mi] EQ overflowing. The server is probably stuck in an infinite
loop.

 

 

 

 Does anyone can offer some info about this? Thanks a lot !

 

 BRS

 

 Flora

 

 

On my xinerama system the cursor will some times hang at the left edge
of right screen.  This hangs X and all user input stops working (mouse,
tablet, keyboard..).  It does not happen very often so I have not spent
any time trying to figure out what is causing it.

 

I am running the nvidia driver with a 7950 card.   It has been doing
this for 

some time with different versions of the x server and different
versions of the nvidia driver.

 

Hal

 

Dear Hal:

 

 Thanks a lot for your reply!

 I forgot to say the xorg I used is xorg 1.7.6,  and I encounter
this at every time,  if this happens, the input  (mouse, tablet,
keyboard..) still active, just the cursor can not move to the second
screen center, 

when I using the SW cursor this still happens,  whether can I say there
is some relationship with xorg code?

 

BRS

Flora

 

 

___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Xinerama cursor problem

2010-06-25 Thread FloraGui
Dear All:

 Does anyone still use Xinerama mode?

 Section ServerLayout

Identifier X.org Configured

OptionRandR false

Screen  0  Screen0 0 0

Screen  1  Screen1 RightOf Screen0

Option Xineramaon

InputDeviceMouse0 CorePointer

InputDeviceKeyboard0 CoreKeyboard

EndSection

 

If  Screen  1  Screen1 RightOf Screen0,  Screen  1
Screen1 Below Screen0 the cursor is OK

If  Screen  1  Screen1 LeftOf Screen0, you move cursor to the
left, the cursor will abnormal, cursor jump in the edge, can not move to
center

The xorg print error info:

Backtrace:

0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e937b]

1: /usr/bin/X (mieqEnqueue+0x1ab) [0x80e8b6b]

2: /usr/bin/X (xf86PostMotionEventP+0xd2) [0x80c2d02]

3: /usr/lib/xorg/modules/input/evdev_drv.so (0x4ad000+0x48a1) [0x4b18a1]

4: /usr/lib/xorg/modules/input/evdev_drv.so (0x4ad000+0x4b96) [0x4b1b96]

5: /usr/bin/X (0x8048000+0x6d5bf) [0x80b55bf]

6: /usr/bin/X (0x8048000+0x122794) [0x816a794]

7: (vdso) (__kernel_sigreturn+0x0) [0x429400]

8: /usr/bin/X (0x8048000+0x144d5e) [0x818cd5e]

9: /usr/bin/X (0x8048000+0x1441cc) [0x818c1cc]

10: /usr/bin/X (miPointerUpdateSprite+0x172) [0x80a04b2]

11: /usr/bin/X (0x8048000+0x5863d) [0x80a063d]

12: /usr/bin/X (0x8048000+0x170957) [0x81b8957]

13: /usr/bin/X (0x8048000+0x33a2b) [0x807ba2b]

14: /usr/bin/X (0x8048000+0x38a8c) [0x8080a8c]

15: /usr/bin/X (0x8048000+0xe00c2) [0x81280c2]

16: /usr/bin/X (0x8048000+0x103678) [0x814b678]

17: /usr/bin/X (mieqProcessDeviceEvent+0x1e4) [0x80e8744]

18: /usr/bin/X (mieqProcessInputEvents+0x6c) [0x80e87dc]

19: /usr/bin/X (ProcessInputEvents+0x17) [0x80b57e7]

20: /usr/bin/X (0x8048000+0x2a1a0) [0x80721a0]

21: /usr/bin/X (0x8048000+0x1ed7a) [0x8066d7a]

22: /lib/tls/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0x1d0bd6]

23: /usr/bin/X (0x8048000+0x1e961) [0x8066961]

[mi] EQ overflowing. The server is probably stuck in an infinite loop.

 

Does anyone can offer some info about this? Thanks a lot !

BRS

Flora

___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

undefined symbol:pixman_disable_out_of_bounds_workaround

2009-11-09 Thread FloraGui
Dear All:

   Today, I build xorg-1.7.1.901 in Ubuntu 9.04 want to
replace the Xorg with new version, but when I built over, run startx the
error below have found:

   /usr/bin/X11/X: symbol lookup error: /usr/bin/X11/X:
undefined symbol: pixman_disable_out_of_bounds_workaround

xinit:  Server error.

 

The pixman lib I using is pixman-0.15.20

Does anybody have the same problem?

Thanks a lot!

BRS

 

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Xserver 1.6.0 problem?

2009-04-28 Thread FloraGui
Dear All:

 I now use Xserver 1.6.0, set Disable in Monitor Section 

 Section Monitor

   Identifier 

   ...

   Option Disable  

   Option PreferredMode  1024x768

 EndSection

 

 The device still light on, does it reasonable?

 If anyone know something about it ,  give me some advice.

 Thanks a lot !

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

randr1.3 primary output using?

2009-03-25 Thread FloraGui
Dear All:

Recently I am using RandR1.3, I found a little confuse with RandR1.3
primary output definition.

What is this parameter for?

 

I use the command

 xrandr  --output  VGA  --primary 

I found if the VGA occupied the IGA2, after using the command line
it occupied IGA1, see the info from xrandr --verbose 

Before command 

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2048 x
2048

VGA connected 1024x768+0+0 (0x3e) normal (normal left inverted right x
axis y axis) 352mm x 264mm

Identifier: 0x3a

Timestamp:  584354

Subpixel:   unknown

Clones:

CRTC:   0

CRTCs:  0 1

EDID_DATA:

00005a63133501010101

320d01031d241bbe2abbb8a352469824

0f484c8081998159714f6159a94f

c140c940d140863d00c05100304040a0

13006008111e00ff00333543

3033353030303238300a00fd0032

b41e6118000a20202020202000fc

00473930662b0a2020202020202000bb

TV connected 1024x768+0+0 (0x49) normal (normal left inverted
right x axis y axis) 0mm x 0mm

Identifier: 0x3d

Timestamp:  584354

Subpixel:   unknown

Clones:

CRTC:   1

CRTCs:  0 1

After command

 Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2048 x
2048

CRT connected 1024x768+0+0 (0x3e) normal (normal left inverted right x
axis y axis) 352mm x 264mm

Identifier: 0x3a

Timestamp:  584354

Subpixel:   unknown

Clones:

CRTC:   1

CRTCs:  1 0

EDID_DATA:

00005a63133501010101

320d01031d241bbe2abbb8a352469824

0f484c8081998159714f6159a94f

c140c940d140863d00c05100304040a0

13006008111e00ff00333543

3033353030303238300a00fd0032

b41e6118000a20202020202000fc

00473930662b0a2020202020202000bb

TV connected 1024x768+0+0 (0x49) normal (normal left inverted
right x axis y axis) 0mm x 0mm

Identifier: 0x3d

Timestamp:  584354

Subpixel:   unknown

Clones:

CRTC:   0

CRTCs:  1 0

 

In my opinion, because the crtc is changed we need to redraw the
screen, but actually the screen do not redraw, so I now is a little
confused about the function of this command? what is the right behavior
of the command?

Thanks!

 
Best Regards

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Does xrandr1.3 rotate support panning?

2009-02-20 Thread FloraGui
Dear All:

Recently,  I use xrandr1.3, I use following command:

xrandr  --output  VGA   --panning 1600x1200

the screen can do panning 

then I use xrandr  --output VGA  --rotate left

it can not do panning.

Does xrandr1.3 support rotate panning ?

Thanks!

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

答复: Does libpciaccess support two scre en share one pci clone mode ?

2008-11-17 Thread FloraGui
Dear Ian:
Thanks a lot for your reply!

If you're doing clone mode within one driver, you shouldn't need to map
the device twice.  Map the device memory once and use the same mapping from
both screens.  I'm pretty sure that's how other drviers do it.

Now I use this method to realize it which is just as you said I judge it if I 
mapped once, I will not map it.But I saw the open source of Intel and NV and 
see they place pci_device_map_range(mmio map) in ScreenInit stage. In old xorg 
structure, if in clone mode xorg call ScreenInit twice, we use old structure, 
so if we do nothing here, it will call pci_device_map_range(mmio map)twice and 
the second time will failed . I thought because Intel use xrandr12 structure 
the xorg don't all ScreenInit twice in the clone mode.The xrandr12 always 
build-in
one screen. Ps: I work on S3 Graphic.

-邮件原件-
发件人: Ian Romanick [mailto:[EMAIL PROTECTED] 
发送时间: 2008年11月18日 2:38
收件人: Flora Gui
抄送: xorg@lists.freedesktop.org
主题: Re: Does libpciaccess support two screen share one pci clone mode ?

On Thu, Nov 13, 2008 at 02:52:19PM +0800, [EMAIL PROTECTED] wrote:
  Recently I study libpciaccess, found pci_device_map_range
 function, when map the same physical address and the same size will
 failed. 
 
 If we use libpciaccess and want support two screen which share one
 pci, they are mmio base is the same physical address and the size is the
 same, when the second screeninit goto pci_device_map_range, screeninit
 will failed.

If you're doing clone mode within one driver, you shouldn't need to map
the device twice.  Map the device memory once and use the same mapping from
both screens.  I'm pretty sure that's how other drviers do it.

Just out of curiosity, what device are you working on?

  And we can not light device.
 
  I want to ask two question:
 
  1. Does the libpciaccess support two screen share one pci ?
 
  2. If not support, we can do same issue in 2D driver , but I
 can see the nv and intel do nothing , it confused me a lot.

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Does libpciaccess support two screen share one pci clone mode ?

2008-11-12 Thread FloraGui
Dear All:

 Recently I study libpciaccess, found pci_device_map_range
function, when map the same physical address and the same size will
failed. 

If we use libpciaccess and want support two screen which share one
pci, they are mmio base is the same physical address and the size is the
same, when the second screeninit goto pci_device_map_range, screeninit
will failed.

 And we can not light device.

 

 I want to ask two question:

 1. Does the libpciaccess support two screen share one pci ?

 2. If not support, we can do same issue in 2D driver , but I
can see the nv and intel do nothing , it confused me a lot.



 If anyone know , please help me , thanks a lot !  

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

XRandR rotate support HW rotate or not?

2008-10-31 Thread FloraGui
Dear Keith Packard:

  I have recently study RandR,  I found if we use RandR rotate no matter 
static rotate or dynamic rotate,we always use RandR’s own software rotate.

  We draw the screen desktop very slow,  how can we support HW rotate using 
RandR or it is a RandR limitation, if it is, RandR1.3 has support HW rotate or 
not ?

  Thanks a lot!

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

答复: XRandR rotate support HW rotate or not?

2008-10-31 Thread FloraGui
Dear Alan:
Do you mean we can use damage extension to draw the update screen, so 
the draw speed can up a litter.
But the rotation action still use xrandr's software rotation method, is 
it right?

-邮件原件-
发件人: Alan Hourihane [mailto:[EMAIL PROTECTED] 
发送时间: 2008年10月31日 18:47
收件人: Flora Gui
抄送: xorg@lists.freedesktop.org
主题: Re: XRandR rotate support HW rotate or not?

On Fri, 2008-10-31 at 17:50 +0800, [EMAIL PROTECTED] wrote:
 Dear Keith Packard:
 
   I have recently study RandR,  I found if we use RandR rotate no
 matter static rotate or dynamic rotate,we always use RandR’s own
 software rotate.
 
   We draw the screen desktop very slow,  how can we support HW
 rotate using RandR or it is a RandR limitation, if it is, RandR1.3 has
 support HW rotate or not ?
 
   Thanks a lot!

It is possible to support HW accelerated rotation.

You can use the damage extension to get rectangular regions to do
rotated blits.

You can look at the Intel driver to see how this is done for an example.

Alan.


___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

答复: 答复: XRandR rotate support HW rot ateor not?

2008-10-31 Thread FloraGui
Dear Alan:
If it action like this, what is feature of xrandr?
 Do you mean we could realize some part function of xrandr rotate use 
damage extension?

-邮件原件-
发件人: Alan Hourihane [mailto:[EMAIL PROTECTED] 
发送时间: 2008年10月31日 19:09
收件人: Flora Gui
抄送: xorg@lists.freedesktop.org
主题: Re: 答复: XRandR rotate support HW rotateor not?

You do accelerated drawing to the new offscreen framebuffer, and rotate
blit the damaged regions.

Again, you should look at the intel driver for an example.

Alan.

On Fri, 2008-10-31 at 19:05 +0800, [EMAIL PROTECTED] wrote:
 Dear Alan:
   Do you mean we can use damage extension to draw the update screen, so 
 the draw speed can up a litter.
   But the rotation action still use xrandr's software rotation method, is 
 it right?
 
 -邮件原件-
 发件人: Alan Hourihane [mailto:[EMAIL PROTECTED] 
 发送时间: 2008年10月31日 18:47
 收件人: Flora Gui
 抄送: xorg@lists.freedesktop.org
 主题: Re: XRandR rotate support HW rotate or not?
 
 On Fri, 2008-10-31 at 17:50 +0800, [EMAIL PROTECTED] wrote:
  Dear Keith Packard:
  
I have recently study RandR,  I found if we use RandR rotate no
  matter static rotate or dynamic rotate,we always use RandR’s own
  software rotate.
  
We draw the screen desktop very slow,  how can we support HW
  rotate using RandR or it is a RandR limitation, if it is, RandR1.3 has
  support HW rotate or not ?
  
Thanks a lot!
 
 It is possible to support HW accelerated rotation.
 
 You can use the damage extension to get rectangular regions to do
 rotated blits.
 
 You can look at the Intel driver to see how this is done for an example.
 
 Alan.
 
 

___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg