mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: Re: Re: Re: Re: barebox extending boot-scripts
Date: Mon, 17 Jan 2022 09:59:37 +0100	[thread overview]
Message-ID: <20220117085937.GC1121@pengutronix.de> (raw)
In-Reply-To: <trinity-dcf71a1e-4856-486b-a9a5-74ed6a82fd34-1642254462656@3c-app-gmx-bap71>

On Sat, Jan 15, 2022 at 02:47:42PM +0100, Frank Wunderlich wrote:
> Hi,
> 
> i have now created a new barebox board as copy from evb. i can load it from tftp with
> 
> bootm /mnt/tftp/barebox-rk3568-r2pro.img
> 
> i can create a bootmenu with entries of loader/entries and boot it:
> 
> boot -m sd.1
> 
> my bootscripts are also there, but they are not listed in $global.boot.default
> 
> $ grep defaultenv arch/arm/boards/bananapi-r2-pro/Makefile
> bbenv-y += defaultenv-rk3568
> $ grep defaultenv arch/arm/boards/bananapi-r2-pro/board.c
> 	defaultenv_append_directory(defaultenv_rk3568);
> $ cat arch/arm/boards/bananapi-r2-pro/defaultenv-rk3568/nv/boot.default
> net list-images mmc-linux tftp-linux

So an "echo $global.boot.default" shows something different, right?

Could it be that you have overwritten this variable in your persistent
env? In that case try a "saveenv -z" which invalidates the persistent
env.

Sascha


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  reply	other threads:[~2022-01-17  9:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 15:20 Frank Wunderlich
2022-01-05 16:07 ` Ahmad Fatoum
2022-01-05 18:13   ` Aw: " Frank Wunderlich
2022-01-06  8:08     ` Sascha Hauer
2022-01-06 12:41       ` Aw: " Frank Wunderlich
2022-01-07 13:07         ` Sascha Hauer
2022-01-07 16:42           ` Aw: " Frank Wunderlich
2022-01-10  9:42             ` Sascha Hauer
2022-01-15 13:47               ` Aw: " Frank Wunderlich
2022-01-17  8:59                 ` Sascha Hauer [this message]
2022-01-29 10:40       ` Aw: " Frank Wunderlich
2022-01-31 11:03         ` Sascha Hauer

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=20220117085937.GC1121@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=frank-w@public-files.de \
    /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