Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add package raspberrypi-firmware.
Date: Thu, 20 Sep 2012 01:10:43 +0200	[thread overview]
Message-ID: <505A50F3.1060605@mind.be> (raw)
In-Reply-To: <CAAfyv35PHKbCht56tRcswvT4Gyy57e_0v0uSnGnk2mvjQ-zR=Q@mail.gmail.com>

On 09/19/12 23:50, Belisko Marek wrote:
> I would prefer to keep boot.tar.gz format. Imagine somebody who build
> RPI config and in images directory he will have 6 files. How he should
> know without reading
> elinux.org or rpi webpage what and which should be copied where ? With
> boot.tar.gz we can keep it in
> consistent format and if the name will be boot.tar.gz then average
> user will understand
> this should go to boot SD card partition. But this is just my opinion.

  Compare to any other defconfig: it will produce a number of files in the images
directory.  For instance, a typical TI OMAP will have MLO, u-boot.img, uImage
and rootfs.ext2.  The first three should go into the FAT partition, the last
on into an ext2 partition.  For RPi it's the same thing, except that the
number of images is a bit larger.

  That said, it's a good idea to have a readme.txt in the board directory to
explain how to put everything into a bootable image.

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
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:[~2012-09-19 23:10 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
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 [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=505A50F3.1060605@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