[Buildroot] Packet menu: X.org X Window System

[Buildroot] Packet menu: X.org X Window System

[Woody Wu]

Hi,

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?

I know I have some concepts not so clear in the area. If so, please help
to point it out.

Thanks in advance!

-- 
woody
I can't go back to yesterday - because I was a different person then.

[Buildroot] Packet menu: X.org X Window System

[Thomas Petazzoni]

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

[Buildroot] Packet menu: X.org X Window System

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 Thomas> In fact, the X.org server can be compiled in two different flavors:

 Thomas>  * The modular X.org flavor, which is the one used on virtually all
 Thomas>    Linux distributions. In this flavor, the device drivers (video,
 Thomas>    input, etc.) are compiled separately from the X.org server and can
 Thomas>    be dynamically loaded.

 Thomas>  * The TinyX variant, in which drivers are directly bundled into the X
 Thomas>    server. Those drivers are more limited (in number), and are directly
 Thomas>    part of the X.org server code base (as opposed to the modular X.org,
 Thomas>    where each driver is a separate project, separate tarball.

Also notice that Tinyx/kdrive is deprecated, and there's been talks
about completely removing it several times, most recently afaik was:

http://lists.x.org/archives/xorg-devel/2012-March/030059.html

 Thomas> It would probably be more clear to have the Server Type
 Thomas> selection as a sub-option of the X.org server selection.

Agreed.

-- 
Bye, Peter Korsgaard

[Buildroot] Packet menu: X.org X Window System

[Thomas Petazzoni]

Dear Peter Korsgaard,

On Wed, 26 Dec 2012 23:59:20 +0100, Peter Korsgaard wrote:

> Also notice that Tinyx/kdrive is deprecated, and there's been talks
> about completely removing it several times, most recently afaik was:
> 
> http://lists.x.org/archives/xorg-devel/2012-March/030059.html

Then, shouldn't we make "Modular X.org" be the default option instead
of the current default of "TinyX" ?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com