From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add package raspberrypi-firmware.
Date: Tue, 18 Sep 2012 20:06:22 +0200 [thread overview]
Message-ID: <20120918200622.472bf779@skate> (raw)
In-Reply-To: <201209181947.32049.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Tue, 18 Sep 2012 19:47:31 +0200, Yann E. MORIN wrote:
> So, basically, the initial interest for this package is to provide the
> bootloader files, hence I believe the package should go in the bootloader
> sub-menu.
>
> Then we can add a VideoCoreIV package in one of the "packages on target"
> sub-menu ("libs -> hardware handling" sounds the most adequate AFAICS).
And so this package would "depends on" a bootloader?
Marek made it clear at the beginning: even though this
rasberrypi-firmware package contains a bootloader, he decided to put it
in package/ because it also contains userspace libraries. And Marek
wanted to avoid having two separate packages, because it would be that
you would download the same original tarball (or Git repository) twice,
have two packages to upgrade when bumping the version, etc.
Note that we however already have a relatively similar situation with
u-boot: we have boot/uboot for the bootloader and package/u-boot-tools
for the host and target utilities.
It is clearly a lack of separation between source package and binary
packages that is causing problem here. We should normally have one
source package: rasberrypi-firmware, that provides two binary packages:
rasberrypi-bootloader and rasberrypi-videocore-libs.
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-09-18 18:06 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
2012-09-18 17:47 ` Yann E. MORIN
2012-09-18 18:06 ` Thomas Petazzoni [this message]
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=20120918200622.472bf779@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