From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot ColdFire development
Date: Fri, 29 Jun 2007 13:56:08 +0200 [thread overview]
Message-ID: <m2sl8b5607.fsf@sowhat.denx.de> (raw)
In-Reply-To: <4791E710007FEB4BBF83775D787F462F047A3F6C@az33exm22.fsl.freescale.net> (Liew Tsi Chung-r5aahp's message of "Tue\, 26 Jun 2007 23\:55\:46 -0700")
Hi Liew,
>> Are you sure that you need this board specific flash driver?
>> Can't you use the common CFI flash driver? What FLASH chips
>> are used on the board?
>
> There is no speed performance in erasing and reading between common CFI
> flash driver and board specific flash driver, except programming. CFI
> flash driver needs ~80s to program 1MB data compare to board specific
> flash driver needs only ~14s. User has a choice to select them either by
> define or undef CFG_FLASH_CFI in configuration file. If there is a 8MB
> flash, it would take about 640s compare to 112s. Big different. I might
> have missed a define for common flash driver in configuration file that
> might caused slow programming in flash, if I do please let me know.
I think Stefans intention of the question was a little bit different.
For the maintainability of U-Boot we should strive to share as many
code as possible between different boards, so for quite sometime now
we generally(*) encourage people to use the CFI driver in order to
achieve this goal.
I am not at all convinced that even a factor of two in programming
times can compensate for the added complexity of Yet Another Custom
Flash Driver.
What would really be interesting is to find out why the CFI driver is
slower. I think fixing this will be a much more worthwhile
contribution to U-Boot as a whole.
Thanks
Detlev
(*) Wolfgang happily allows exceptions for resource limited setups.
--
A statistician can have his head in an oven and his feet in ice, and
he will say that on the average he feels fine.
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2007-06-29 11:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4791E710007FEB4BBF83775D787F462F04749339@az33exm22.fsl.freescale.net>
[not found] ` <200706131523.44148.sr@denx.de>
[not found] ` <4791E710007FEB4BBF83775D787F462F04749874@az33exm22.fsl.freescale.net>
[not found] ` <200706141057.32860.sr@denx.de>
2007-06-21 13:52 ` [U-Boot-Users] U-boot ColdFire development Liew Tsi Chung-r5aahp
2007-06-22 5:46 ` Stefan Roese
2007-06-27 6:55 ` Liew Tsi Chung-r5aahp
2007-06-29 11:56 ` Detlev Zundel [this message]
2007-06-29 17:40 ` Liew Tsi Chung-r5aahp
2007-06-30 2:01 ` Wolfgang Denk
2007-07-03 8:53 ` Stefan Roese
2007-07-03 18:02 ` Liew Tsi Chung-r5aahp
2007-07-04 6:20 ` Stefan Roese
2007-07-06 1:55 ` Liew Tsi Chung-r5aahp
[not found] ` <A6535175C7B95548B81ECF6C91B3C42305261080@az33exm22.fsl.freescale.net>
2007-07-10 23:04 ` Liew Tsi Chung-r5aahp
2007-07-12 14:26 ` Stefan Roese
2007-07-20 12:31 ` Stefan Roese
2007-07-23 22:00 ` Liew Tsi Chung-r5aahp
2007-07-25 15:54 ` w.wegner at astro-kom.de
2007-07-27 0:39 ` Liew Tsi Chung-r5aahp
2007-07-27 4:51 ` Stefan Roese
2007-07-27 18:19 ` Liew Tsi Chung-r5aahp
2007-07-27 19:20 ` Stefan Roese
2007-07-27 7:12 ` w.wegner at astro-kom.de
2007-07-26 15:46 ` w.wegner at astro-kom.de
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=m2sl8b5607.fsf@sowhat.denx.de \
--to=dzu@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