All of lore.kernel.org
 help / color / mirror / Atom feed
From: Drew Fustini <drew@beagleboard.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Support for the Beagle-V platform
Date: Thu, 29 Apr 2021 17:35:27 -0700	[thread overview]
Message-ID: <20210430003527.GA132765@x1> (raw)
In-Reply-To: <CAK4VdL2T=a7ffUweZC2dV5LTD2JNmP=UxU+2BfJ-L+bVB7Vp=Q@mail.gmail.com>

On Thu, Apr 29, 2021 at 02:39:16PM +0200, Erico Nunes wrote:
> On Thu, Apr 29, 2021 at 9:47 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> > slight annoyance is that the bootloader
> > pre-flashed on the board doesn't work as-is, just due to an incorrect
> > fdt_addr_r environment variable value. So reflashing the bootloader
> > with what has been built by Buildroot is necessary (but is trivial to
> > do using Xmodem).
> 
> I would like to try this but I have some questions:
> Are you able to still boot the reference Fedora image after flashing
> the custom bootloader?
> Also, if it is just a matter of updating fdt_addr_r, could it just be
> updated in the u-boot environment instead?
> And finally, should that be reported as an issue in the starfive
> u-boot so maybe they can release another build with that fixed?

I think that is a good idea so I have opened an issue to track resolving
this in future production of BeagleV Starlight boards.

Thanks,
Drew

[1] https://github.com/starfive-tech/freelight-u-sdk/issues/18

  parent reply	other threads:[~2021-04-30  0:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  7:46 [Buildroot] [PATCH 0/4] Support for the Beagle-V platform Thomas Petazzoni
2021-04-29  7:46 ` [Buildroot] [PATCH 1/4] boot/opensbi: add support for version configuration Thomas Petazzoni
2021-04-29 12:45   ` Bin Meng
2021-04-30  7:48   ` Peter Korsgaard
2021-04-30  8:51   ` Drew Fustini
2021-04-30  8:56     ` Thomas Petazzoni
2021-04-29  7:46 ` [Buildroot] [PATCH 2/4] boot/opensbi: allow using U-Boot as a payload Thomas Petazzoni
2021-04-29 12:45   ` Bin Meng
2021-04-30  7:49   ` Peter Korsgaard
2021-04-29  7:46 ` [Buildroot] [PATCH 3/4] boot/opensbi: add options to enable/disable image installation Thomas Petazzoni
2021-04-29 12:39   ` Bin Meng
2021-04-29  7:46 ` [Buildroot] [PATCH 4/4] configs/beaglev_defconfig: new defconfig Thomas Petazzoni
2021-04-29 12:44   ` Bin Meng
2021-05-01 14:37   ` Frank Hunleth
2021-04-29 12:39 ` [Buildroot] [PATCH 0/4] Support for the Beagle-V platform Erico Nunes
2021-04-29 13:01   ` Thomas Petazzoni
2021-04-29 13:26     ` Erico Nunes
2021-04-29 13:48       ` Thomas Petazzoni
2021-04-29 13:52         ` Erico Nunes
2021-04-29 14:26           ` Thomas Petazzoni
2021-04-29 14:55             ` Erico Nunes
2021-04-30  0:35   ` Drew Fustini [this message]
2021-04-30  8:27 ` Drew Fustini

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=20210430003527.GA132765@x1 \
    --to=drew@beagleboard.org \
    --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.