From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1] arm: socfpga: Enable load zImage and Linux DTB from QSPI
Date: Fri, 27 Nov 2015 09:24:49 +0800 [thread overview]
Message-ID: <1448587489.1908.4.camel@altera.com> (raw)
In-Reply-To: <20151126144356.GA25328@amd>
Hi Pavel,
On Thu, 2015-11-26 at 15:43 +0100, Pavel Machek wrote:
> Hi!
>
> > Adding new environment qspiload which will load zImage and
> > Linux DTB from serial NOR flash. The default flash offset for
> > the images as below and they are configurable during run time.
> >
> > - zImage located at 0xa0000 with assuming file size 6MB
> > - Linux DTB located at 0x50000 with assuming file size 28kB
>
> Hmm. Ok, zImage second, so that it can grow. Makes sense. Not sure if
> 28kB is not a bit small for DTB. I'd reserve at least 64kB.
Yup, it can grow up to 64kB as the size for a sector. We used 28KB
mainly for boot time performance.
>
> > Please adjust the file size env var if exceeding the default
> >
> > Signed-off-by: Chin Liang See <clsee@altera.com>
> > Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
> > Cc: Dinh Nguyen <dinh.linux@gmail.com>
>
> Acked-by: Pavel Machek <pavel@denx.de>
>
> Notice that you sent two patches marked "v1".
Haha too obsess with the -v argument within git format-patch :P
Thanks
Chin Liang
>
> Thanks,
> Pavel
next prev parent reply other threads:[~2015-11-27 1:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 2:32 [U-Boot] [PATCH v1] arm: socfpga: Enable load zImage and Linux DTB from QSPI Chin Liang See
2015-11-26 6:12 ` Stefan Roese
2015-11-27 1:26 ` Chin Liang See
2015-11-26 14:43 ` Pavel Machek
2015-11-27 1:24 ` Chin Liang See [this message]
2015-11-27 1:27 ` Marek Vasut
2015-11-27 1:34 ` Chin Liang See
2015-11-27 10:20 ` Marek Vasut
2015-11-27 12:07 ` Chin Liang See
2015-11-27 12:11 ` Marek Vasut
2015-11-27 12:16 ` Chin Liang See
2015-11-27 12:26 ` Marek Vasut
2015-11-27 13:08 ` Chin Liang See
2015-11-27 14:24 ` 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=1448587489.1908.4.camel@altera.com \
--to=clsee@altera.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 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.