From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Do we really want shared Xserver script for all machines?
Date: Fri, 16 Apr 2010 14:39:20 +0200 [thread overview]
Message-ID: <20100416123920.GB3323@jama> (raw)
Hi,
on Openmoko Freerunner om-gta02 Xserver script takes about 3s on every
boot
http://build.shr-project.org/tests/jama/bootchart-2.6.32.9.r1.png
it's started from /etc/init.d/xserver-nodm and with eliminated Xserver
call by passing xinit call directly with right Xorg params I get this
http://build.shr-project.org/tests/jama/bootchart-2.6.32.9.r3.png
My question is:
should I commit simplified versions of Xserver script
xserver-kdrive-common/xserver-kdrive-common/Xserver
to
xserver-kdrive-common/xserver-kdrive-common/om-gta02/Xserver
and the same for other devices supported in Xserver (to save
grep,awk call).
or do it only for om-gta02 (maybe even in
xserver-kdrive-common/xserver-nodm-init/xserver-nodm
) and those who care about boot time will follow?
Maybe calling fallback_screen_arg only where it's really needed would be
good enough optimization, without the cost of loosing PACKAGE_ARCH =
"all".
Cheers,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next reply other threads:[~2010-04-16 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 12:39 Martin Jansa [this message]
2010-04-16 13:25 ` Do we really want shared Xserver script for all machines? Koen Kooi
2010-04-16 13:41 ` Marcin Juszkiewicz
2010-04-16 20:50 ` Martin Jansa
2010-04-20 4:53 ` Martin Jansa
2010-04-16 13:39 ` Sergey Lapin
2010-04-16 21:00 ` [OT] bootchart (was: Do we really want shared Xserver script for all machines?) Paul Menzel
2010-04-16 21:19 ` Martin Jansa
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=20100416123920.GB3323@jama \
--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.