From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC/PATCH 1/4] Enable multi chip support in the NAND layer
Date: Mon, 19 Jan 2009 18:21:14 +0100 [thread overview]
Message-ID: <200901191821.15116.sr@denx.de> (raw)
In-Reply-To: <20090119170804.GA23019@ld0162-tx32.am.freescale.net>
On Monday 19 January 2009, Scott Wood wrote:
> > > Actually, none of the boards use multi-chip support (NAND_MAX_CHIPS >
> > > 1). The bamboo and the DU440 define
> > >
> > > #define NAND_MAX_CHIPS CONFIG_SYS_MAX_NAND_DEVICE
> > >
> > > but that's bogus and did not work yet anyhow.
> >
> > Not sure what you mean by this. Bamboo has 2 NAND chips and U-Boot can
> > access both chips.
>
> Are they accessed as 2 NAND controllers, or 2 chips on one controller?
2 chips on one controller.
> We can make it "#define NAND_MAX_CHIPS 2" if that's appropriate, but
> defining it to CONFIG_SYS_MAX_NAND_DEVICE doesn't seem to make sense.
OK with me.
Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2009-01-19 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 18:53 [U-Boot] [RFC/PATCH 1/4] Enable multi chip support in the NAND layer Wolfgang Grandegger
2009-01-15 22:17 ` Scott Wood
2009-01-16 7:59 ` Wolfgang Grandegger
2009-01-16 8:22 ` Wolfgang Denk
2009-01-16 17:15 ` Wolfgang Grandegger
2009-01-19 16:12 ` Stefan Roese
2009-01-19 17:08 ` Scott Wood
2009-01-19 17:21 ` Stefan Roese [this message]
2009-01-19 19:50 ` Wolfgang Grandegger
2009-01-20 7:40 ` Stefan Roese
2009-01-20 8:36 ` Wolfgang Grandegger
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=200901191821.15116.sr@denx.de \
--to=sr@denx.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