From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [2011,03 maint] Confused about xserver-xorg + touchscreen
Date: Sat, 10 Dec 2011 23:57:05 +0100 [thread overview]
Message-ID: <20111210225705.GC3986@jama.jama.net> (raw)
In-Reply-To: <4EE3A963.8070504@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 2864 bytes --]
On Sat, Dec 10, 2011 at 10:48:03AM -0800, Ed Nelson wrote:
> I am trying to build a modified minimal-gpe-image to use xserver-xorg
> and use xinput-calibrator but for some reason it keeps building tslib.
> Consequently I have to modify xorg.conf so the touchscreen driver uses
> tslib and not evdev for the touchsceen to work. This is OK but I
> thought that the new way to do the touchscreen was to use xinput and to
> calibrate the touchscreen was to use xinput-calibrator. I tried to find
> a image recipe that used xinput-calbrator but didn't find one.
>
> Is it better to use xserver-xorg + xinput-calibrator or use
> xserver-xorg + tslib + modify xorg.conf?
> Am I missing something in the minimal-gpe-image recipe?
> Shouldn't I see something for xinput-calibrator inside Xsessions?
See SHR overrides in xserver-common
Regards,
>
>
> Below is my minimal-gpe-image recipe
> ==================================
> #Angstrom minimal gpe image
> # This image provides a barebone dm and 'desktop'
> # Very angstrom and opkg centric
>
> ANGSTROM_EXTRA_INSTALL += " \
> "
>
> XSERVER = "xserver-xorg \
> xf86-input-evdev \
> xf86-input-mouse \
> xf86-video-fbdev \
> xf86-input-keyboard"
>
> SPLASH ?= ' ${@base_contains("MACHINE_FEATURES", "screen",
> "psplash-angstrom", "",d)}'
>
> export IMAGE_BASENAME = "minimal-gpe-image"
>
> PR = "r2"
>
> DEPENDS = "task-boot"
>
> IMAGE_INSTALL = "\
> ${XSERVER} \
> task-boot \
> gpe-dm gpe-session-scripts gpe-login \
> matchbox-wm \
> gpe-terminal \
> angstrom-feed-configs \
> xinput-calibrator \
> nano \
> python \
> ${SPLASH} \
> ${ANGSTROM_EXTRA_INSTALL} \
> "
>
> #zap root password for release images
> ROOTFS_POSTPROCESS_COMMAND += '${@base_conditional("DISTRO_TYPE",
> "release", "zap_root_password; ", "",d)}'
>
> inherit image
>
> =========================================
> This is my Xinit.d
>
> root@sbc9261:~# ls /etc/X11/Xinit.d/
> 01xrandr 40xmodmap 60xXDefaults 99gpe-login
> 11zaurus 50setdpi 89xTs_Calibrate
> 12keymap 55xScreenSaver 98keymap-fixup
>
> ================================================
> This is my Xsessions.d
>
> root@sbc9261:~# ls /etc/X11/Xsession.d/
> 50autolock 69ipaq-sleep 98standard-apps
> 60xXDefaults 89xdgautostart 99xWindowManager
> root@sbc9261:~#
>
> Thanks
> Ed
>
>
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2011-12-10 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 18:48 [2011,03 maint] Confused about xserver-xorg + touchscreen Ed Nelson
2011-12-10 22:57 ` Martin Jansa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111210225705.GC3986@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.