From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] building fbtft framebuffer drivers into buildroot.
Date: Fri, 26 Dec 2014 15:04:38 +0100 [thread overview]
Message-ID: <20141226150438.08e429c2@free-electrons.com> (raw)
In-Reply-To: <20141226102028.GA3982@free.fr>
Dear Yann E. MORIN,
On Fri, 26 Dec 2014 11:20:29 +0100, Yann E. MORIN wrote:
> I've had a look at this package, and unfortunately, it will be hard to
> get it packaged in Buildroot.
>
> The problem is that this kernel module does not compile as an
> out-of-tree module, and their buildsystem is made so that it requires
> the kernel be patched.
>
> This is not posible with Buildroot.
Well, yes and no. Indeed it is much easier to package if the stuff can
be built as an out-of-tree module. However, we have two examples of
things packaged in Buildroot that require patching the kernel: Xenomai
and RTAI. They use a loosely defined model that we could name "Linux
extension", see linux/linux-ext-*.mk. They basically hook up into the
Linux build process by adding some stuff to LINUX_PRE_PATCH_HOOKS.
I recently had a look at the aufs stuff, and it has the same problem:
not only it is made of modules that can be built out-of-tree, but it
also needs to patch the kernel (some core VFS changes).
So, I haven't looked at all the fbtft stuff. If it's a set of
standalone drivers that don't require any modification to the core of
the kernel, then indeed, turning them into out-of-tree modules can be a
good idea. If not, then using the "linux-ext" model can be a solution.
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-12-26 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-25 20:09 [Buildroot] building fbtft framebuffer drivers into buildroot thebestofall007 .
2014-12-26 10:20 ` Yann E. MORIN
2014-12-26 14:04 ` Thomas Petazzoni [this message]
2014-12-26 14:51 ` Yann E. MORIN
2014-12-26 16:33 ` Thomas Petazzoni
[not found] ` <CAFGceHEkkKaSCQzarHbZx34h7ndirva-Y__Cot8Wo28zJ8rTpA@mail.gmail.com>
2015-01-15 2:16 ` Lou Crittenden
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=20141226150438.08e429c2@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