From: David Brownell <david-b@pacbell.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [patch arm/next] dm355 evm support (v2)
Date: Mon, 11 May 2009 18:56:06 -0700 [thread overview]
Message-ID: <200905111856.06754.david-b@pacbell.net> (raw)
In-Reply-To: <20090512004014.GH18336@game.jcrosoft.org>
On Monday 11 May 2009, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > +#define BIT(x) (1 << (x))
>
> please remove
> or use set_bit
I think that should probably be added to all the bitops.h headers,
or someplace similar. But, OK; __{set,clear}_bit() work here too.
> > +/*#define CONFIG_SYS_NAND_SMALLPAGE */
>
> please remove if no need
OK, I'll just make a later #ifdef have an #else for that,
kicking in when someone swaps out the largepage chip for
a smallpage one.
> > +#define CONFIG_SYS_NAND_LARGEPAGE
> > +#define CONFIG_SYS_NAND_BASE_LIST { 0x02000000, }
> > +/* socket has two chipselects, nCE0 gated by address BIT(14) */
> > +#define CONFIG_SYS_MAX_NAND_DEVICE 1
> > +#define CONFIG_SYS_NAND_MAX_CHIPS 2
> > +
> > +/* USB: OTG connector */
> > +/* #define CONFIG_USB_DAVINCI */
> please remove if no need
That's a "NYET". It initializes a bit differently on this
board because the on-chip PHY is newer, and also interchanges
the D+/D- lines for better signal routing. It's there as a
placeholder, and will be enabled later.
> > +
> > +/*#define CONFIG_BOOTDELAY 5 */
> please remove if no need
Again a NYET. When the NAND support kicks in, there will
be an environment, and this can be enabled. Until then,
it's a placeholder ... when booting from MMC, UART or JTAG,
with no environment, hands-off booting is ill-advised.
Updated patch coming soon.
- dave
prev parent reply other threads:[~2009-05-12 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 22:43 [U-Boot] [patch arm/next] dm355 evm support (v2) David Brownell
2009-05-12 0:40 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-12 1:56 ` David Brownell [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=200905111856.06754.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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