From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Juergen Beisert Date: Tue, 24 Jan 2012 20:24:40 +0100 References: <4F1EFADC.7020308@gmail.com> In-Reply-To: <4F1EFADC.7020308@gmail.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201201242024.40361.jbe@pengutronix.de> Subject: Re: [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 Cc: "Olbrich, Michael" , Guillermo Rodriguez Hi Guillermo, Guillermo Rodriguez wrote: > 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` This should help: $ ptxdist menuconfig Shell & Console Tools ---> util-linux-ng -----> [*] 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. Maybe a missing dependency from the xinit package into the util-linux-ng package. @Michael: what do you think? > 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. No, PTXdist cannot detect it automatically. The Kernel is part of the platform, Xorg is part of the userland. It's up to you as the developer to get the configuration in a way that matches your requirements. Our Mini2440 BSP can only act as a template for you. I did not configure it for maximum features, because I cannot test everything ;-) > 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. Same here: @Michael: what do you think? > 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. If you know what dependencies should be met (if the user want them), patches are welcome at the PTXdist mailing list. I cannot comment on this, as its long time ago, that I worked with Xorg on any kind of embedded device. Regards, Juergen -- Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | http://www.pengutronix.de/ | -- ptxdist mailing list ptxdist@pengutronix.de