From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: "Trent Piepho" <tpiepho@freescale.com>
Cc: linuxppc-dev@ozlabs.org, u-boot@lists.denx.de,
Stefan Roese <sr@denx.de>,
Norbert van Bolhuis <nvbolhuis@aimvalley.nl>,
Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: [U-Boot] NAND only (no NOR)
Date: Wed, 3 Dec 2008 14:57:24 +0100 [thread overview]
Message-ID: <c384c5ea0812030557q1293a2beo3a306e176c306e0a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812022339030.10176@t2.domain.actdsltmp>
Hello,
On Wed, Dec 3, 2008 at 8:40 AM, Trent Piepho <tpiepho@freescale.com> wrote:
> On Wed, 3 Dec 2008, Sean MacLennan wrote:
>>> Yes, I would recommend to do it this way if possible. A small NOR for
>>> U-Boot and environment and everything else in NAND. This makes things
>>> much easier. But I understand that this is sometimes a problem with
>>> space (2 FLASH chips) and costs.
>>
>> Mainly cost. We didn't want to pay for a second chip.
>
> I think for NAND the latches necessary to de-multiplex the localbus aren't
> necessary like they are for NOR? On our board the latches might even take
> more space than the flash chip.
The local bus can be configured to run non-multiplexed.
Regards,
--
Leon
prev parent reply other threads:[~2008-12-03 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 8:55 NAND only (no NOR) Norbert van Bolhuis
2008-12-02 9:31 ` [U-Boot] " Alessandro Rubini
2008-12-03 2:50 ` Sean MacLennan
2008-12-03 5:48 ` [U-Boot] " Stefan Roese
2008-12-03 6:38 ` Sean MacLennan
2008-12-03 7:40 ` Trent Piepho
2008-12-03 13:57 ` Leon Woestenberg [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=c384c5ea0812030557q1293a2beo3a306e176c306e0a@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nvbolhuis@aimvalley.nl \
--cc=smaclennan@pikatech.com \
--cc=sr@denx.de \
--cc=tpiepho@freescale.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;
as well as URLs for NNTP newsgroup(s).