Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] rpi-fw: New package
Date: Mon, 07 Jan 2013 18:45:11 +0100	[thread overview]
Message-ID: <50EB09A7.80705@mind.be> (raw)
In-Reply-To: <CAGduivxAVfkwsmqjjk1JY7_gU70VmBrsUcVeEtzPtYUh70k1Ng@mail.gmail.com>

On 06/01/13 15:47, Maxime Hadjinlian wrote:
>> >    Floris>  But another question would be if bootloader files really should be
>> >    Floris>  installed under target.
>> >    Floris>  Keep in mind that the Raspberry Pi boot files are normally kept on a
>> >    Floris>  FAT partition seperate from the root file system.
>> >
>> >  Indeed, it probably makes more sense to just put it in IMAGES_DIR
>> >  instead.
> How about putting them all in a rpi-firmware folder inside IMAGES_DIR
> ? I don't want to just throw them in this folder, it would be a pain
> afterwards since they all go in the same place.

  I think typically everything in the images directory goes into the boot 
partition, except the rootfs.* (exception to the exception: rootfs.cpio*, 
unless it's an initramfs)

  I have thought about creating a boot/ subdirectory in the images 
directory that collects everything that is supposed to go to the boot 
partition. But I'm afraid that there is no generic way to decide what has 
to go to the boot partition. For instance, if you generate a U-Boot for 
Flash but boot from SD card, you would have only kernel and device tree 
in the boot partition. In addition, you often want to add some additional 
things to the boot partition.

  Therefore I think that what we have now is quite OK. You can easily 
wrap the build in a script that copies things to the right place.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2013-01-07 17:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 14:10 [Buildroot] [pull request] Pull request for branch rpi-support Maxime Hadjinlian
2013-01-05 14:10 ` [Buildroot] [PATCH 1/3] libcofi: new package Maxime Hadjinlian
2013-01-05 14:10 ` [Buildroot] [PATCH 2/3] rpi-userland: " Maxime Hadjinlian
2013-01-05 15:18   ` Samuel Martin
2013-01-05 16:23     ` Maxime Hadjinlian
2013-01-05 16:33       ` Samuel Martin
2013-01-05 17:39     ` Thomas Petazzoni
2013-01-05 20:12       ` Maxime Hadjinlian
2013-01-05 20:21         ` Samuel Martin
2013-01-05 15:23   ` Yann E. MORIN
2013-01-05 15:41   ` Alex Bradbury
2013-01-05 16:27     ` Maxime Hadjinlian
2013-01-06  2:26   ` Floris Bos
2013-01-06 10:28     ` Maxime Hadjinlian
2013-01-06 13:50       ` Floris Bos
2013-01-05 14:10 ` [Buildroot] [PATCH 3/3] rpi-fw: New package Maxime Hadjinlian
2013-01-05 15:36   ` Yann E. MORIN
2013-01-05 16:16     ` Maxime Hadjinlian
2013-01-05 17:58     ` Thomas Petazzoni
2013-01-05 20:00       ` Yann E. MORIN
2013-01-05 20:12         ` Maxime Hadjinlian
2013-01-05 15:52   ` Alex Bradbury
2013-01-05 16:09     ` Maxime Hadjinlian
2013-01-05 16:28       ` Alex Bradbury
2013-01-06  2:40   ` Floris Bos
2013-01-06 10:29     ` Maxime Hadjinlian
2013-01-06 14:26     ` Peter Korsgaard
2013-01-06 14:47       ` Maxime Hadjinlian
2013-01-07 17:45         ` Arnout Vandecappelle [this message]

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=50EB09A7.80705@mind.be \
    --to=arnout@mind.be \
    --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