Nvidia Optimus and hybrid graphics
Is there any plans to develop a Xorg version that supports the latest hardware with hybrid graphics (e.g. Nvidia optimus)? ___ 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
Problems with vmwgfx driver
mwgfx(0): Using default gamma of (1.0, 1.0, 1.0) unless othe wise stated. [37.989] (==) vmwgfx(0): DPI set to (96, 96) [39.087] (II) vmwgfx(0): Initialized VMWARE_CTRL extension version 0.2 [39.103] (II) vmwgfx(0): ## [39.103] (II) vmwgfx(0): # Usefull debugging info follows # [39.103] (II) vmwgfx(0): ## [39.103] (II) vmwgfx(0): Using libkms backend [39.103] (II) vmwgfx(0): 2D Acceleration is disabled [39.104] (II) vmwgfx(0): Fallback debugging is disabled [39.104] (**) vmwgfx(0): 3D Acceleration is disabled [39.104] (==) vmwgfx(0): Swap Throttling is enabled. [39.104] (==) vmwgfx(0): Dirty Throttling is disabled. [39.104] (II) vmwgfx(0): ## [39.105] (==) vmwgfx(0): Backing store disabled [39.116] (==) vmwgfx(0): Silken mouse enabled [39.284] (II) vmwgfx(0): RandR 1.2 enabled, ignore the following RandR disa led message. [39.757] (==) vmwgfx(0): DPMS enabled [41.759] (II) vmwgfx(0): Damage tracking initialized [41.759] (II) vmwgfx(0): Setting screen physical size to 211 x 158 Any hints? Bye Marco ___ 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
Re: Question about snapshots
Em 20-09-2010 13:04, Burton Samograd escreveu: > Benni Stolz writes: > >> Hi, >> >> Im trying to write a small application wich observe a room in my house. >> My resources: >> - USB Webcam >> - Ubuntu Netbook Remix >> >> Is it possible to take a snapshot in the command shell? > > w3cam is a tiny little program that does what you're looking for: > > http://freshmeat.net/projects/w3cam/ > > -- > Burton Samograd http://www.zoneminder.com/screenshots.html http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome -- Marco de Freitas ___ 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
Informations about X11R7.6
Hi team Xorg I just installed ubuntu 10.10alpha 3 and i have a video card SiS Mirage 3 Grapichs. Unfotuntley this is the same bug version video relution(800x600). I knew a few weeks released the new version of Xorg(X11R7.6). This new version will fix this bug??? or as in previous versions of ubuntu, i have to fix this bug by editing Xorg.conf I wait a reply, thank u for attention Marco ___ 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
Re: xinput-calibrator XChangeDeviceProperty calls ignored
Peter Hutterer ha scritto, Il 11/02/2010 00:18: > On Wed, Feb 10, 2010 at 05:28:57PM +0100, Marco Cavallini wrote: >> Simon Thum ha scritto, Il 27/01/2010 13:29: >>> Marco Cavallini wrote: >>>> Simon Thum ha scritto, Il 27/01/2010 11:47: >>>>> Marco Cavallini wrote: >>>>>> Hi, >>>>>> I'm testing and debugging xinput-calibrator and looks like >>>>>> CalibratorEvdev::do_set_prop - XChangeDeviceProperty calls are ignored >>>>>> by Xorg. >>>>> Properties may reject attempts to change their value (to specific >>>>> values). Also, if the properties don't exist before, you may be creating >>>>> them but they don't have any actual meaning. >>>> Simon, >>>> If I see the following properties, should I be able to set an of them? >>> Yeah you should. But it's important to get the value and type right. >>> Citing from evdev-properties.h: >>> /* Run-time calibration */ >>> /* CARD32, 4 values [minx, maxx, miny, maxy], or no values for unset */ >>> #define EVDEV_PROP_CALIBRATION "Evdev Axis Calibration" >>> >>> (you should have this file if you compiled evdev or have a *-dev package) >>> >>> You ought to be getting errors if it doesn't work: >>> >>> si...@simons ~ $ xinput --set-prop 6 "Device Accel Constant Deceleration" -1 >>> X Error of failed request: BadValue (integer parameter out of range for >>> operation) >>> Major opcode of failed request: 139 (XInputExtension) >>> Minor opcode of failed request: 57 () >>> Value in failed request: 0xf3 >>> Serial number of failed request: 17 >>> Current serial number in output stream: 18 >>> >> My calls are successfull and I get back any error. >> I still have no effects on XChangeDeviceProperty calls. >> >> Anybody could point me where to continue digging? >> For instance, where is XChangeDeviceProperty? > > xserver/Xi/xiproperty.c, ProcXChangeDeviceProperty, or if you're using > server 1.7 xinput will likely use XIChangeProperty. that's in the same file, > but called ProcXIChangeProperty. > > that again calls into the property handler, for acceleration properties that > is one of the AccelSet*Property calls in xserver/dix/ptrveloc.c. > for evdev properties, it's EvdevSetProperty in xf86-input-evdev/src/evdev.c. > That's likely where the Error is coming from. > > Can you provide some more detail though, it might be a trivial fix once I > can reproduce it. What's the URL for the calibrator program and what > property are you trying to set? > >> How it manage the raw coordinates coming from /dev/input/touchscreen0 ? > > not quite sure what you mean there. > > Cheers, > Peter Solved Peter, you was right! The problem was caused by double "InputDevice" definition in xorg.conf Removing the mouse device xinput calibrator work smoothly. Thank you all. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xinput settings ignored
Peter Hutterer ha scritto, Il 11/02/2010 00:26: > On Wed, Feb 10, 2010 at 05:35:52PM +0100, Marco Cavallini wrote: >> Hi I am facing to a weird behaviour with my ARM based touchscreen >> device, xinput settings ignored and looks like I have a parallel input >> device. >> >> X.Org X Server 1.7.4 >> >> >> # cat /dev/input/touchscreen0 >> if I touch the screen I can see chars >> >> If I start xorg with >> xinit & >> I can see the graphic application (xterm) and the cursor moves when I >> touch the screen. >> Cursor movements are not calibrated and axes are swapped. >> >> # cat /etc/X11/xorg.conf >> ... >> Section "InputDevice" >> Identifier "atmel-ts" >> Driver "evdev" >> Option "SwapAxes" "1" >> Option "Device" "/dev/input/touchscreen0" >> EndSection >> ... > > Can I assume that the touchscreen talks the event API? because if not, some > interesting behaviour can be expected. > > >> Now, the weird stuff: If I do >> xinput set-int-prop "atmel-ts" "Device Enabled" 8 0 >> the command >> xinput test "atmel-ts" >> doesn't return any coordinate and any event, but the cursor moves on the >> screen. >> >> If I enable the device >> xinput set-int-prop "atmel-ts" "Device Enabled" 8 1 >> the command >> xinput test "atmel-ts" >> works, and the cursor has the same behaviour (not cailbrable) >> >> May these info give you any idea about what's happening? >> Any hint will be appreciated. > > have you disabled hotplugging? chances are the device is added twice, once > as part of the xorg.conf, once through HAL. if you disable the xorg.conf > device, the other one will happily keep sending coordinates. > > Cheers, Peter, you was right! The problem was caused by double "InputDevice" definition in xorg.conf Removing the mouse device xinput calibrator work smoothly. Thank you all. Section "InputDevice" Identifier "atmel-ts" Driver "evdev" Option "SwapAxes" "1" Option "Device" "/dev/input/touchscreen0" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "CorePointer" EndSection Section "ServerLayout" Identifier "Layout" Screen "fbscreen" #InputDevice "Generic Mouse" InputDevice "atmel-ts" "CorePointer" EndSection Cheers -- Marco Cavallini | KOAN sas | Bergamo - Italia embedded and real-time software engineering Atmel third party certified consultant Phone:+39-035-255.235 - Fax:+39-178-22.39.748 http://www.KoanSoftware.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xinput settings ignored
Peter Hutterer ha scritto, Il 11/02/2010 00:26: > On Wed, Feb 10, 2010 at 05:35:52PM +0100, Marco Cavallini wrote: >> Hi I am facing to a weird behaviour with my ARM based touchscreen >> device, xinput settings ignored and looks like I have a parallel input >> device. >> >> X.Org X Server 1.7.4 >> >> >> # cat /dev/input/touchscreen0 >> if I touch the screen I can see chars >> >> If I start xorg with >> xinit & >> I can see the graphic application (xterm) and the cursor moves when I >> touch the screen. >> Cursor movements are not calibrated and axes are swapped. >> >> # cat /etc/X11/xorg.conf >> ... >> Section "InputDevice" >> Identifier "atmel-ts" >> Driver "evdev" >> Option "SwapAxes" "1" >> Option "Device" "/dev/input/touchscreen0" >> EndSection >> ... > > Can I assume that the touchscreen talks the event API? because if not, some > interesting behaviour can be expected. > > >> Now, the weird stuff: If I do >> xinput set-int-prop "atmel-ts" "Device Enabled" 8 0 >> the command >> xinput test "atmel-ts" >> doesn't return any coordinate and any event, but the cursor moves on the >> screen. >> >> If I enable the device >> xinput set-int-prop "atmel-ts" "Device Enabled" 8 1 >> the command >> xinput test "atmel-ts" >> works, and the cursor has the same behaviour (not cailbrable) >> >> May these info give you any idea about what's happening? >> Any hint will be appreciated. > > have you disabled hotplugging? chances are the device is added twice, once > as part of the xorg.conf, once through HAL. if you disable the xorg.conf > device, the other one will happily keep sending coordinates. Hi Peter, I tred removing the touchscreen from xinit.org Results are: 1. touchscreen is still working 2. xinput --list --short no longer detect the touchscreen device 3. and of course xinput-calibrator does not start I'm quite puzzled, why touchscreen is still working? How could I disable the current touch events and replace it with the one defined in xorg.conf? Option "Device" "/dev/input/touchscreen0" TIA /marco ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xinput-calibrator XChangeDeviceProperty calls ignored
Peter Hutterer ha scritto, Il 11/02/2010 00:18: > xserver/Xi/xiproperty.c, ProcXChangeDeviceProperty, or if you're using > server 1.7 xinput will likely use XIChangeProperty. that's in the same file, > but called ProcXIChangeProperty. > > that again calls into the property handler, for acceleration properties that > is one of the AccelSet*Property calls in xserver/dix/ptrveloc.c. > for evdev properties, it's EvdevSetProperty in xf86-input-evdev/src/evdev.c. > That's likely where the Error is coming from. > > Can you provide some more detail though, it might be a trivial fix once I > can reproduce it. What's the URL for the calibrator program and what > property are you trying to set? Hi Peter, thank you for answering. I'm working with Tias on his project http://github.com/tias/xinput_calibrator These settings, and any xinput set-int-prop "atmel-ts" "Evdev Axis Calibration" has no effect. --- # export DISPLAY=:0 # xinput_calibrator Calibrating EVDEV driver for "atmel-ts" current calibration values (from XInput): min_x=150, max_x=3830 and min_y=190, max_y=3830 To make the settings permanent, create add a startup script for your window manager with the following command(s): xinput set-int-prop "atmel-ts" "Evdev Axes Swap" 8 1 xinput set-int-prop "atmel-ts" "Evdev Axis Calibration" 32 3581 1929 -106 1946 Doing dynamic recalibration: Swapping X and Y axis... Setting new calibration data: 3581, 1929, -106, 1946 -- # xinput --list --short Virtual core pointer id=2[master pointer (3)] Virtual core XTEST pointer id=4[slave pointer (2)] Generic Mouse id=6[slave pointer (2)] Virtual core keyboardid=3[master keyboard (2)] Virtual core XTEST keyboard id=5[slave keyboard (3)] id=8[slave keyboard (3)] atmel-tsid=7[floating slave] # xinput --list-props "atmel-ts" Device 'atmel-ts': Device Enabled (112): 1 Device Accel Profile (220): 0 Device Accel Constant Deceleration (221): 1.00 Device Accel Adaptive Deceleration (223): 1.00 Device Accel Velocity Scaling (224):10.00 Evdev Reopen Attempts (229):10 Evdev Axis Inversion (230): 0, 0 Evdev Axis Calibration (231): 1000, 10, 1000, 10 Evdev Axes Swap (232): 1 Axis Labels (233): "Abs X" (226), "Abs Y" (227), "Abs Pressure" (228) Button Labels (234):"Button Unknown" (225), "Button Unknown" (225), "Button Unknown" (225), "Button Wheel U) Evdev Middle Button Emulation (235):2 Evdev Middle Button Timeout (236): 50 Evdev Wheel Emulation (237):0 Evdev Wheel Emulation Axes (238): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (239):10 Evdev Wheel Emulation Timeout (240):200 Evdev Wheel Emulation Button (241): 4 Evdev Drag Lock Buttons (242): 0 Cheers -- Marco Cavallini | KOAN sas | Bergamo - Italia embedded and real-time software engineering Atmel third party certified consultant Phone:+39-035-255.235 - Fax:+39-178-22.39.748 http://www.KoanSoftware.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
xinput settings ignored
Hi I am facing to a weird behaviour with my ARM based touchscreen device, xinput settings ignored and looks like I have a parallel input device. X.Org X Server 1.7.4 # cat /dev/input/touchscreen0 if I touch the screen I can see chars If I start xorg with xinit & I can see the graphic application (xterm) and the cursor moves when I touch the screen. Cursor movements are not calibrated and axes are swapped. # cat /etc/X11/xorg.conf ... Section "InputDevice" Identifier "atmel-ts" Driver "evdev" Option "SwapAxes" "1" Option "Device" "/dev/input/touchscreen0" EndSection ... Now, the weird stuff: If I do xinput set-int-prop "atmel-ts" "Device Enabled" 8 0 the command xinput test "atmel-ts" doesn't return any coordinate and any event, but the cursor moves on the screen. If I enable the device xinput set-int-prop "atmel-ts" "Device Enabled" 8 1 the command xinput test "atmel-ts" works, and the cursor has the same behaviour (not cailbrable) May these info give you any idea about what's happening? Any hint will be appreciated. TIA /marco ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xinput-calibrator XChangeDeviceProperty calls ignored
Simon Thum ha scritto, Il 27/01/2010 13:29: > Marco Cavallini wrote: >> Simon Thum ha scritto, Il 27/01/2010 11:47: >>> Marco Cavallini wrote: >>>> Hi, >>>> I'm testing and debugging xinput-calibrator and looks like >>>> CalibratorEvdev::do_set_prop - XChangeDeviceProperty calls are ignored >>>> by Xorg. >>> Properties may reject attempts to change their value (to specific >>> values). Also, if the properties don't exist before, you may be creating >>> them but they don't have any actual meaning. >> Simon, >> If I see the following properties, should I be able to set an of them? > Yeah you should. But it's important to get the value and type right. > Citing from evdev-properties.h: > /* Run-time calibration */ > /* CARD32, 4 values [minx, maxx, miny, maxy], or no values for unset */ > #define EVDEV_PROP_CALIBRATION "Evdev Axis Calibration" > > (you should have this file if you compiled evdev or have a *-dev package) > > You ought to be getting errors if it doesn't work: > > si...@simons ~ $ xinput --set-prop 6 "Device Accel Constant Deceleration" -1 > X Error of failed request: BadValue (integer parameter out of range for > operation) > Major opcode of failed request: 139 (XInputExtension) > Minor opcode of failed request: 57 () > Value in failed request: 0xf3 > Serial number of failed request: 17 > Current serial number in output stream: 18 > My calls are successfull and I get back any error. I still have no effects on XChangeDeviceProperty calls. Anybody could point me where to continue digging? For instance, where is XChangeDeviceProperty? How it manage the raw coordinates coming from /dev/input/touchscreen0 ? TIA /marco ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: FOSDEM DevRoom schedule updated.
Luc Verhaegen ha scritto, Il 22/01/2010 02:56: > http://wiki.x.org/wiki/fosdem2010 > > The current schedule (as it will be printed in the booklet too): > > * 10.00: ... > * 11.00: ... > * 12.00: ... > * 13.00: Daniel Stone : Polishing X11 and making it shiny. > * 14.00: Luc Verhaegen : The free software desktop’s graphics driver > stack. > * 15.00: Jerome Glisse : GPU Userspace - kernel interface & Radeon > kernel modesetting status. > * 16.00: Mikhail Gusarov : X on e-Paper. > > I'm sure that the DevRoom will be brimmed when there are talks, but the > FOSDEM organizers are not exactly thrilled with the coverage on even a > single day, and I don't think that we will get a 6th devroom next year. > > Anyway, hope to meet some of you there. Mail me for contact info for > friday evening supper meet-up on the grand place. > Unfortunately I have to leave Brussels on Sunday at 14:00 but I hope to meet some of you at the Beer event and/or during any other session. BTW I should stay the most of the time at OpenEmbedded stand. Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen -- Marco Cavallini | KOAN sas | Bergamo - Italia embedded and real-time software engineering Phone:+39-035-255.235 - Fax:+39-178-22.39.748 http://www.KoanSoftware.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: evdev touchscreen calibration problems
Abelenda ha scritto, Il 01/02/2010 17:18: > Hi, > > I have a little problem calibrating my touchscreen using xinput. > > I can invert the Y axis no problem, suppress acceleration, but there is > no way to get calibration right it seems that the numbers I put do not > influence the pointer. > > for example I execute : > xinput set-int-prop 6 238 32 500 600 200 300 > or > xinput set-int-prop 6 238 32 20 100 30 50 > I am facing exactly to the same problem here with my ARM based board. Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen -- Marco Cavallini | KOAN sas | Bergamo - Italia embedded and real-time software engineering Atmel third party certified consultant Phone:+39-035-255.235 - Fax:+39-178-22.39.748 http://www.KoanSoftware.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xserver - Touchscreen
balakrishnan ha scritto, Il 01/02/2010 11:50: > Hi, >I am building "stable/2009" angstrom-distro branch in open embedded. > What is my problem is I am not able to enable 'touch screen'. I have > added "touchscreen" value in MACHINE_FEATURES variable also. > My configuration details is > > PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg" > XSERVER = "xserver-xorg \ >xf86-input-evdev \ >xf86-input-mouse \ >xf86-video-fbdev \ >xf86-input-keyboard" > MACHINE_FEATURES = "kernel26 usbgadget usbhost vfat alsa touchscreen" > > 1.How to enable touch screen in "xserver-xorg" configuration?. > 2.whether it is possible in xserver-kdrive? > > With Regards > J.Balakrishnan > > ___ Hi, I am currently working on xinput-calibrator integration into OpenEmbedded (so consequently into Angstrom and KaeilOS) http://www.angstrom-distribution.org/ http://www.kaeilos.com/ (mantained by me) Both these two distributions uses xserver-xorg rather than the old xserver-kdrive, so please try enabling xinput-calibrator in your image recipe in order to include xinput-calibrator_0.5.0.bb Please let me know how is it working on your side, posting here, in IRC #oe or by private mail. Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen -- Marco Cavallini | KOAN sas | Bergamo - Italia embedded and real-time software engineering Atmel third party certified consultant Phone:+39-035-255.235 - Fax:+39-178-22.39.748 http://www.KoanSoftware.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xinput-calibrator XChangeDeviceProperty calls ignored
Simon Thum ha scritto, Il 27/01/2010 11:47: > Marco Cavallini wrote: >> Hi, >> I'm testing and debugging xinput-calibrator and looks like >> CalibratorEvdev::do_set_prop - XChangeDeviceProperty calls are ignored >> by Xorg. > Properties may reject attempts to change their value (to specific > values). Also, if the properties don't exist before, you may be creating > them but they don't have any actual meaning. Simon, If I see the following properties, should I be able to set an of them? I ask because I get no effect. # xinput --list-props "atmel-ts" Device 'atmel-ts': Device Enabled (112): 1 Device Accel Profile (220): 0 Device Accel Constant Deceleration (221): 1.00 Device Accel Adaptive Deceleration (223): 1.00 Device Accel Velocity Scaling (224):10.00 Evdev Reopen Attempts (229):10 Evdev Axis Inversion (230): 0, 0 Evdev Axis Calibration (231): Evdev Axes Swap (232): 1 Axis Labels (233): "Abs X" (226), "Abs Y" (227), "Abs Pressure" (228) Button Labels (234):"Button Unknown" (225), "Button Unknown" (225), "Button Unknown" (225), "Button Wheel U) Evdev Middle Button Emulation (235):2 Evdev Middle Button Timeout (236): 50 Evdev Wheel Emulation (237):0 Evdev Wheel Emulation Axes (238): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (239):10 Evdev Wheel Emulation Timeout (240):200 Evdev Wheel Emulation Button (241): 4 Evdev Drag Lock Buttons (242): 0 TIA /marco ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
xinput-calibrator XChangeDeviceProperty calls ignored
Hi, I'm testing and debugging xinput-calibrator and looks like CalibratorEvdev::do_set_prop - XChangeDeviceProperty calls are ignored by Xorg. I wonder who is responsible of touchscreen coords adjustment. Does exist a documentation about the flow beginning from touching the screen up to X cursor moving on the screen? Which are the libraries involved into this operation? TIA /marco ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
TouchScreen calibration fails with xinput_calibrator
Hi, With precious help from Tias I am testing and debugging xinput and xinput_calibrator on my custom ARM based board. Some information of my system X.Org X Server 1.7.3 Release Date: 2009-12-3 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-2-amd64 x86_64 Current Operating System: Linux PM9263 2.6.28 #1 Thu Nov 19 18:00:34 CET 2009 armv5tejl Package: xinput Version: 1.5.0-r0.5 Package: xinput-calibrator Version: 0.5.0-r1.5 # xinput --list --short Virtual core pointer id=2[master pointer (3)] Virtual core XTEST pointer id=4[slave pointer (2)] Generic Mouse id=6[slave pointer (2)] Virtual core keyboardid=3[master keyboard (2)] Virtual core XTEST keyboard id=5[slave keyboard (3)] id=8[slave keyboard (3)] atmel-ts id=7[floating slave] I am able to run xinput-calibrator but looks like the new settings are ignored # xinput_calibrator Calibrating EVDEV driver for "atmel-ts" To make the settings permanent, create add a startup script for your window manager with the following command(s): xinput set-int-prop "atmel-ts" "Evdev Axes Swap" 8 1 xinput set-int-prop "atmel-ts" "Evdev Axis Calibration" 32 2016 508 -145 3564 Doing dynamic recalibration: Swapping X and Y axis... Setting new calibration data: 2016, 508, -145, 3564 In the next step I run xinput test "atmel-ts" then I touched the screen in the 4 corners Up-Left, Up-Right, Bottom-Left, Bottom-Right # xinput test "atmel-ts [UL] motion a[0]=651 a[1]=626 a[2]=7500 [UR] motion a[0]=3345 a[1]=713 a[2]=7500 [BL] motion a[0]=595 a[1]=3317 a[2]=7500 [BR] motion a[0]=558 a[1]=3361 a[2]=7500 If I play with xinput set-int-prop the coordinates from xinput test change xinput set-int-prop "atmel-ts" "Evdev Axis Calibration" 32 800 190 2000 3300 so looks like everything works, but my cursor behaviour is always the same (wrong). What could I test? Any hint would be appreciated. TIA Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen -- Marco Cavallini | KOAN sas | Bergamo - Italia embedded and real-time software engineering Atmel third party certified consultant Phone:+39-035-255.235 - Fax:+39-178-22.39.748 http://www.KoanSoftware.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg-1.7.3 XCALIBRATE touchscreen
Dan Nicholson ha scritto, Il 15/01/2010 19:17: > > The config.log says that you don't have the XCALIBRATE extension built > into the server. > > XCALIBRATE_TRUE='#' > > That means the automake conditional to build the xcalibrate sources > will be false. So, you'll have to run configure again and see what it > says about finding the xcalibrate dependencies. Looks like configure.ac wants KDRIVE in order to enable xcalibrate, isn't it? if test "x$XCALIBRATE" = xyes && test "$KDRIVE" = yes; then AC_DEFINE(XCALIBRATE, 1, [Build XCalibrate extension]) REQUIRED_MODULES="$REQUIRED_MODULES $XCALIBRATEPROTO" else XCALIBRATE=no fi AM_CONDITIONAL(XCALIBRATE, [test "x$XCALIBRATE" = xyes]) What do you suggest to do? TIA - /marco ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg-1.7.3 XCALIBRATE touchscreen
Dan Nicholson ha scritto, Il 15/01/2010 18:38: > On Fri, Jan 15, 2010 at 9:25 AM, Marco Cavallini > wrote: >> Hi, >> I am using an ARM based architecture and I am trying to enable >> touchscreen calibration without success. >> I built Xorg version Xorg-1.7.3 configured with --enable-xcalibrate >> but I didn't get this extension in my Xorg, so when I try to call xtscal >> I get this error: >> # xtscal >> XCALIBRATE extension missing: Success >> >> I debugged a bit the following packages (xtscal_0.6.3, >> libxcalibrate_git, libxext_1.1.1) and I realized that the problem is >> into Xorg so I wonder how could I enable XCALIBRATE. >> >> Any help would be greatly appreciated. >> If any functionality is missing I'd like to get a hint about how to >> proceed to implement, debug and test it. > > Can you post Xorg.log? Did configure give you any messages about > xcalibrate when you used --enable-xcalibrate? > > -- Dan, thank you for answering. Now I'm at home and I haven't access to the target machine, but I can pastebin you the config.log : http://pastebin.com/m4ecd3f48 If you really need Xorg.log I could send it to you tomorrow morning. Thank you Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen -- Marco Cavallini | KOAN sas | Bergamo - Italia embedded and real-time software engineering Phone:+39-035-255.235 - Fax:+39-178-22.39.748 http://www.KoanSoftware.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Xorg-1.7.3 XCALIBRATE touchscreen
Hi, I am using an ARM based architecture and I am trying to enable touchscreen calibration without success. I built Xorg version Xorg-1.7.3 configured with --enable-xcalibrate but I didn't get this extension in my Xorg, so when I try to call xtscal I get this error: # xtscal XCALIBRATE extension missing: Success I debugged a bit the following packages (xtscal_0.6.3, libxcalibrate_git, libxext_1.1.1) and I realized that the problem is into Xorg so I wonder how could I enable XCALIBRATE. Any help would be greatly appreciated. If any functionality is missing I'd like to get a hint about how to proceed to implement, debug and test it. Thank you # xdpyinfo name of display::0.0 version number:11.0 vendor string:The X.Org Foundation vendor release number:10703000 X.Org version: 1.7.3 maximum request size: 16777212 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, LSBFirst, 32 image byte order:LSBFirst number of supported pixmap formats:7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: PointerRoot number of extensions:21 BIG-REQUESTS Composite DAMAGE DOUBLE-BUFFER DPMS Generic Event Extension MIT-SCREEN-SAVER MIT-SHM RANDR RENDER SHAPE SYNC X-Resource XC-MISC XFIXES XFree86-DGA XFree86-VidModeExtension XInputExtension XKEYBOARD XTEST XVideo default screen number:0 number of screens:1 screen #0: print screen:no dimensions:240x320 pixels (64x85 millimeters) resolution:95x96 dots per inch depths (7):15, 1, 4, 8, 16, 24, 32 root window id:0x43 depth of root window:15 planes number of colormaps:minimum 1, maximum 1 default colormap:0x20 default number of colormap cells:32 preallocated pixels:black 0, white 32767 options:backing-store NO, save-unders NO largest cursor:240x320 current input event mask:0x0 number of visuals:2 default visual id: 0x21 visual: visual id:0x21 class:TrueColor depth:15 planes available colormap entries:32 per subfield red, green, blue masks:0x1f, 0x3e0, 0x7c00 significant bits in color specification:8 bits visual: visual id:0x41 class:TrueColor depth:32 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen -- Marco Cavallini | KOAN sas | Bergamo - Italia embedded and real-time software engineering Atmel third party certified consultant Phone:+39-035-255.235 - Fax:+39-178-22.39.748 http://www.KoanSoftware.com ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Cairo with glitz backend
On Wed, Mar 4, 2009 at 10:02 AM, Chris Wilson wrote: > So currently aside from glitz, there are experiments to show that simply > doing basic compositing using OpenGL can be much faster than XRender: > http://cgit.freedesktop.org/~anholt/cairo/log/?h=gl and > http://cgit.freedesktop.org/~ickle/cairo/log/?h=opengl A slightly more > ambitious (though it does have quite a few fundamental flaws of its own, > chiefly among those is that he hasn't asked anyone from the cairo > community to review it...) > http://github.com/akyrtzi/cairo-gral/tree/master And my favourite > (slightly biased since I'm the author ;-) is an example of what you can > achieve with direct rendering: > http://cgit.freedesktop.org/~ickle/cairo/log/?h=drm which, I claim, is > just about as fast as you can make cairo on an eee/i915. (I welcome any > patches to make it, and cairo, even faster :-) The discussion was intriguing, so i tried your latest cairo with drm backend (http://cgit.freedesktop.org/~ickle/cairo/log/?h=drm) because I have an i915 chipset (GM45). Recompiled all the stuff with --enable-drm --enable-xlib-xrender --enable-dri2 --enable-gl with my brand new intel video drivers(2.6.3) with UXA on top of libdrm 2.4.5 I have to say that I thougth there would be a boost for all gnome applications, but I hardly see any difference from cairo (1.8.6) standard (debian packaging). I remember passing from standard backends to glitz showed a great performance boost. How i could be sure cairo is using drm backend (apart the fact that libcairo is linked with libdrm)? Are there any tests I could check to see how fast is cairo with drm backend? Anyway I think these new works about cairo backends coul be very primising. Thanks for your work. Marco ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xf86-video-intel memory leakage
>> Anyway the problem appears only with UXA , with EXA I could start >> Xorg, but have no direct rendering. > But that seems to be more due to some missing visuals, isn't it? Exactly. Bye Marco ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xf86-video-intel memory leakage
I have xf86-video-intel master from git and kernel 2.6.29-rc3 at commit b1792e367053968f2ddb48bc911d314143ce6242. I have to say that I also merged wirless-testing and drm-airlied/drm-fixes (Merge: 9ceb716... ac048e1...) Anyway the problem appears only with UXA , with EXA I could start Xorg, but have no direct rendering. My card is (from Xorg.log): (**) intel(0): Option "AccelMethod" "UXA" (II) intel(0): Integrated Graphics Chipset: Intel(R) 945GM (--) intel(0): Chipset: "945GM" Bye Marco On Sat, Feb 7, 2009 at 9:17 PM, Johannes Engel wrote: > Marco schrieb: >> Same for me, starting iceweasel on my GM45 bump suddenly out of swap. >> >> Bisected to: >> deneb:~/src/xf86-video-intel.git# git bisect view >> commit 8d4bc36fae50b09a73ba2cfab920adb32141a358 >> Author: Jesse Barnes >> Date: Mon Jan 26 17:14:06 2009 -0800 >> >> Support tiled back/depth on 915-class hardware with DRI2. >> >> Set alignments, tile settings and flags correctly in the 2D driver to >> suppor >> tiled rendering. UXA's create pixmap function currently assumes the >> worst >> about the alignment constraints; that should probably be fixed. Some of >> the >> 1M alignment fixes could probably be done more cleanly as well. >> (END) >> >> >> In fact after reverting it, all seems fine. > I can confirm that for my 945GM. > Don't know if that is really the culprit or just what makes another > error more obvious... > > Cheers, Johannes > ___ > xorg mailing list > xorg@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/xorg > ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: xf86-video-intel memory leakage
Same for me, starting iceweasel on my GM45 bump suddenly out of swap. Bisected to: deneb:~/src/xf86-video-intel.git# git bisect view commit 8d4bc36fae50b09a73ba2cfab920adb32141a358 Author: Jesse Barnes Date: Mon Jan 26 17:14:06 2009 -0800 Support tiled back/depth on 915-class hardware with DRI2. Set alignments, tile settings and flags correctly in the 2D driver to suppor tiled rendering. UXA's create pixmap function currently assumes the worst about the alignment constraints; that should probably be fixed. Some of the 1M alignment fixes could probably be done more cleanly as well. (END) In fact after reverting it, all seems fine. Bye ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
