From: Lars Poeschel <poeschel@lemonage.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] pcm051: Add support for Phytec phyCORE-AM335x
Date: Wed, 9 Jan 2013 15:23:55 +0100 [thread overview]
Message-ID: <201301091523.55969.poeschel@lemonage.de> (raw)
In-Reply-To: <20130108185837.577D3202B69@gemini.denx.de>
Hello Wolfgang,
thank you for your fast review!
On Tuesday 08 January 2013 at 19:58:37, Wolfgang Denk wrote:
> > +/* DDR RAM defines */
> > +#define DDR_CLK_MHZ 303
>
> Is this really correct? 303 ??
I am quite sure, I read this in a datasheet, but I can not find it anymore. I
set this to 333 now. mtest still works.
...
> Do you plan to use this? Otherwise please just omit such dead code.
>
> > +#ifdef CONFIG_DRIVER_TI_CPSW
> > +static void cpsw_control(int enabled)
> > +{
> > + /* VTP can be added here */
> > +
> > + return;
> > +}
>
> Ditto...
The cpsw driver needs a control function, otherwise the board crashes when
network initializes. On my board this is empty like on am335x_evm.
> > +#define CONFIG_ENV_OVERWRITE 1
>
> Please do not define values for logical variables like this one;
> please fix globally.
Fix globally ? Do you mean, I have to fix that for EVERY board that is in u-
boot, that defines CONFIG_ENV_OVERWRITE with a value to get my patch in?
There are a number of boards doing this wrong!
> > +#define CONFIG_ENV_IS_NOWHERE
>
> Really?
Uuhm. Yes. At the moment I use this uEnv.txt file on sd-card, as I am not
able to use the NAND yet. The env should go to nand later.
Thanks for the other hints you gave. I will address this and send a version 2
soon.
Regards,
Lars
next prev parent reply other threads:[~2013-01-09 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 16:52 [U-Boot] [PATCH 1/2] am33xx: add a pulldown macro to pinmux config Lars Poeschel
2013-01-08 16:52 ` [U-Boot] [PATCH 2/2] pcm051: Add support for Phytec phyCORE-AM335x Lars Poeschel
2013-01-08 18:58 ` Wolfgang Denk
2013-01-09 14:23 ` Lars Poeschel [this message]
2013-01-09 19:34 ` Tom Rini
2013-01-10 7:30 ` Lars Poeschel
2013-01-10 15:14 ` 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=201301091523.55969.poeschel@lemonage.de \
--to=poeschel@lemonage.de \
--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