All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Rae <srae@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] arm: add Cygnus and NSP boards
Date: Mon, 21 Jul 2014 17:02:37 -0700	[thread overview]
Message-ID: <53CDAA1D.2070709@broadcom.com> (raw)
In-Reply-To: <20140720075434.48C31380316@gemini.denx.de>



On 14-07-20 12:54 AM, Wolfgang Denk wrote:
> Dear Steve Rae,
>
> In message <1405733854-20194-5-git-send-email-srae@broadcom.com> you wrote:
>>
>> The bcm_ep board configuration is used by a number of boards
>> including Cygnus and NSP.
>> Add builds for the bcm958300k and the bcm958622hr boards.
> ...
>> +/* uArchitecture specifics */
> ...
>> +#define CONFIG_CONS_INDEX		3
>> +#define CONFIG_SYS_NS16550_COM3		0x18023000
>
> Is the console inex really architecture specific and identical for all
> boards based on this?  I would expect to find this in the board config
> header.
>
Yes -- the bootrom code always uses 3 for this architecture

>> +/* uArchitecture specifics */
> ...
>> +#define CONFIG_CONS_INDEX		1
>> +#define CONFIG_SYS_NS16550_COM1		0x18000300
>
> Ditto here.
Ditto -- the bootrom code always uses 1 for this architecture

>
> ...
>> +	/* Address of boot parameters passed to kernel
>> +	 * Use default offset 0x100
>> +	 */
>
> Incorrect multiline comment style.  Please check (and fix, if needed)
> globally.
will fix in [v2]

>
>> +/*
>> + * misc_init_r - miscellaneous platform dependent initializations
>> + */
>> +int misc_init_r(void)
>> +{
>> +	return 0;
>> +}
>
> It makes no sense to add an empty function here.  Just do not define
> CONFIG_MISC_INIT_R
will fix in [v2]

>
>
>> +#define CONFIG_SYS_MALLOC_LEN		SZ_4M	/* see armv7/start.S. */
>> +#define CONFIG_STACKSIZE		SZ_256K
>
> Please do not use the SZ_ defines.  They are deprecated.
will fix in [v2]

>
>> +/* Init functions */
>> +#define CONFIG_MISC_INIT_R	/* board's misc_init_r function */
>
> Unused, so remove.
will fix in [v2]
>
>> +#define CONFIG_ENV_SIZE			0x10000
>
> Do you really, really need 64 kB of environmnt?  I doubt that.
will fix in [v2]

>
>
> Best regards,
>
> Wolfgang Denk
>

      reply	other threads:[~2014-07-22  0:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-19  1:37 [U-Boot] [PATCH 0/4] Introducing the Broadcom Cygnus and NSP boards Steve Rae
2014-07-19  1:37 ` [U-Boot] [PATCH 1/4] arm: iproc: Initial commit of iproc architecture code Steve Rae
2014-07-20  7:46   ` Wolfgang Denk
2014-07-22  0:27     ` Steve Rae
2014-07-19  1:37 ` [U-Boot] [PATCH 2/4] arm: bcmcygnus: Add bcmcygnus u-architecture Steve Rae
2014-07-19  1:37 ` [U-Boot] [PATCH 3/4] arm: bcmnsp: Add bcmnsp u-architecture Steve Rae
2014-07-19  1:37 ` [U-Boot] [PATCH 4/4] arm: add Cygnus and NSP boards Steve Rae
2014-07-20  7:54   ` Wolfgang Denk
2014-07-22  0:02     ` Steve Rae [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=53CDAA1D.2070709@broadcom.com \
    --to=srae@broadcom.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.