From: York Sun <york.sun@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] ls2080ardb: Convert to distro boot
Date: Fri, 13 May 2016 09:21:23 -0700 [thread overview]
Message-ID: <5735FF03.1060702@nxp.com> (raw)
In-Reply-To: <F459369E-AF19-46AE-858E-A7EEBE1B0DB4@suse.de>
On 05/13/2016 07:32 AM, Alexander Graf wrote:
>
>> Am 13.05.2016 um 16:26 schrieb Stuart Yoder <stuart.yoder@nxp.com>:
>>
>>
>>
>>> -----Original Message-----
>>> From: Alexander Graf [mailto:agraf at suse.de]
>>> Sent: Friday, May 13, 2016 7:22 AM
>>> To: u-boot at lists.denx.de
>>> Cc: Stuart Yoder <stuart.yoder@nxp.com>; york sun <york.sun@nxp.com>
>>> Subject: [PATCH 5/5] ls2080ardb: Convert to distro boot
>>>
>>> Most new systems in U-Boot these days make use of the generic "distro"
>>> framework which allows a user to have U-Boot scan for a bootable OS
>>> on all available media types.
>>>
>>> This patch converts the LS2080ARDB board to use that framework instead
>>> of booting from a hard coded flash offset.
>>>
>>> Signed-off-by: Alexander Graf <agraf@suse.de>
>>>
>>> ---
>>>
>>> This obviously means that we can no longer boot from said offset. Is
>>> that a reasonable thing to do or should I put the bootm back into the
>>> default boot command and only do distro boot if it fails?
>>
>> To date all armv8 FSL/NXP sdk releases, field engineers, etc have been using
>> bootm. I'm a little concerned about changing the default boot command
>> right now...as I assume things will unexpectedly appear to just stop
>> working. Or, is booting from the NOR flash one of the distro boot
>> "media" types?
>
> The problem with boot from NOR is that we have no source of information on what lies where. So distro boot can't have it in its target list, as you have to know magical offsets.
>
> We could put the magical bootm after tge distro list, but that would mean that field engineers get pxe boot with long timeouts first and then their NOR bootm booted.
>
> So the only option left that I can see is to always try magical offset NOR bootm and do distro boot if it fails. Then just tell people to write zeros to the NOR kernel offset and they get distro boot automatically.
>
Alex,
I suggest to attempt current boot method before moving on to other sources. I
presume booting from NOR would check the image header first. If the image is
valid, go ahead to boot it. Otherwise, move on.
Beside, it would be helpful to define a list and order of boot source.
York
next prev parent reply other threads:[~2016-05-13 16:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 12:21 [U-Boot] [PATCH 0/5] LS2080ARDB: Enable EFI boot support Alexander Graf
2016-05-13 12:21 ` [U-Boot] [PATCH 1/5] ls2080: Exit dpaa only right before exiting U-Boot Alexander Graf
2016-05-18 12:29 ` Prabhakar Kushwaha
2016-05-27 14:27 ` Alexander Graf
2016-06-07 1:28 ` Prabhakar Kushwaha
2016-06-19 21:58 ` Alexander Graf
2016-06-20 6:24 ` Alexander Graf
2016-05-13 12:21 ` [U-Boot] [PATCH 2/5] ls2080: Disable dcache during ddr init Alexander Graf
2016-05-13 16:28 ` York Sun
2016-05-13 19:43 ` Alexander Graf
2016-05-18 12:17 ` Prabhakar Kushwaha
2016-05-13 12:21 ` [U-Boot] [PATCH 3/5] efi_loader: AArch64: Run EFI payloads in EL2 if U-Boot runs in EL3 Alexander Graf
2016-05-13 12:21 ` [U-Boot] [PATCH 4/5] ls2080ardb: Reserve DP-DDR RAM Alexander Graf
2016-05-13 12:21 ` [U-Boot] [PATCH 5/5] ls2080ardb: Convert to distro boot Alexander Graf
2016-05-13 14:26 ` Stuart Yoder
2016-05-13 14:31 ` Alexander Graf
2016-05-13 16:21 ` York Sun [this message]
2016-05-13 17:03 ` Alexander Graf
2016-05-13 17:05 ` York Sun
2016-05-13 19:36 ` Alexander Graf
2016-05-13 19:52 ` York Sun
2016-05-14 21:21 ` Bhupesh Sharma
2016-05-16 6:58 ` Amit Tomer
2016-05-16 7:38 ` Alexander Graf
2016-05-16 12:04 ` Bhupesh Sharma
2016-05-16 12:21 ` Alexander Graf
2016-05-16 13:23 ` Bhupesh Sharma
2016-05-16 13:49 ` Peter Newton
2016-05-13 19:42 ` [U-Boot] [PATCH v2 " Alexander Graf
2016-05-15 20:33 ` [U-Boot] [PATCH v3 " Alexander Graf
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=5735FF03.1060702@nxp.com \
--to=york.sun@nxp.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