public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mkimage: rockchip: add suport for rk33 serial
Date: Fri, 15 Jul 2016 09:40:11 +0800	[thread overview]
Message-ID: <57883EFB.8060103@rock-chips.com> (raw)
In-Reply-To: <45bec492-4ada-cb29-8325-4e7e8e925477@suse.de>

Hi Andreas,

On 07/14/2016 12:26 PM, Andreas F?rber wrote:
> Am 14.07.2016 um 05:51 schrieb Kever Yang:
>> Add support for rockchip rk33 series Soc like rk3368 and rk3399
>>
>> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
>> ---
>>
>>   tools/rkcommon.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/tools/rkcommon.c b/tools/rkcommon.c
>> index 72621fd..9ec7eb2 100644
>> --- a/tools/rkcommon.c
>> +++ b/tools/rkcommon.c
>> @@ -56,6 +56,7 @@ struct spl_info {
>>   static struct spl_info spl_infos[] = {
>>   	{ "rk3036", "RK30", 0x1000 },
>>   	{ "rk3288", "RK32", 0x8000 },
>> +	{ "rk33xx", "RK33", 0x20000 },
> Is xx really future-safe or would it be better to have two lines with
> the exact model names as before?
Two information here, one is TAG 'RK33' which used by bootrom, they are 
the same
for rk33 series SoC; another is SPL size which is depend on IRAM size, 
this is
different for different SoC, rk3368 is smaller than rk3399.

I will use rk3399 first, but we may need to optimize the size limit 
later for the tool,
because the image in Rockchip IDB format could be two parts, one like 
SPL should
be run in IRAM, and another one like U-boot can be run in DRAM, the tool 
only
consider the SPL part now.

Thanks,
- Kever
>
> Cheers,
> Andreas
>
>>   };
>>   
>>   static unsigned char rc4_key[16] = {
>>
>

  reply	other threads:[~2016-07-15  1:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14  3:51 [U-Boot] [PATCH] mkimage: rockchip: add suport for rk33 serial Kever Yang
2016-07-14  4:26 ` Andreas Färber
2016-07-15  1:40   ` Kever Yang [this message]
2016-07-15  3:20 ` Simon Glass
2016-07-15  3:56   ` Simon Glass
2016-07-16 16:04     ` Andreas Färber
2016-07-17 14:14       ` Simon Glass

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