All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/8] board/raspberrypi: post-image customisations.
Date: Mon, 11 Feb 2019 19:21:01 +0100	[thread overview]
Message-ID: <20190211182101.GO3079@scaer> (raw)
In-Reply-To: <e5641c36-15cc-1a2e-7b86-1e41d7ec188b@codethink.co.uk>

Robert, All,

On 2019-02-11 11:17 +0000, Robert Heywood spake thusly:
> On 08/02/2019 21:15, Arnout Vandecappelle wrote:
> >  Only, config.txt doesn't come from upstream; it comes from
> >package/rpi-firmware/config.txt and it says "we recommend you to change it to
> >fit your needs".
> >
> >  Okay, it goes on saying to override it in a post-build script, but that's
> >because there is no other way to put a file into genimage.cfg.
> >
> The package/rpi-firmware/config.txt file is downloaded from the raspberrypi
> github. While its true that the file won't change without someone updating
> the commit in the respective .mk file,

Absolutely not. The config.txt file *is* bundled in Buildroot.

> its not a file that buildroot
> maintains or authored. It is being pulled from upstream.

Yes it is, just do:  "git log package/rpi-firmware/config.txt"  and
you'll see that it is a file we have had since the inception of the
rpi-firmware package in Buildroot.

We may have used the upstream one as inspirtion, though.

> If you really wanted to keep separate versions of config.txt around for each
> board, genimage does support renaming files as it copies them into the
> image.
> You could feasibly add a line such as this to each cfg file;
>     file config.txt { image = "board/raspberrypi/config_raspberrypi0w.txt" }

Actually, I think this is a very good idea. But that is just my
position, others may disagree...

Again, you have to recognise that the defconfig files we have in
Buildroot are just basic configurations and setups, that are there just
to help one bootstrap a local build for a custom project/hobby/...

Again, my position is that, if one's project/hobby/... needs a custom
linux/uboot/firmware/etc... config file, then one should handle it
locally, using the files in Buildroot as inspiration.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2019-02-11 18:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 13:23 [Buildroot] [PATCH 0/8] board/raspberrypi: post-image customisations Robert J. Heywood
2019-01-29 13:23 ` [Buildroot] [PATCH 1/8] board/raspberrypi: Unify the genimage config files Robert J. Heywood
2019-01-29 13:23 ` [Buildroot] [PATCH 2/8] board/raspberrypi: post-image --overlays option Robert J. Heywood
2019-01-29 13:23 ` [Buildroot] [PATCH 3/8] board/raspberrypi: post-image, include .config dfs files Robert J. Heywood
2019-01-29 13:23 ` [Buildroot] [PATCH 4/8] board/raspberrypi: post-image, include .config kernel target Robert J. Heywood
2019-01-29 13:23 ` [Buildroot] [PATCH 5/8] board/raspberrypi: post-image --file option Robert J. Heywood
2019-01-29 13:23 ` [Buildroot] [PATCH 6/8] board/raspberrypi: post-image --rootfs option Robert J. Heywood
2019-01-29 13:23 ` [Buildroot] [PATCH 7/8] board/raspberrypi: post-image --skip-sdimg option Robert J. Heywood
2019-01-29 13:23 ` [Buildroot] [PATCH 8/8] board/raspberrypi: post-image --kernel option Robert J. Heywood
2019-02-06 12:36 ` [Buildroot] [PATCH 0/8] board/raspberrypi: post-image customisations Arnout Vandecappelle
2019-02-08 11:41   ` Robert Heywood
2019-02-08 21:15     ` Arnout Vandecappelle
2019-02-11 11:17       ` Robert Heywood
2019-02-11 18:21         ` Yann E. MORIN [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=20190211182101.GO3079@scaer \
    --to=yann.morin.1998@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.