From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] ti-gfx: add new package
Date: Fri, 14 Jun 2013 22:22:54 +0200 [thread overview]
Message-ID: <20130614222254.56e49fcb@skate> (raw)
In-Reply-To: <CALo-6+jEOu+5pTr2oizokQexOdm1EimxYhM-Q1sHEnJ_oBFMog@mail.gmail.com>
Dear Charles Krinke,
On Thu, 13 Jun 2013 07:11:18 -0700, Charles Krinke wrote:
> On Spenser's patch, my comments to the RFC remain the same and those
> are 1) Graphics_SDK should not be a part of buildroot and 2) A kernel
> build should be independent of the root file system.
Sorry, but you're wrong on both points I believe:
(1) The whole point of the ti-gfx package that Spenser is doing, and
the whole point of the GSoC project Spenser is working on is
*precisely* to create Buildroot packages for many binary blobs /
special kernel modules that are needed to enable OpenGL, EGL and
other similar technologies on ARM SoCs. So, we definitely want
such packages to automatically download, extract, configure, build
and install whatever is necessary to enable the usage of such
technologies, and this, without requiring special intervention
from the Buildroot user. Just like all the other packages we have.
The fact that the Graphics_SDK thing is pretty huge to download is
just due to the poor TI practices in terms of packaging and
releases, and there's not much we can do about it. And anyway,
Buildroot users willing to enable complex technologies such as
OpenGL are most likely ready to download fairly large packages.
(2) The Graphics_SDK contains some kernel modules. They have to be
built against a Linux kernel tree that has been configured and
built. The only way to do that in Buildroot is to depend on the
'linux' package, which triggers a build of the Linux kernel. This
is completely normal, and I really don't see how it could be done
otherwise. That's already what we do for a number of other
packages that contain kernel modules, such as linux-fusion,
lttng-modules or rtai.
So the build of the root filesystem (which contains kernel
modules) cannot be fully independent from the build of the kernel.
It would be interesting if you could expand on why (1) or (2) are
causing problems for you, in the light of the above explanations.
Best regards,
Thomas Petazzoni
--
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:[~2013-06-14 20:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 17:36 [Buildroot] AM3517 Neon, OpenGL & EGLFS support Charles Krinke
2013-06-05 18:05 ` Wojciech Sleńska
2013-06-05 18:17 ` Charles Krinke
2013-06-05 22:16 ` Charles Krinke
2013-06-06 17:16 ` Wojciech Sleńska
2013-06-06 18:20 ` Charles Krinke
2013-06-06 18:26 ` Charles Krinke
2013-06-06 19:26 ` Wojciech Sleńska
2013-06-07 8:08 ` Thomas Petazzoni
2013-06-07 14:44 ` Charles Krinke
2013-06-07 15:23 ` Thomas Petazzoni
2013-06-07 15:40 ` Charles Krinke
2013-06-07 16:48 ` Thomas Petazzoni
2013-06-07 17:06 ` Charles Krinke
2013-06-07 20:18 ` [Buildroot] [RFC] ti-gfx: add new package Spenser Gilliland
2013-06-11 17:58 ` Charles Krinke
2013-06-12 17:33 ` Spenser Gilliland
2013-06-12 17:55 ` Charles Krinke
2013-06-12 18:37 ` Spenser Gilliland
2013-06-13 8:03 ` Naumann Andreas
2013-06-13 14:11 ` Charles Krinke
2013-06-14 20:22 ` Thomas Petazzoni [this message]
2013-06-14 20:58 ` Charles Krinke
2013-06-14 23:12 ` Yann E. MORIN
2013-06-15 16:28 ` Thomas Petazzoni
2013-06-15 9:37 ` Sundareson, Prabindh
2013-06-13 14:58 ` Spenser Gilliland
2013-06-17 13:35 ` Andreas Naumann
2013-06-17 16:26 ` Spenser Gilliland
2013-06-13 16:49 ` Arnout Vandecappelle
2013-06-14 2:20 ` Sundareson, Prabindh
2013-06-15 16:33 ` 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=20130614222254.56e49fcb@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