From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Packet menu: X.org X Window System
Date: Wed, 26 Dec 2012 09:47:19 +0100 [thread overview]
Message-ID: <20121226094719.64380938@skate> (raw)
In-Reply-To: <20121226022529.GA5440@zuhnb712.ap.bm.net>
Dear Woody Wu,
On Wed, 26 Dec 2012 10:25:29 +0800, Woody Wu wrote:
> I feel a little confused in the 'X.org X Window System' packet menu.
> It present me with 'X Window System server' as well as 'X11R7
> servers'. Under 'X Window System server' I can choice TinyX, under
> the 'X11R7 servers', I can choice x.org server. Is that a conflict?
> Or does it means, in additional to TinyX, I still need to pick up a
> X11R7 server to work with it?
There are two things:
* The selection of the "Server Type" (i.e TinyX or Modular X.org)
* The enabling or disabling of the X.org server
In fact, the X.org server can be compiled in two different flavors:
* The modular X.org flavor, which is the one used on virtually all
Linux distributions. In this flavor, the device drivers (video,
input, etc.) are compiled separately from the X.org server and can
be dynamically loaded.
* The TinyX variant, in which drivers are directly bundled into the X
server. Those drivers are more limited (in number), and are directly
part of the X.org server code base (as opposed to the modular X.org,
where each driver is a separate project, separate tarball.
It would probably be more clear to have the Server Type selection as a
sub-option of the X.org server selection.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-26 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 2:25 [Buildroot] Packet menu: X.org X Window System Woody Wu
2012-12-26 8:47 ` Thomas Petazzoni [this message]
2012-12-26 22:59 ` Peter Korsgaard
2012-12-27 11:46 ` Thomas Petazzoni
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=20121226094719.64380938@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox