All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] rk3399: Reserve space for ARM Trust Firmware
Date: Fri, 04 Nov 2016 08:43:28 +0800	[thread overview]
Message-ID: <581BD9B0.1050501@rock-chips.com> (raw)
In-Reply-To: <79830e3a-f827-92a9-4fae-9947a02e88c3@suse.de>

Hi Andreas,

On 11/03/2016 09:32 AM, Andreas F?rber wrote:
> Hello,
>
> Am 25.07.2016 um 05:45 schrieb Kever Yang:
>> RK3399 needs reserve 0x200000 at the beginning of DRAM, for ATF bl31.
>>
>> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
>> ---
>>
>> Changes in v2:
>> - correct some typo on commit message and comment
>>
>>   board/rockchip/evb_rk3399/evb-rk3399.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/board/rockchip/evb_rk3399/evb-rk3399.c b/board/rockchip/evb_rk3399/evb-rk3399.c
>> index 39a26fa..84a00fc 100644
>> --- a/board/rockchip/evb_rk3399/evb-rk3399.c
>> +++ b/board/rockchip/evb_rk3399/evb-rk3399.c
>> @@ -35,6 +35,7 @@ int dram_init(void)
>>   
>>   void dram_init_banksize(void)
>>   {
>> -	gd->bd->bi_dram[0].start = 0;
>> +	/* Reserve 0x200000 for ATF bl31 */
>> +	gd->bd->bi_dram[0].start = 0x200000;
>>   	gd->bd->bi_dram[0].size = 0x80000000;
> Doesn't the size need to be deduced by the same amount then?

Yes, you are right, will send a patch to fix this.

Thanks,
- Kever
>
> Regards,
> Andreas
>
>>   }
>>
>

      reply	other threads:[~2016-11-04  0:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25  3:45 [U-Boot] [PATCH v2] rk3399: Reserve space for ARM Trust Firmware Kever Yang
2016-07-28  3:11 ` Simon Glass
2016-07-28  3:33   ` Simon Glass
2016-11-03  1:32 ` Andreas Färber
2016-11-04  0:43   ` Kever Yang [this message]

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=581BD9B0.1050501@rock-chips.com \
    --to=kever.yang@rock-chips.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.