Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] rpi-firmware: do not rename startup files
Date: Thu, 25 Jun 2020 23:31:57 +0200	[thread overview]
Message-ID: <20200625213157.GW20645@scaer> (raw)
In-Reply-To: <CAFs+hh6XDH80-Sk9DG95ez7vEF4XJR=DrqAgjzZK7xcm42SrzQ@mail.gmail.com>

St?phane, All,

On 2020-06-25 19:30 +0200, St?phane Veyret spake thusly:
> > > Le jeu. 25 juin 2020 ? 18:23, Peter Seiderer <ps.report@gmx.net> a ?crit :
> > > > > I think we should instead force the name of the startup files in the
> > > > > config.txt (in package/rpi-firmware/config.txt):
> > > > >     start_file=start.elf
> > > > >     fixup_file=fixup.dat
> > > > Or one step further, copy the start/fixup file verbatim and only change the
> > > > start_file/fixup_file entry in config.txt (with the advantage to make it
> > > > transparent which files are installed/in-use)...
> > > If the file name is already the appropriate one (this is the first
> > > version of my patch), using start_file and fixup_file is useless. And
> > > I don't feel it is a good idea to set start_file and fixup_file if the
> > > files already have expected names, because using these options is
> > > discouraged: https://www.raspberrypi.org/documentation/configuration/config-txt/boot.md.
> > The options are not discouraged, but 'advanced options' and should be handled with care ;-)
> > The advantage of the explicit start_file/fixup_file entries is that it is clear/determined
> > which files are used (instead of relaying on the RPi 'magic' depending on the combination
> > of other options)....
> OK, I understand. Yann, do you agree? Shall I create a v3 patch?

I do agree that we better force the names of the file to load, yes.

No, you do not need to send a v3, as I explained in my reply to Peter.

I'll will probably apply your v2 patch as-is shortly...

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:[~2020-06-25 21:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 11:50 [Buildroot] [PATCH 1/1] rpi-firmware: do not rename startup files Stéphane Veyret
2020-06-24 16:54 ` Yann E. MORIN
2020-06-25 16:23   ` Peter Seiderer
2020-06-25 16:38     ` Stéphane Veyret
2020-06-25 17:20       ` Peter Seiderer
2020-06-25 17:30         ` Stéphane Veyret
2020-06-25 21:31           ` Yann E. MORIN [this message]
2020-06-25 19:50         ` Yann E. MORIN

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=20200625213157.GW20645@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox