From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xserver_xorg-server: backport hotplug support
Date: Wed, 13 Jun 2012 18:28:59 +0200 [thread overview]
Message-ID: <20120613182859.3217c88c@skate> (raw)
In-Reply-To: <1339603696-2787-1-git-send-email-rbraun@sceen.net>
Le Wed, 13 Jun 2012 18:08:16 +0200,
Richard Braun <rbraun@sceen.net> a ?crit :
> The hotplug and configuration improvements in the X server 1.8 branch,
> namely the udev backend and the xorg.conf.d directory, were backported
> in the 1.7 Debian package. Grab the appropriate patches from the
> Debian xorg-server_1.7.7-14 sources, bump version to 1.7.7 for the
> latest fixes and clean patching, and adjust the makefile to enable
> the udev backend when using udev. This, combined with the evdev input
> driver, provides automatic support for USB mouse/keyboard
> hotplugging, and probably other device types.
Unless I'm wrong X11R7.7 has been released some time ago, and it
includes X server 1.12, at
http://www.x.org/releases/X11R7.7/src/xserver/. So why would we bother
backporting 1.8 material to a 1.7 version? Upgrading the complete X.org
stack to X11R7.7 seems like a much more appropriate solution. Or maybe
I'm missing something obvious?
Moreover in general, we don't like to carry patches that aim at adding
features. We carry patches to fix build problems, or sometimes
architecture-specific fixes, but large new features should not be added
to packages using patches, otherwise Buildroot will become an
unmaintainable crap of patches.
Best regards,
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-06-13 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 16:08 [Buildroot] [PATCH] xserver_xorg-server: backport hotplug support Richard Braun
2012-06-13 16:28 ` Thomas Petazzoni [this message]
2012-06-13 16:44 ` Richard Braun
2012-06-13 17:01 ` Will Wagner
2012-06-14 5:56 ` Peter Korsgaard
2012-06-14 15:59 ` Julian Lunz
2012-06-14 5:55 ` Peter Korsgaard
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=20120613182859.3217c88c@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