From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] out-of-tree kernel modules and linux header versions
Date: Thu, 13 Nov 2014 21:27:04 +0100 [thread overview]
Message-ID: <20141113212704.74b96059@free-electrons.com> (raw)
In-Reply-To: <CAJpxd04tNrVAiT4AC0ojA75pH9q9TYU6XtezqyTNWNJh8LSkwg@mail.gmail.com>
Dear Bryce Schober,
On Thu, 13 Nov 2014 09:03:07 -0800, Bryce Schober wrote:
> I would, if it *were* simple. Because my target is tied to *very* old
> kernel and certain packages, especially Xorg, it is not at all simple. The
> infrastructure around Xorg and opengl has changed a lot since 2011.08, and
> backporting the extensive list of xorg and related packages would be a lot
> of work. Or at least I think it would be... maybe I'm being too
> pessimistic. Don't get me wrong, I'd love to spend the time to get
> up-to-date and get all the benefits of recent development. But I'm sure you
> know how competing priorities go...
Aah, yes, I now remember. Due to a proprietary graphics driver, you
have to use an old X.org version and an old kernel. Using an old kernel
is fairly easy, but using an old X.org version is more problematic.
Unfortunately, that's not something for which I see an easy solution in
Buildroot :-/
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-13 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 1:53 [Buildroot] out-of-tree kernel modules and linux header versions Bryce Schober
2014-11-13 2:16 ` Bryce Schober
2014-11-13 8:20 ` Thomas Petazzoni
2014-11-13 17:03 ` Bryce Schober
2014-11-13 20:27 ` Thomas Petazzoni [this message]
2014-11-13 19:48 ` Arnout Vandecappelle
2014-11-13 21:53 ` Bryce Schober
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=20141113212704.74b96059@free-electrons.com \
--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