public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dalon Westergreen <dwesterg@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] Distroboot support for DE0-nano-SoC board
Date: Sat, 28 Jan 2017 14:47:24 -0800	[thread overview]
Message-ID: <1485643644.12609.36.camel@gmail.com> (raw)
In-Reply-To: <8a4273d1-1fef-0c95-7abe-b9bf89289262@denx.de>

On Sat, 2017-01-28 at 23:30 +0100, Marek Vasut wrote:
> On 01/28/2017 10:25 PM, Westergreen, Dalon wrote:
> > 
> > On Sat, 2017-01-28 at 21:53 +0100, Marek Vasut wrote:
> > > 
> > > On 01/28/2017 09:47 PM, Frank Kunz wrote:
> > > > 
> > > > 
> > > > This adds common distribution boot environment variables for
> > > > DE0-nanos-SoC board. The current boot procedure is extended to run
> > > > the distribution boot as fallback.
> > > > The SOC ROM loader scans for the SPL in the special partition 0xa2
> > > > (partition mode)
> > > > if this is not found it scans the MMC card sector 0 (raw mode), for up
> > > > to
> > > > four valid SPLs. When a partition table (MBR, GPT) is used with raw
> > > > mode,
> > > > the first SPL must not be written to the MMC and the ROM loader uses the
> > > > second SPL.
> > > > 
> > > > Frank Kunz (3):
> > > > ? socfpga: Enable abort for DE-nano-SoC SPL uboot load from MMC
> > > > ? socfpga: Add distoboot support for DE0-nano-SoC
> > > > ? socfpga: Adapt environment storage for DE0-nano-SoC
> > > > 
> > > > ?include/configs/socfpga_de0_nano_soc.h | 32
> > > > +++++++++++++++++++++++++++++++-
> > > > ?1 file changed, 31 insertions(+), 1 deletion(-)
> > > 
> > > CCing Dalon, he sent a series
> > > [PATCH v7 0/7] arm: socfpga: update default u-boot environment
> > > 
> > > Can you two coordinate the efforts ? I think it'd make sense to wait for
> > > his series to reach v8 and then rebase on top of it. I would also like
> > > Dalon to do a v8 which just extracts the common env, so we can
> > > merge that first and then look into the more intrusive bits.
> > > 
> > Cool, i can submit a v8 which just moves the env to a common location.
> > I have reservations about the use use of raw mode while an MBR is
> > present.??It is definitely not an intended use, although it does
> > work. If you like i can just merge the two patch sets into v8?
> 
> No, please just keep the stuff separate, so we can get something in
> and then move on to the next thing.
> 
Will do, it should be identical to the v6 patches. ?I also have tested
a patch to support searching for the a2 partition to load the uboot image
which i will send afterwards

  reply	other threads:[~2017-01-28 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28 20:47 [U-Boot] [PATCH 0/3] Distroboot support for DE0-nano-SoC board Frank Kunz
2017-01-28 20:47 ` [U-Boot] [PATCH 1/3] socfpga: Enable abort for DE-nano-SoC SPL uboot load from MMC Frank Kunz
2017-01-28 20:47 ` [U-Boot] [PATCH 2/3] socfpga: Add distoboot support for DE0-nano-SoC Frank Kunz
2017-01-28 20:47 ` [U-Boot] [PATCH 3/3] socfpga: Adapt environment storage " Frank Kunz
2017-01-28 20:53 ` [U-Boot] [PATCH 0/3] Distroboot support for DE0-nano-SoC board Marek Vasut
2017-01-28 21:25   ` Westergreen, Dalon
2017-01-28 21:33     ` Frank Kunz
2017-01-28 22:30     ` Marek Vasut
2017-01-28 22:47       ` Dalon Westergreen [this message]
2017-01-28 22:49         ` Marek Vasut

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=1485643644.12609.36.camel@gmail.com \
    --to=dwesterg@gmail.com \
    --cc=u-boot@lists.denx.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