From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add package raspberrypi-firmware.
Date: Tue, 18 Sep 2012 07:09:34 +0200 [thread overview]
Message-ID: <20120918070934.2e3182bf@skate> (raw)
In-Reply-To: <201209172350.27316.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Mon, 17 Sep 2012 23:50:27 +0200, Yann E. MORIN wrote:
> What would be the interest to install the GPU boot files, but not install
> the VideoCore libraries? Or the other way around, what would be the intrest
> to install the VidoeCore library without the GPU boot files?
The GPU boot files are needed to actually boot the ARM processor. So
technically speaking, they are some kind of first-stage bootloader for
the ARM processor, even if they get executed on the GPU.
So, if you want to use the RasberryPi, you *must* install those GPU
boot files. However, if you're not using the RasberryPi for a 3D
graphical application, you don't necessarily need the VideoCore library
files. So I think it makes sense to be able to install the GPU boot
files separately from the VideoCore library.
The underlying problem here is a fundamental weakness in Buildroot
design: the absence of separation between source packages and binary
packages. We have the same situation quite often for other things. For
example the "curl" package. It provides both a library "libcurl", and a
program "curl" that relies on that library. Should this package be
under "Libraries -> Networking" or under "Networking applications" ?
Ditto for many, many of our packages.
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-09-18 5:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 20:34 [Buildroot] [PATCH] Add package raspberrypi-firmware Marek Belisko
2012-09-17 20:43 ` Thomas Petazzoni
2012-09-17 21:01 ` Yann E. MORIN
2012-09-17 21:50 ` Yann E. MORIN
2012-09-18 5:09 ` Thomas Petazzoni [this message]
2012-09-18 17:47 ` Yann E. MORIN
2012-09-18 18:06 ` Thomas Petazzoni
2012-09-18 21:53 ` [Buildroot] Two packages with the same source [was: [PATCH] Add package raspberrypi-firmware.] Arnout Vandecappelle
2012-09-18 22:01 ` [Buildroot] [PATCH] Add package raspberrypi-firmware Arnout Vandecappelle
2012-09-19 7:59 ` Diego Iastrubni
2012-09-19 8:09 ` Belisko Marek
2012-09-19 19:49 ` Arnout Vandecappelle
2012-09-19 20:08 ` Belisko Marek
2012-09-19 21:28 ` Arnout Vandecappelle
2012-09-19 21:50 ` Belisko Marek
2012-09-19 23:10 ` Arnout Vandecappelle
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=20120918070934.2e3182bf@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