public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v2] vexpress64: use 2nd DRAM bank only on juno
Date: Fri, 13 Nov 2015 08:25:05 -0500	[thread overview]
Message-ID: <20151113132505.GG8060@bill-the-cat> (raw)
In-Reply-To: <CAD0U-hKB=sO_xxQY5CfTz+XHpvbzsbqq=Uq24OH6WUDkryifZg@mail.gmail.com>

On Fri, Nov 13, 2015 at 08:26:31AM +0000, Ryan Harkin wrote:
> Hi Tom,
> 
> Thanks for coming back to this.
> 
> On 12 November 2015 at 20:58, Tom Rini <trini@konsulko.com> wrote:
> > On Mon, Oct 26, 2015 at 11:00:22AM +0000, Ryan Harkin wrote:
> >
> >> This patch makes the 2nd DRAM bank available on Juno only and not on
> >> other vexpress64 targets, eg. the FVP models.
> >>
> >> The commit below added a 2nd bank of NOR flash for Juno, but also for
> >> all vexpress64 targets:
> >>
> >>     commit 2d0cee1ca2b9d977fa3214896bb2e30cfec77059
> >>     Author: Liviu Dudau <Liviu.Dudau@foss.arm.com>
> >>     Date:   Mon Oct 19 11:08:31 2015 +0100
> >>
> >>     vexpress64: Juno: Declare all 8GB of RAM and make them visible to the kernel.
> >>
> >>     Juno comes with 8GB RAM, but U-Boot only passes 2GB to the kernel.
> >>     Declare a secondary memory bank and set the sizes correctly.
> >>
> >>     Signed-off-by: Liviu Dudau <Liviu.Dudau@foss.arm.com>
> >>     Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> >>     Reviewed-by: Ryan Harkin <ryan.harkin@linaro.org>
> >>     Tested-by: Ryan Harkin <ryan.harkin@linaro.org>
> >>
> >> Unfortunately, I only fully tested on Juno R0, R1 and the FVP Foundation
> >> model.  Whilst FVP Base AEMV8 models run U-Boot OK, they fail to boot
> >> the kernel.
> >>
> >> Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
> >> Acked-by: Liviu Dudau <liviu.dudau@foss.arm.com>
> >> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> >
> > This breaks building of vexpress_aemv8a_semi :(
> 
> Yes, I see the problem now :(
> 
> If I apply this to pure upstream, I get this error, which I assume is
> the same as yours:
> 
> board/armltd/vexpress64/pcie.c: In function 'xr3pci_setup_atr':
> board/armltd/vexpress64/pcie.c:111:29: error: 'PHYS_SDRAM_2'
> undeclared (first use in this function)
>   xr3pci_set_atr_entry(base, PHYS_SDRAM_2, PHYS_SDRAM_2,
> 
> This error was fixed by Linus Walleij's patch that I carry in my u-boot fork:
> 
> [PATCH] vexpress64: compile Juno PCIe conditionally
> 
> I'd prefer that Linus' patch is merged, then mine, but if you don't
> want to do that, I can change my patch so that PHYS_SDRAM_2 isn't used
> if it isn't defined.

Didn't I ask for some changes on that PCIe patch?

-- 
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/20151113/a1f59557/attachment.sig>

  reply	other threads:[~2015-11-13 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 11:00 [U-Boot] [PATCH v2] vexpress64: use 2nd DRAM bank only on juno Ryan Harkin
2015-10-27 12:10 ` Linus Walleij
2015-11-11 16:03   ` Ryan Harkin
2015-11-12 20:58 ` [U-Boot] [U-Boot, " Tom Rini
2015-11-13  8:26   ` Ryan Harkin
2015-11-13 13:25     ` Tom Rini [this message]
2015-11-13 13:36       ` Ryan Harkin
2015-11-13 20:23         ` Linus Walleij

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=20151113132505.GG8060@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox