From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-we0-f172.google.com ([74.125.82.172]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RplHF-0001Bf-S3 for ptxdist@pengutronix.de; Tue, 24 Jan 2012 19:39:31 +0100 Received: by werp11 with SMTP id p11so4093399wer.31 for ; Tue, 24 Jan 2012 10:39:24 -0800 (PST) Message-ID: <4F1EFADC.7020308@gmail.com> Date: Tue, 24 Jan 2012 19:39:24 +0100 From: Guillermo Rodriguez MIME-Version: 1.0 Subject: [ptxdist] X.org on mini2440 Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Dear all, I am playing with ptxdist (2011.12.0) on a mini2440 board and wanted to test X.org on it. After some tweaking I have managed to successfully run X, but wanted to share some issues I've found along the way. I enabled X.org with the framebuffer driver, evdev for touchscreen input, and "void" for keyboard input. I also added the xinit package (for startx and xinit), built everything, and booted the target. I then tried startx, but got an error message saying that a cookie could not be generated. Upon inspecting /usr/bin/startx I see that the following has leaked through: mcookie=`/home/grodriguez/work/ptxdist/OSELAS.BSP-Pengutronix-Mini2440-2011.12.0/platform-mini2440/sysroot-host/bin/mcookie` Not sure whether this is a bug in the configure script in the xinit package, and/or something that can be fixed in ptxdist itself. In my case, I fixed this by manually editing the startx script and replacing the above with a pregenerated mcookie value. Next thing was that X.org would not start if the kernel is not compiled with support for virtual terminals. While obvious in retrospect, I wonder whether it is possible for ptxdist to detect this kind of dependencies (e.g. detect that a required kernel option is not set in the current kernel configuration). While this wouldn't help when ptxdist is used to generate a rootfs only, it would certainly be useful if ptxdist is also generating the kernel for the target platform. Rebuilt and reflashed the kernel and the problem went away. Finally I found that even when I had configured X.org to use the "void" driver for the keyboard, it would keep complaining about keymaps and keyboard initialisation until I added xkeyboard-config (presumably for /usr/lib/X11/xkb/rules/base) and xkbcomp (for the latter I had to enable the "Keyboard mappings" option in ptxdist). Not sure whether these two are actually required for all X.org installations but I could not find any other way around. If this is really a requirement perhaps these dependencies should be forced. After this I could run X on the target device. Used fluxbox as a WM. I can provide more information on any of the above issues if required. Thanks and best regards, Guillermo Rodriguez -- ptxdist mailing list ptxdist@pengutronix.de