From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/6] arm: omap-common: Guard some parts of the code with CONFIG_OMAP44XX/OMAP54XX
Date: Wed, 16 Mar 2016 21:57:11 -0400 [thread overview]
Message-ID: <20160317015711.GC23166@bill-the-cat> (raw)
In-Reply-To: <1458140588-28276-6-git-send-email-trini@konsulko.com>
On Wed, Mar 16, 2016 at 11:03:08AM -0400, Tom Rini wrote:
> On OMAP4 platforms that also need to calculate their DDR settings we are
> now getting very close to the linker limit size. Since OMAP44XX is only
> seen with LPDDR2, remove some run time tests for LPDDR2 or DDR3 as we
> will know that we don't have it for OMAP44XX.
>
> Cc: Nishanth Menon <nm@ti.com>
> Signed-off-by: Tom Rini <trini@konsulko.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160316/757e59ed/attachment.sig>
next prev parent reply other threads:[~2016-03-17 1:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 15:03 [U-Boot] [PATCH 1/6] ARM: keystone2: Split monitor code / command code Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 2/6] ARM: keystone2: Switch to using the poweroff command Tom Rini
2016-03-17 1:56 ` Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 3/6] ARM: keystone2: Only link cmd_ddr3.o on non-SPL builds Tom Rini
2016-03-17 1:56 ` Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 4/6] cmd: scsi: Group the command portion together, guard with !CONFIG_SPL_BUILD Tom Rini
2016-03-17 1:57 ` Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 5/6] lpc32xx: work_92105: Rework Makefile Tom Rini
2016-03-17 1:57 ` Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 6/6] arm: omap-common: Guard some parts of the code with CONFIG_OMAP44XX/OMAP54XX Tom Rini
2016-03-17 1:57 ` Tom Rini [this message]
2016-03-16 17:15 ` [U-Boot] [PATCH 1/6] ARM: keystone2: Split monitor code / command code Albert ARIBAUD
2016-03-16 19:02 ` Tom Rini
2016-03-17 1:56 ` 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=20160317015711.GC23166@bill-the-cat \
--to=trini@konsulko.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.