From: Lukasz Majewski <l.majewski@majess.pl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] SPL: NOR: Add CONFIG_SPL_NOR_COPY_ENTIRE_IMAGE define to enable whole image copy from NOR
Date: Wed, 28 Dec 2016 09:52:28 +0100 [thread overview]
Message-ID: <20161228095228.641327e9@jawa> (raw)
In-Reply-To: <361a7fcb-7333-0ed8-e342-2ee8c3538520@denx.de>
Hi Marek,
> On 12/26/2016 05:36 PM, Lukasz Majewski wrote:
> > Hi Marek,
> >
> >> On 11/29/2016 07:18 PM, Tom Rini wrote:
> >>> On Tue, Nov 29, 2016 at 11:50:34AM +0100, Marek Vasut wrote:
> >>>> On 11/29/2016 10:11 AM, Lukasz Majewski wrote:
> >>>>> Hi Marek,
> >>>>>
> >>>>>> On 11/28/2016 10:09 PM, Lukasz Majewski wrote:
> >>>>>>> This define gives the possibility to copy entire image
> >>>>>>> (including header - e.g. u-boot.img) from NOR parallel memory
> >>>>>>> to e.g. SDRAM. The current code only supports loading the raw
> >>>>>>> binary image (the u-boot.bin).
> >>>>>>>
> >>>>>>> The legacy behavior is preserved, since other board don't
> >>>>>>> enabled this option.
> >>>>>>
> >>>>>> Sooooo, what's the usecase again ? ;-)
> >>>>>
> >>>>> :-)
> >>>>>
> >>>>> The use case is to allow u-boot.img being loaded from Parallel
> >>>>> NOR. The current code only supports u-boot.bin.
> >>>>
> >>>> Why is u-boot.bin (or the payload) not sufficient ? Why do you
> >>>> need the header ?
> >>>
> >>> Well, the general use-case and code flow is that we load
> >>> u-boot.img (or a FIT image) and if all else fails, fall back to
> >>> assuming a .bin and a known address).
> >>>
> >> And exactly how is that whole image useful in RAM ? Sorry, I still
> >> do not see it, usually you just need the executable payload,
> >> although even that can be left in flash most of the time.
> >
> > The use case is that I do want to boot from SD card/eMMC and NOR
> > with using u-boot.img.
> >
> > I would like to avoid situation when for NOR I must use u-boot.bin
> > and for eMMC u-boot.img.
> >
> > Such approach keeps things as simple as possible :-)
>
> Oh, so it allows you to detect bitrot for the content in SPI NOR ?
I do not use SPI NOR, it is parallel NOR.
> It's a bit strange we had to use u-boot.bin with SPL there.
>
This is how the legacy system behaves. It uses (by default) Parallel
NOR for booting (with advised/provided NOR memory timings). After doing
some measurements, it turned out that for "tunned" u-boot/SPL there
would be the best way to copy it to ram and execute it from there (just
like eMMC).
Hence, I would like to use u-boot.img in both booting scenarios.
Best regards,
?ukasz Majewski
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161228/68baa16e/attachment.sig>
next prev parent reply other threads:[~2016-12-28 8:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 8:43 [U-Boot] [PATCH] ML: SPL: NOR: Add CONFIG_SPL_NOR_COPY_ENTIRE_IMAGE define to enable whole image copy from NOR Lukasz Majewski
2016-09-18 18:03 ` Tom Rini
2016-09-18 19:10 ` Lukasz Majewski
2016-09-18 19:24 ` Tom Rini
2016-09-18 23:27 ` Lukasz Majewski
2016-10-07 1:00 ` [U-Boot] " Tom Rini
2016-11-28 6:27 ` [U-Boot] [PATCH] " Lukasz Majewski
2016-11-28 12:43 ` Marek Vasut
2016-11-28 16:50 ` Tom Rini
2016-11-28 17:17 ` Marek Vasut
2016-11-28 21:09 ` Lukasz Majewski
2016-11-28 21:15 ` Marek Vasut
2016-11-29 9:11 ` Lukasz Majewski
2016-11-29 10:50 ` Marek Vasut
2016-11-29 18:18 ` Tom Rini
2016-11-29 18:34 ` Marek Vasut
2016-12-26 16:36 ` Lukasz Majewski
2016-12-27 23:29 ` Marek Vasut
2016-12-28 8:52 ` Lukasz Majewski [this message]
2016-12-28 23:41 ` Marek Vasut
2016-12-29 15:26 ` Tom Rini
2016-12-30 19:08 ` Marek Vasut
2016-12-30 21:28 ` Lukasz Majewski
2016-12-30 21:48 ` Marek Vasut
2016-12-30 21:50 ` Lukasz Majewski
2017-01-02 0:07 ` Lukasz Majewski
2017-01-02 18:57 ` 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=20161228095228.641327e9@jawa \
--to=l.majewski@majess.pl \
--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