[ANNOUNCE] xf86-input-evdev 2.1.99.1

[Peter Hutterer]

First snapshot for evdev 2.2.

Lots of cleanup, and - most notably - general axis/button support.
For those running an X server from master, evdev will label axes and buttons
for you.

shortlog is a bit longer than it actually is, it includes a number of patches
that were cherry-picked onto 2.1 and have since been released.

Cheers,
  Peter

Shortlog since xf86-input-evdev-2.1.0:

Adam Jackson (3):
  Open with O_NONBLOCK, and simplify EvdevReadInput to match.
  Move relative motion and other magic up to EV_SYN processing.
  Reduce the number of read calls in ReadInput.

Alan Coopersmith (2):
  Remove xorgconfig & xorgcfg from See Also list in man page
  Add README with pointers to mailing list, bugzilla & git repos

Bryce Harrington (1):
  Add descriptive messages for device-has-changed errs

Dan Nicholson (2):
  Stop hammering XKB defaults
  Really fix distcheck

Daniel Stone (1):
  Keyboard: Disable kernel autorepeat

Fernando Carrijo (1):
  Fix error message

Julien Cristau (1):
  Fix TestBit() on 64bit

Julien Plissonneau Duquene (1):
  EvdevCacheCompare: ignore changes in current device position

Matt Helsley (4):
  Add pressure valuator
  rename NBITS to NLONGS to reflect its actual meaning
  Fix FOO_MAX off-by-one
  General axis valuator support.

Michael Chapman (1):
  Disable middle mouse button emulation when a middle mouse button event is 
registered

Paulo Cesar Pereira de Andrade (1):
  Janitor: make distcheck, .gitignore.

Peter Breitenlohner (1):
  fix manpage formatting

Peter Hutterer (64):
  Bump to 2.1.99.
  Document InvertX/Y options.
  Document properties in man page.
  Add property support for ReopenAttempts option.
  Janitor: clean up xf86Msg use, might as well use X_CONFIG directly.
  Clean up program flow - don't call PreInit for "modules" on DEVICE_INIT.
  Register property handler from within the modules, not the main evdev 
file.
  Rename DragLockInit to DragLockPreInit, remove superfluous "return".
  Tidy up evdev.h
  Don't include the client-side header anymore. xkbstr.h is server SDK.
  8-bit properties should use 8-bit storage types...
  Don't init draglock, etc. if we don't have the required capabilities.
  Fix "Device reopened after N attempts" message.
  Don't post keycodes > 255.
  Add option "GrabDevice", don't grab the device by default.
  Init ioctl bitmasks to 0, shuts up valgrind too.
  MB emulation timeout is stored as Time, make the property 32-bit too.
  Silence compiler warning by memsetting the struct properly.
  emulate MB: fix confusing log message.
  Fix axis inversion for absolute coordinates.
  emuMB: add EvdevMBEmuOn and call from EvdevOn to register wakeup handlers.
  Flush input after re-opening the fd.
  Remove obsolete FIXME
  Treat BTN_[0-2] as LMR buttons if necessary.
  Add test/ directory for uinput-based test devices.
  Add support for run-time calibration.
  Add support for axes swapping.
  Store device file's minor/major to avoid duplicate devices.
  Finalize MB emu (and wakeup handlers) before closing the fd.
  Add dummy test device - simple device that doesn't move at all.
  Test for pressure BEFORE using has_pressure.
  Register the property handler AFTER setting all the properties.
  Don't print xkb options twice to the log file.
  Add automatic axis labeling.
  Require XKB.
  Deal with XINPUT ABI 5.
  Reshuffle property initialization.
  Protect against zero-sized property values. #19882
  Remove useless include directive.
  Remove duplicate MB emu finalization.
  Remove superfluous motion history allocation.
  Log which EVIOCGABS ioctl failed.
  Remove unused 'screen' variable from the EvdevRec.
  Change cached bitmasks from long to unsigned long.
  CacheCompare before probing the device.
  Swap axes after scaling, not before.
  man: Fix two minor typos in man page.
  man: list the options and properties in alphabetical order.
  remove duplicate (code > 255) check.
  Add dynamic axis labelling for absolute devices.
  Add generic axis support for relative axes.
  Remove superfluous (and duplicate) call to xf86MotionHistoryAllocate.
  Add support for arbitrary relative axis labels.
  Accommodate for holes in the ABS label defines.
  Label axes conditional on actual support.
  Revert "Remove useless include directive."
  Split ReadInput into ReadInput and ProcessEvent.
  Pass on all relative events, not just x/y.
  Ignore REL_WHEEL, REL_HWHEEL and REL_DIAL during axis initialisation.
  If scrollwheels are found, bump the button number by 4 (or up to 7).
  Don't double-assign the UKNOWN axis label.
  Rename prop_label to prop_axis_label.
  Add support for button labelling.
  evdev 2.1.99.1

Sascha Hlusiak (2):
  

visual and PictFormat related question

[Alexei Babich]

Hello, all.

xdpyinfo shows, that my X-server supports two visuals: 24 and 32 bits (visuals 
IDs is: 0x21, 0x39); I aim to apply 'PictStandardARGB32' PictFormat to the 
windows.
Visual having ID 0x39 is suitable for this type of PictFormat.
But default visual of the root window is 0x21, so when I try to create windows 
with 0x39 visual, the root window as a parent, I always get a BadMatch error.
Should I change default visual for the root window? If so, how can I do that? 
If no, how shold I use 'PictStandardARGB32' PictFormat with the windows?

Thank you in advance!

-- 
Regards,
Alexei Babich, circuit engineer, OOO NPP "Rezonans", Chelyabinsk, Russia
http://www.rez.ru
Jabber ID: imp...@jabber.ru
name of display::1.0
version number:11.0
vendor string:The X.Org Foundation
vendor release number:7020
X.Org version: 7.2.0
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 4, 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:29
BIG-REQUESTS
Composite
DAMAGE
DEC-XTRAP
DOUBLE-BUFFER
DPMS
Extended-Visual-Information
GLX
MIT-SCREEN-SAVER
MIT-SHM
MIT-SUNDRY-NONSTANDARD
RANDR
RECORD
RENDER
SECURITY
SGI-GLX
SHAPE
SYNC
TOG-CUP
X-Resource
XAccessControlExtension
XC-APPGROUP
XC-MISC
XFIXES
XFree86-Bigfont
XInputExtension
XKEYBOARD
XTEST
XVideo
default screen number:0
number of screens:1

screen #0:
  dimensions:800x480 pixels (212x127 millimeters)
  resolution:96x96 dots per inch
  depths (7):1, 4, 8, 15, 16, 24, 32
  root window id:0x3b
  depth of root window:24 planes
  number of colormaps:minimum 1, maximum 1
  default colormap:0x20
  default number of colormap cells:256
  preallocated pixels:black 0, white 16777215
  options:backing-store NO, save-unders NO
  largest cursor:800x480
  current input event mask:0x0
  number of visuals:2
  default visual id:  0x21
  visual:
visual id:0x21
class:TrueColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x39
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
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: Preferred way to create & insert input events?

[Peter Hutterer]

On Fri, Feb 27, 2009 at 04:33:36PM -0700, Chris Riddoch wrote:
> I'm working on some accessibility software that will enter events into
> X, and have had some difficulty finding the appropriate APIs to use to
> do so. I've looked at some existing software (cellwriter, easystroke,
> xvkbd, etc.) and it seems like this is a relatively tricky thing to
> do.

XTestFakeInput or create a device through uinput.
 
> I've learned quite a bit about the uinput kernel module, but I haven't
> figured out how to determine how it's been mapped to another key
> before it gets to the application, or how to get at the mapping from
> scancodes to keycodes, or even whether that's where I should be trying
> to hook in, in the first place.  I have an old copy of O'Reilly's Xlib
> programming manual, volume 1, from 1995, but I'm sure things have
> moved on since then and there's a preferred way to generate input
> events in software in modern X.

scancode -> keysym is mostly done in xkb. if you're using uinput, just make
sure you post the right keycodes as defined in linux/input.h through the
device.

Same with XTestFakeInput keycodes, as long as you have the evdev ruleset
(xkeyboard-config 1.4 and later)

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

Re: [Question]LED status control over Caps Lock key

[Peter Hutterer]

On Thu, Feb 26, 2009 at 08:12:41PM +0900, Kan-I Jyo wrote:
> Dear list,
> 
> Under normal circumstance, the LED lights up and down whenever
> pressing caps lock key only
> or "shift + caps_lock".
> 
> It is my intention to make it only light up the LED when "shift +
> caps_lock" is pressed.
> 
> By doing some goggling, there are pages says that setting following
> two options in xorg.conf
> would make the magic.
> 
> 
> ... snip ...
> Option "XkbTypes" "complete"
> Option "XkbCompat" "complete+japan"
> ... snip ...
> 
> However, in my case, it is not the "shift + caps_lock" but "caps_lock"
> only to light up
> the caps_lock LED.
> 
> Is there a way to make the behaviour fit my wish?
> 
> Any comment would be greatly appreciated.
> 
> By the way, "$ man 4 kbd" does not mention about the above two options.
> Is there any document describes them?

this is handled by xkb magic, and the file that describes what happens is
assembled from the xkeyboard-config data files.
look through /usr/share/X11/xkb/rules/evdev, these are all the rules you can
apply with setxkbmap. There's some that change the behaviour of the scroll
lock LED, maybe there's one that does what you need.

http://who-t.blogspot.com/2008/09/rmlvo-keyboard-configuration.html
has a bit of an overview what those files are..
If not, you'll have to play around with the xkb compat options.

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

Re: How to build entirety of Xorg 7.4 from source

[Florian Lier]

Hey


You hints are excellent. I will try themout over the
next few days. And yes, I am building from scratch!
BTW, what do you mean by bleeding edge X?
I have no idea what features/modules/components
would constitute a bleeding edge X.


*Bleeding edge* is a term that refers to technology 
 that is so new (and thus, 
presumably, not perfected) that the user is required to risk reductions 
in stability and productivity in order to use it^[1] 
 . It also 
refers to the tendency of the latest technology to be extremely 
expensive. [wikipedia]



I guess Xi2.0 is such a module :)

cheers, fl0



Cheers,

JD

Florian Lier wrote:

hey jd,

No problem
I guess "the rt2860 wifi mini-pci" driver won't be affected by 
building a xserver ^^


"ATI Mobility Radeon 9600"  I guess the latest driver from the git 
works fine (but

you better ask here or google first)

"How do you suggest I install 7.4 (once I build it) - I mean
do I first uninstall my existing X (on which so many packages
depend), and then install 7.4?"

You don't need to replace or uninstall your "old" xserver,
as you might have noticed the script builds the server
here: PREFIX="/opt/gfx-test" which means you can
start the sever like that:


  1.

  rmmod i915 /# assuming you're using Intel/

  2.

  rmmod drm

  3.

  insmod ///linux-core/drm.ko

  4.

  insmod ///linux-core/i915.ko

  5.

  export LD_LIBRARY_PATH=/opt/gfx-test/lib

  6.

  startx -- /opt/gfx-test/bin/Xorg -verbose /# make sure you have
  a ~/.xinitrc with what you want to run/


If the server works fine you can set the new xorg stack as your 
default x-server. I won't recommend you
setting a "bleeding edge" X as default (btw, it won't startup atm 
have a look @ xorg tinderbox).
I don't know that much about Fedora, but I installed FC10 lately from 
a live cd which works fine for me...

Do you want to compile it from scratch?

Cheers, Florian



JD wrote:

Hi Florian,
and thank you very much for your response.
I have a Fedora FC7 notebook.  with 2 cruicial drivers
that I had struggled a lot to make  them work; namely,
the rt2860 wifi mini-pci card from Ralink Technology, and
the ATI Mobility Radeon 9600.
The modification that have been made to these drivers in
their latest incarnations, do not work for me.

How do you suggest I install 7.4 (once I build it) - I mean
do I first uninstall my existing X (on which so many packages
depend), and then install 7.4? I am afraid that the dependencies
will be broken, and many if not most graphical packages
will stop working.

Best regards,

JD


Florian Lier wrote:

Hey JD,

there's a little script on the Xorg / git development site.

http://www.x.org/wiki/Development/git

You can copy and paste the script into a myxorgscript.sh (chmod +x 
it )
You can start building X like that (in console): sh myxorgscript 
init | build | update


Depending on what distri you're using you'll need a bunch of 
dependencies.

If you're on Ubuntu I can help you out...


DEPS="\autoconf automake xserver-xorg-dev libdrm-dev 
build-essential libxxf86vm-dev libxdamage-dev libxfixes-dev 
libxfixes3 expat libexpat-dev libtool autobook \
libxinerama1 libxinerama-dev libxkbfile-dev libxkbfile1 openssl 
libssl-dev xkbsel x11-xkb-utils libxfont1 libxfont-dev git-core 
gawk libxt-dev \
xdebconfigurator autoconf-doc libhal-dev libdbus-1-dev 
libxcomposite-dev libpng12-dev libsm-dev libxrandr-dev \
libxdamage-dev libxinerama-dev libstartup-notification0-dev 
libgconf2-dev libgl1-mesa-dev libglu1-mesa-dev libmetacity-dev 
librsvg2-dev libdbus-1-dev \
libdbus-glib-1-dev libgnome-desktop-dev 
libgnome-window-settings-dev gitweb curl intltool libxslt1-dev 
xsltproc libwnck-dev python-dev libX11-xcb-dev \
pyrex-mode python-pyrex x11proto-scrnsaver-dev libxss-dev 
libprotobuf0 libprotobuf-dev protobuf-compiler gperf xmlto 
libglut3-dev freeglut3-dev \

freeglut-dev libglu1-mesa-dev libglu1-mesa"


(this is if you want to build compiz too)


I hope this helps.

cheers florian

JD wrote:

Dear Developers of Xorg

I wanted to build the entirety of X 7.4 frm source, but when
I saw that it is made up of individual tarballs, I decided to
write and ask if there is a single tarball of everything,
with a top level configure ...etc to build the whole thing.

I searched the FAQ for a "how to build X" or just "how to build"
but came up empty.

Thanx for any info to show how to build the whole 7.4 X system.

Best Regards,

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

  








begin:vcard
fn:Florian Lier
n:Lier;Florian
org:;AG AI | so far
adr:;;Germany
email;internet:f...@icram.de
title:B. Sc. Informatics
tel;work:University | AG Angewandte Informatik
tel;home:/home/usr
x-mozilla-html:FALSE
url:www.icram.de
version:2.1
end:vcard

___

Re: How to build entirety of Xorg 7.4 from source

[Florian Lier]

hey jd,

No problem
I guess "the rt2860 wifi mini-pci" driver won't be affected by building 
a xserver ^^


"ATI Mobility Radeon 9600"  I guess the latest driver from the git works 
fine (but

you better ask here or google first)

"How do you suggest I install 7.4 (once I build it) - I mean
do I first uninstall my existing X (on which so many packages
depend), and then install 7.4?"

You don't need to replace or uninstall your "old" xserver,
as you might have noticed the script builds the server
here: PREFIX="/opt/gfx-test" which means you can
start the sever like that:


  1.

 rmmod i915 /# assuming you're using Intel/

  2.

 rmmod drm

  3.

 insmod ///linux-core/drm.ko

  4.

 insmod ///linux-core/i915.ko

  5.

 export LD_LIBRARY_PATH=/opt/gfx-test/lib

  6.

 startx -- /opt/gfx-test/bin/Xorg -verbose /# make sure you have a
 ~/.xinitrc with what you want to run/


If the server works fine you can set the new xorg stack as your default 
x-server. I won't recommend you
setting a "bleeding edge" X as default (btw, it won't startup atm have a 
look @ xorg tinderbox).
I don't know that much about Fedora, but I installed FC10 lately from a 
live cd which works fine for me...

Do you want to compile it from scratch?

Cheers, Florian



JD wrote:

Hi Florian,
and thank you very much for your response.
I have a Fedora FC7 notebook.  with 2 cruicial drivers
that I had struggled a lot to make  them work; namely,
the rt2860 wifi mini-pci card from Ralink Technology, and
the ATI Mobility Radeon 9600.
The modification that have been made to these drivers in
their latest incarnations, do not work for me.

How do you suggest I install 7.4 (once I build it) - I mean
do I first uninstall my existing X (on which so many packages
depend), and then install 7.4? I am afraid that the dependencies
will be broken, and many if not most graphical packages
will stop working.

Best regards,

JD


Florian Lier wrote:

Hey JD,

there's a little script on the Xorg / git development site.

http://www.x.org/wiki/Development/git

You can copy and paste the script into a myxorgscript.sh (chmod +x it )
You can start building X like that (in console): sh myxorgscript init 
| build | update


Depending on what distri you're using you'll need a bunch of 
dependencies.

If you're on Ubuntu I can help you out...


DEPS="\autoconf automake xserver-xorg-dev libdrm-dev build-essential 
libxxf86vm-dev libxdamage-dev libxfixes-dev libxfixes3 expat 
libexpat-dev libtool autobook \
libxinerama1 libxinerama-dev libxkbfile-dev libxkbfile1 openssl 
libssl-dev xkbsel x11-xkb-utils libxfont1 libxfont-dev git-core gawk 
libxt-dev \
xdebconfigurator autoconf-doc libhal-dev libdbus-1-dev 
libxcomposite-dev libpng12-dev libsm-dev libxrandr-dev \
libxdamage-dev libxinerama-dev libstartup-notification0-dev 
libgconf2-dev libgl1-mesa-dev libglu1-mesa-dev libmetacity-dev 
librsvg2-dev libdbus-1-dev \
libdbus-glib-1-dev libgnome-desktop-dev libgnome-window-settings-dev 
gitweb curl intltool libxslt1-dev xsltproc libwnck-dev python-dev 
libX11-xcb-dev \
pyrex-mode python-pyrex x11proto-scrnsaver-dev libxss-dev 
libprotobuf0 libprotobuf-dev protobuf-compiler gperf xmlto 
libglut3-dev freeglut3-dev \

freeglut-dev libglu1-mesa-dev libglu1-mesa"


(this is if you want to build compiz too)


I hope this helps.

cheers florian

JD wrote:

Dear Developers of Xorg

I wanted to build the entirety of X 7.4 frm source, but when
I saw that it is made up of individual tarballs, I decided to
write and ask if there is a single tarball of everything,
with a top level configure ...etc to build the whole thing.

I searched the FAQ for a "how to build X" or just "how to build"
but came up empty.

Thanx for any info to show how to build the whole 7.4 X system.

Best Regards,

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

  






begin:vcard
fn:Florian Lier
n:Lier;Florian
org:;AG AI | so far
adr:;;Germany
email;internet:f...@icram.de
title:B. Sc. Informatics
tel;work:University | AG Angewandte Informatik
tel;home:/home/usr
x-mozilla-html:FALSE
url:www.icram.de
version:2.1
end:vcard

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

Re: How to build entirety of Xorg 7.4 from source

[ace102]

  After going through the pain of trying to build straight from tarballs/git
myself I found that JHBuild is a nice interface to do this sort of thing.
With a little tweaking of the xorg.modules and jhbuildrc (both in
xorg/util/modular) it works nicely. Remember to make a prefix build
directory that isn't /usr to do a test build first to work out the kinks and
errors that might occur. Also don't build modules/drivers you don't need
which helps cut down on the build time.


JD-7 wrote:
> 
> I wanted to build the entirety of X 7.4 frm source, but when
> I saw that it is made up of individual tarballs, I decided to
> write and ask if there is a single tarball of everything,
> with a top level configure ...etc to build the whole thing.
> 


-
Error:Success
-- 
View this message in context: 
http://www.nabble.com/How-to-build-entirety-of-Xorg-7.4-from-source-tp22269690p22276143.html
Sent from the Free Desktop - xorg mailing list archive at Nabble.com.

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

Keyboard modifier mapping problems

[Tobias Gerdin]

Hello,

I have a Japanese Powerbook G4 I'm creating a custom layout for. I have
created a xkb_symbols entry in the relevant file in
/usr/share/X11/xkb/symbols (Debian Lenny system) directory and added entries
for some non-modifier keys. It works.

However, to implement the rest of the layout I need to perform the following
remappings involving modifier keys:

Control_L -> [ apostrophe, quotedbl ]

Caps Lock -> "Alt Gr"

Alt_L -> [ less, greater ]

Super_L (this is the left "Command" key) -> Alt/Meta

Hiragana_Katakana -> Control

Eisu_toggle -> Control

KP_Enter (KPEN?) -> Alt/Meta


Thus, I want to remap non-modifier keys to modifier keys, modifier-keys to
non-modifying keys and from one modifier-key to another modifier key.

I have been trying all day getting at least some of these mappings to work
but not much success I am afraid. I first tried the xmodmap route but I am
under the impression that this should be possible using only xkb using
modifier_maps and the like.

Perhaps someone could would care to supply me with a suitable strategy here?

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

Re: correct location of evdev?

[Dan Nicholson]

On Sat, Feb 28, 2009 at 5:46 PM, Marc Weber  wrote:
>
> The concept of nixos is to store everypackage within its own path.
> That's why there are that many /nix/store/hash-name/ paths above.
> After having installed the packages into the store those dirs are made
> readonly. Now xkbcomp tries to save to one of those paths and fails.

Unless you're extremely careful about how you configure the packages
(and some of them may not even allow you to do it), you probably will
hit problems trying to install all the x packages into different
roots. They really expect to be integrated together into common paths.
Good luck with that.

Did you try running xkbcomp manually like I suggested? It might shed
more light onto why it can't find the evdev keycodes.

> The next small issue I have is that xkeyboard-config and xkbmodmap both
> depend on each other in some way:
> xkeyboard-config requires some header files of xkbcomp
> xkbcomp requires the installation path of xkeyboard-config to find evdev. [1]

xkbcomp is just an application, it doesn't have any headers.
xkeyboard-config does not require it. Likewise, you don't have to have
xkeyboard-config installed to build xkbcomp. You can just tell the
build where the xkb files will be.

I think what you're seeing is that xkeyboard-config is searching for
xkbcomp at build time. It then tries to make a symlink at
$XKB_ROOT/xkbcomp to the real xkbcomp. This is just for your
convenience. Nothing else uses that symlink, and I suspect most
distros remove it.

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

xserver and --enable-debug faili ng, ET_DeviceKeyPress’ undeclared

[Marc Weber]

Hi,

when compliling xorgserver using --enable-debug I get this error:
make[1]: Entering directory `/tmp/xserver/dix'
building events.lo
 if ../doltcompile gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include
-I../include -I../include -I../include -I../include -I../include
-DHAVE_DIX_CONFIG_H -Wall -Wpointer-arith -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations -Wnested-externs
-fno-strict-aliasing -Wbad-function-cast -Wold-style-definition
-Wdeclaration-after-statement -DDBUS_API_SUBJECT_TO_CHANGE -D_BSD_SOURCE
-DHAS_FCHOWN -DHAS_STICKY_DIR_BIT
-I/nix/store/fczfqarm5nkkwip32q4zddr0rz29miav-openssl-0.9.8g/include
-I/nix/store/7k6k46igk63zwxi8j19hwmvnv30yxmqd-inputproto-git/include
-I/nix/store/g3a5ghn573y4mbhck8r09143hzfabgp6-x11proto-git/include
-I/nix/store/hgirr8zqwm11d2i0bdwv6dijqk7lscm2-kbproto-git/include
-I/nix/store/s1a2gqi5awx3ahj48j0x9prv8dl115wk-renderproto-git/include
-I/nix/store/v86gja5sh6yx7rws37vgxics57sgh5i2-xextproto-git/include
-I/nix/store/c1jyp4cq4d9vq774arqccvs7pw17g0im-pixman-git/include/pixman-1
-I/nix/store/x363424j136pcjwlihlaj7xhij83cwah-bigreqsproto-git/include
-I/nix/store/rn9ay321h203f2sk7ynm2zq30syn2bm1-compositeproto-git/include
-I/nix/store/994ngzzz3a2r04j10lp0c5awdsxc6l4b-damageproto-git/include
-I/nix/store/bdkl07dsqvasw4f7h2bmg3bw79vkcrp5-fixesproto-git/include
-I/nix/store/cq6wplmpfcc8i941f94g0zpg0hbp82cb-libfontenc-git/include
-I/nix/store/y0kyh3jm7whin1ndkpw4rrhk67p3wzpv-fontsproto-git/include
-I/nix/store/9p74i9j54qacmj25h21hyhmd8pphj72h-hal-0.5.10/include/hal
-I/nix/store/s4abqgxrzd8ja5l3k4aqza8rwl9simcf-randrproto-git/include
-I/nix/store/82ln2l5568fk54if7sb16fvxz44xjl5j-resourceproto-git/include
-I/nix/store/qzky3dawhnz5j2089kcj1ji3b4wnxmn9-scrnsaverproto-git/include
-I/nix/store/1y42i0ac60haj17qn1sragc8bjdnb83f-videoproto-git/include
-I/nix/store/wbrqkn22rmx8ww46p0sbjw2vwcaq58l5-xcmiscproto-git/include
-I/nix/store/jzh283hzcl2gpfhlx1xjxjd7sp93g245-libXfont-git/include
-I/nix/store/7wb1jmm219j8jipq94zazngv7qsl3dlv-libxkbfile-git/include
-I/nix/store/rq485g665dhjl2yxf1cgkdzz8rnf6kbz-libXau-git/include
-I/nix/store/7xl88y2i52rmjvg6mcny5h8hclidpnk6-libXdmcp-git/include
-I/nix/store/sxri5g1xniyl9vz5k3y9r9v5hdz1jlvw-xineramaproto-git/include
-I/nix/store/wvvwpph4ri8dpb2zpzlfs3qffxqdccm5-libXinerama-git/include
-I/nix/store/j06mzm10ij8qihy4swbfwvacvc19ab5w-libxtrans-git/include
-I/nix/store/wqvgyl3yfdpkldfdgnkak4838gyr5qp6-dbus-library-1.2.4/include/dbus-1.0
-I/nix/store/wqvgyl3yfdpkldfdgnkak4838gyr5qp6-dbus-library-1.2.4/lib/dbus-1.0/include
-I../include -I../include -I../Xext -I../composite -I../damageext
-I../xfixes -I../Xi -I../mi -I../miext/shadow  -I../miext/damage
-I../render -I../randr -I../fb -fvisibility=hidden -DVENDOR_NAME=\""The
X.Org Foundation"\" -DVENDOR_RELEASE="(((1) * 1000) + ((6) * 10)
+ ((99) * 1000) + 1)" -g -O2 -MT events.lo -MD -MP -MF
".deps/events.Tpo" -c -o events.lo events.c; \
then mv -f ".deps/events.Tpo" ".deps/events.Plo"; else rm -f
".deps/events.Tpo"; exit 1; fi
events.c: In function ‘FixKeyState’:
events.c:3678: error: ‘ET_DeviceKeyPress’ undeclared (first use in this
function)
events.c:3678: error: (Each undeclared identifier is reported only once
events.c:3678: error: for each function it appears in.)
make[1]: *** [events.lo] Error 1
make[1]: Leaving directory `/tmp/xserver/dix'

The patch 007e93c8693 broke it.
checking out the version before that I get some linking errors. but
events.o exists. The linking errors probably are caused by more recent
dependencies.

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

Re: [ANNOUNCE] xf86-video-intel 2.6.2

[Vasily Khoruzhick]

On Saturday 28 February 2009 07:21:54 Eric Anholt wrote:
> On Wed, 2009-02-25 at 19:13 +0100, Brice Goglin wrote:
> > Eric Anholt wrote:
> > > On Wed, 2009-02-25 at 14:10 +0100, Jacek Luczak wrote:
> > >> this release is totally unusable while running in UXA. System eats lot
> > >> of memory, including swapping. Is this that, reported earlier,
> > >> ,,memory leak''? As a result X are really slow and lot of lockups
> > >> occur (everything freeze for a few seconds). At the end I can't even
> > >> switch to text console, but system reacts on power button and it goes
> > >> down successfully. With EXA there's no such issue: total system memory
> > >> usage around 40%, no lockups.
> > >>
> > >> If it's not know issue I will try to bisect it down.
> > >>
> > >> -Jacek
> > >>
> > >> --
> > >> Details:
> > >>  1. X.Org X Server 1.5.99.903 (1.6.0 RC 3)
> > >>  2. Linux Kernel 2.6.29-rc6
> > >
> > > Can you give me exact steps to reproduce this leak?
> >
> > Same problem here with libdrm 2.4.5, intel 2.6.2, Xserver 1.6-rc2,
> > Mesa 7.3 on
> > Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated
> > Graphics Controller [8086:27a2] (rev 03)
> >
> > Nothing specific needed to reproduce the problem, just use X :)
> > As soon as I start a big application such as firefox ou thunderbird,
> > my 1GB RAM is entirely used after a couple seconds and the system
> > becomes vey slow.
> >
> > Only downgrade intel to 2.6.1 => 200MB used, no problem.
>
> I think the problem here was the DRI2 tiling fix, which was great for
> the 915-class 3D performance regression but bad for 915-class 2D.  I've
> pushed a fix to master that should help.  If it does, I'll try to get a
> 2.6.3 out soon.
>
> commit 5bfd73cd31ba197a62f549cdbad1a1270b571027
> Author: Eric Anholt 
> Date:   Fri Feb 27 19:09:49 2009 -0800
>
> Only allocate pixmaps aligned for tiling when requested by DRI2
> GetBuffers.
>
> This saves massive quantities of memory on pre-965 since the DRI2
> tiling enable caused the minimum size of any pixmap to be 1MB.

Thanks, fix works for me (no more memory leakage) :)

2D works very fast (xf86-video-intel from git, xorg-server-1.6.0, mesa-7.3, 
kernel-2.6.29_rc6), but 3D is not. With tiling enabled I get low 3D 
performance (up to 10fps in quake3) in any resolution, with tiling disabled I 
hit this bug: http://bugs.freedesktop.org/show_bug.cgi?id=19738.

Someone noted that when the system uses dual channel memory in interleaved 
mode, tiling is not available. Is it true? If yes, will it be ever fixed? :)

Also I get following message on dmesg from time to time:

WARNING: at drivers/gpu/drm/i915/i915_gem.c:3048 i915_gem_idle+0x2e2/0x310 
[i915]()
Hardware name: 0768B9G
Modules linked in: ipv6 snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device 
snd_pcm_oss snd_mixer_oss irda cpufreq_conservative cpufreq_powersave 
cpufreq_ondemand acpi_cpufreq freq_table udf crc_itu_t coretemp vfat fat 
rfcomm l2cap bluetooth i915 drm i2c_algo_bit ppp_async crc_ccitt ppp_generic 
slhc snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm 
snd_timer snd thermal soundcore processor yenta_socket rsrc_nonstatic iwl3945 
sdhci_pci pcmcia_core rfkill mac80211 lib80211 sdhci snd_page_alloc 
thermal_syscfg80211 i2c_i801 mmc_core led_class 8139too button battery ac 
hwmon joydev evdev fuse nfs lockd sunrpc jfs scsi_wait_scan ohci1394ieee1394 
usbhid ohci_hcd uhci_hcd usb_storage hid ehci_hcd usbcore sr_mod cdrom 
sata_via
Pid: 5719, comm: X Tainted: G   A   2.6.29-rc6-anarsoul #2
Call Trace:
 [] warn_slowpath+0x87/0xe0
 [] lock_timer_base+0x40/0x60
 [] del_timer_sync+0x11/0x20
 [] schedule_timeout+0x94/0xf0
 [] __next_cpu+0x12/0x30
 [] i915_gem_retire_requests+0xf7/0x150 [i915]
 [] i915_gem_idle+0x2e2/0x310 [i915]
 [] i915_gem_leavevt_ioctl+0x24/0x40 [i915]
 [] drm_ioctl+0xee/0x2f0 [drm]
 [] hrtimer_forward+0x147/0x1a0
 [] lapic_next_event+0x10/0x20
 [] clockevents_program_event+0xa3/0x170
 [] i915_gem_leavevt_ioctl+0x0/0x40 [i915]
 [] vfs_ioctl+0x80/0x90
 [] do_vfs_ioctl+0x7b/0x5c0
 [] __do_softirq+0x97/0x160
 [] sys_ioctl+0x84/0x90
 [] sysenter_do_call+0x12/0x25
---[ end trace 09752fdd0fff28c4 ]---
[drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled 
pipe 0



signature.asc
Description: This is a digitally signed message part.
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg

Re: How to build entirety of Xorg 7.4 from source

[Florian Lier]

Hey JD,

there's a little script on the Xorg / git development site.

http://www.x.org/wiki/Development/git

You can copy and paste the script into a myxorgscript.sh (chmod +x it )
You can start building X like that (in console): sh myxorgscript init | 
build | update


Depending on what distri you're using you'll need a bunch of dependencies.
If you're on Ubuntu I can help you out...


DEPS="\autoconf automake xserver-xorg-dev libdrm-dev build-essential 
libxxf86vm-dev libxdamage-dev libxfixes-dev libxfixes3 expat 
libexpat-dev libtool autobook \
libxinerama1 libxinerama-dev libxkbfile-dev libxkbfile1 openssl 
libssl-dev xkbsel x11-xkb-utils libxfont1 libxfont-dev git-core gawk 
libxt-dev \
xdebconfigurator autoconf-doc libhal-dev libdbus-1-dev libxcomposite-dev 
libpng12-dev libsm-dev libxrandr-dev \
libxdamage-dev libxinerama-dev libstartup-notification0-dev 
libgconf2-dev libgl1-mesa-dev libglu1-mesa-dev libmetacity-dev 
librsvg2-dev libdbus-1-dev \
libdbus-glib-1-dev libgnome-desktop-dev libgnome-window-settings-dev 
gitweb curl intltool libxslt1-dev xsltproc libwnck-dev python-dev 
libX11-xcb-dev \
pyrex-mode python-pyrex x11proto-scrnsaver-dev libxss-dev libprotobuf0 
libprotobuf-dev protobuf-compiler gperf xmlto libglut3-dev freeglut3-dev \

freeglut-dev libglu1-mesa-dev libglu1-mesa"


(this is if you want to build compiz too)


I hope this helps.

cheers florian

JD wrote:

Dear Developers of Xorg

I wanted to build the entirety of X 7.4 frm source, but when
I saw that it is made up of individual tarballs, I decided to
write and ask if there is a single tarball of everything,
with a top level configure ...etc to build the whole thing.

I searched the FAQ for a "how to build X" or just "how to build"
but came up empty.

Thanx for any info to show how to build the whole 7.4 X system.

Best Regards,

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

  


begin:vcard
fn:Florian Lier
n:Lier;Florian
org:;AG AI | so far
adr:;;Germany
email;internet:f...@icram.de
title:B. Sc. Informatics
tel;work:University | AG Angewandte Informatik
tel;home:/home/usr
x-mozilla-html:FALSE
url:www.icram.de
version:2.1
end:vcard

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