From: Sascha Hauer <s.hauer@pengutronix.de>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: barebox@lists.infradead.org
Subject: Re: Flash drivers, was: IXP4xx support
Date: Mon, 8 Feb 2010 11:06:11 +0100 [thread overview]
Message-ID: <20100208100611.GA17643@pengutronix.de> (raw)
In-Reply-To: <m3r5owdgy2.fsf_-_@intrepid.localdomain>
On Sun, Feb 07, 2010 at 07:44:05PM +0100, Krzysztof Halasa wrote:
> I also wonder, why are there two NOR flash drivers, old and new?
I started working on the U-Boot flash driver and started making
the different Flash chips (AMD, Intel) and bus widths optional in order
to get the driver smaller. I didn't really get ready with it and
checked it in as a second driver. Sorry for the confusion, I should
have made a seperate branch from it.
>
> Another thing, the drivers seem to support various configurations like
> 4*16 bit (4 physical flash chips in parallel). Does any currently
> supported platform use anything like that? Or maybe all platforms use
> 1*8 or 16-bit config and the extra code is unneeded complexity?
I have seen all bus widths from 8bit to 64bit on my boards. Not all
of them are supported in barebox, but it's not a good idea to remove
support for it.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-02-08 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 21:00 Krzysztof Halasa
2010-02-07 10:50 ` Marc Kleine-Budde
2010-02-07 18:44 ` Flash drivers, was: " Krzysztof Halasa
2010-02-08 10:06 ` Sascha Hauer [this message]
2010-02-11 22:29 ` Krzysztof Halasa
2010-02-08 13:40 ` Sascha Hauer
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=20100208100611.GA17643@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=khc@pm.waw.pl \
/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