Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] rpi-fw: New package
Date: Sat, 5 Jan 2013 18:58:34 +0100	[thread overview]
Message-ID: <20130105185834.2f1fb7bc@skate> (raw)
In-Reply-To: <201301051636.51883.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Sat, 5 Jan 2013 16:36:51 +0100, Yann E. MORIN wrote:

> > +++ b/package/rpi-fw/Config.in
> > @@ -0,0 +1,9 @@
> > +config BR2_PACKAGE_RPI_FW
> > +	bool "RaspberryPi Firmware"
> 
> Today, this package is only used fior the RPI. But that GPU is not specific
> to the RPI, so what about calling that package "VideoCore bootloader" ?

I am quite sure the start.elf code is Rasberry Pi specific, so I don't
think this package is just a "VideoCore bootloader".

> > +++ b/package/rpi-fw/cmdline.txt
> > @@ -0,0 +1 @@
> > +dwc_otg.fiq_fix_enable=1 sdhci-bcm2708.sync_after_dma=0 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
> 
> This is typically a reason why I'd like to have a generic way to expressing
> the different filesystems tht form a sinlge firmware. Here, my root partition
> is *not* mmcblk0p2, it's p3. And the rootfstype is *not* ext4, it's ext2.
> 
> But, I guess we'll have to live with that commandline for now... :-/
> 
> Maybe you could just omit the root settings (or replace them with place-
> holders: root=/dev/XXXX rootfstype=XXXX). Of course, that will depend on
> the maintainer's opinion. ;-)

I would like to see a comment added in this file, which mentions this
is only a sample command line, and we recommend to override it on a
per-project basis using a post-build script.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-01-05 17:58 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 [this message]
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

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=20130105185834.2f1fb7bc@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