From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/7] omap3: zoom1: enable bootz
Date: Tue, 8 Apr 2014 12:22:18 -0400 [thread overview]
Message-ID: <20140408162218.GP23803@bill-the-cat> (raw)
In-Reply-To: <CAGo_u6rkvmQdFPzXQGPqDceMnkNHAzrL47+vOhXSXsP9jW6Vgw@mail.gmail.com>
On Tue, Apr 08, 2014 at 09:35:29AM -0500, Nishanth Menon wrote:
> On Mon, Apr 7, 2014 at 9:29 AM, Tom Rini <trini@ti.com> wrote:
> > On Thu, Apr 03, 2014 at 06:19:25PM -0500, Nishanth Menon wrote:
> >
> >> Boot from zImage and fdt_file if uImage is not available to maintain
> >> the legacy behavior.
> > [snip]
> >> #define CONFIG_EXTRA_ENV_SETTINGS \
> >> "loadaddr=0x82000000\0" \
> >> + "fdt_high=0xffffffff\0" \
> >> + "fdtaddr=0x80f80000\0" \
> >
> > OK, how much memory does this board ever have? If less than 512MB,
> > don't do fdt_high. If 256MB or more, please put fdtaddr at base+128MB.
> > Thanks!
>
> As per the board dts in kernel, this platform has 128MB. As per the
> configuration files, CS1 might not be populated on many boards as
> well. so 128MB seems to be the max memory available here.
I never trust the dts in the kernel wrt memory size, at least for TI
platforms as it's always 128MB and we've always gotten by with a
run-time fixup (or people not noticing their board had less memory than
it really does). And, aside, they ought to adapt the PowerPC convention
of saying 0 for memory size so it's clear that the value is fixed up
elsewhere.
> just remove fdt_high?
Yup.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140408/5ddd2f99/attachment.pgp>
next prev parent reply other threads:[~2014-04-08 16:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 23:19 [U-Boot] [PATCH 0/7] omap3: zoom1: long pending cleanups :( Nishanth Menon
2014-04-03 23:19 ` [U-Boot] [PATCH 1/7] omap3: zoom1: enable CONFIG_SYS_GENERIC_BOARD Nishanth Menon
2014-04-03 23:19 ` [U-Boot] [PATCH 2/7] OMAP3: zoom1: Configure GPMC for Ethernet Nishanth Menon
2014-04-03 23:19 ` [U-Boot] [PATCH 3/7] OMAP3: zoom1: enable LAN9211 Nishanth Menon
2014-04-03 23:19 ` [U-Boot] [PATCH 4/7] omap3: zoom1: enable common network commands Nishanth Menon
2014-04-03 23:19 ` [U-Boot] [PATCH 5/7] omap3: zoom1: disable JFFS2 and enable FS_GENERIC Nishanth Menon
2014-04-07 14:27 ` Tom Rini
2014-04-03 23:19 ` [U-Boot] [PATCH 6/7] omap3: zoom1: enable bootz Nishanth Menon
2014-04-07 14:29 ` Tom Rini
2014-04-08 14:35 ` Nishanth Menon
2014-04-08 16:22 ` Tom Rini [this message]
2014-04-08 16:25 ` Nishanth Menon
2014-04-03 23:19 ` [U-Boot] [PATCH 7/7] omap3: zoom1: fix default console Nishanth Menon
2014-04-07 14:25 ` [U-Boot] [PATCH 0/7] omap3: zoom1: long pending cleanups :( Tom Rini
2014-04-08 14:40 ` Nishanth Menon
2014-04-08 14:50 ` [U-Boot] [PATCH V2 0/8] " Nishanth Menon
2014-04-08 14:50 ` [U-Boot] [PATCH V2 1/8] omap3: zoom1: enable CONFIG_SYS_GENERIC_BOARD Nishanth Menon
2014-04-08 14:50 ` [U-Boot] [PATCH V2 2/8] OMAP3: zoom1: Configure GPMC for Ethernet Nishanth Menon
2014-04-08 14:50 ` [U-Boot] [PATCH V2 3/8] OMAP3: zoom1: enable LAN9211 Nishanth Menon
2014-04-08 14:50 ` [U-Boot] [PATCH V2 4/8] omap3: zoom1: enable common network commands Nishanth Menon
2014-04-08 14:50 ` [U-Boot] [PATCH V2 5/8] omap3: zoom1: disable JFFS2 and enable FS_GENERIC Nishanth Menon
2014-04-08 14:50 ` [U-Boot] [PATCH V2 6/8] omap3: zoom1: enable bootz Nishanth Menon
2014-04-08 14:50 ` [U-Boot] [PATCH V2 7/8] omap3: zoom1: fix default console Nishanth Menon
2014-04-08 14:50 ` [U-Boot] [PATCH V2 8/8] omap3: zoom1: switch to generic ti_omap3_common config header Nishanth Menon
2014-04-18 13:23 ` [U-Boot] [PATCH V2 0/8] omap3: zoom1: long pending cleanups :( Tom Rini
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=20140408162218.GP23803@bill-the-cat \
--to=trini@ti.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