From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] cfi_flash is now working with 64 bit port width
Date: Fri, 01 Jul 2005 11:25:20 -0500 [thread overview]
Message-ID: <42C56E70.5060800@orkun.us> (raw)
In-Reply-To: <20050630235942.CFEDE353A1B@atlas.denx.de>
Wolfgang Denk wrote:
>>That way, any board with custom data bus (reversed lanes for example) or
>>address bus (messed up address line) arrangements or specialized
>>handling (need floating point) as in this case would override them
>>easily and we would not end up blocks of #if/#elif/#else/#endif etc. in
>>
>>
>
>No. The whole idea of the CFI flash driver is to have standard code
>for all boards. If your design does not fit the standard, then
>provide your own non-standard driver. Don't add complexity to the CFI
>driver - it has just a single advantage (being "standard"), so please
>don't drop this.
>
>
So, you are saying: it is better to have variations of cfi_flash.c in
board directories and maintenance problems because of code forking of
cfi_flash.c code is better than having the possibility of board specific
read/write access functions. By doing this we not only would save the
day and solve his problem but make cfi_flash.c useful to a broader
application.
For some reason, my mind works to factor common code. It does not make
sense for me but you are the boss.
>>the cfi_flash.c. The board would also enable FP unit in its board file
>>or within these functions if necessary as well.
>>
>>
>
>"enabling FP" has nothing to do with this. The FPU is never disabled
>or so. It's just that the compiler is told to never emit any FP
>instructions :-)
>
>
He had to modify MSR before using FP instructions as well. That was what
I was pointing to.
Best regards,
Tolunay
next prev parent reply other threads:[~2005-07-01 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 8:23 [U-Boot-Users] cfi_flash is now working with 64 bit port width Yusuf Ibrahim Ozkok
2005-06-30 10:29 ` Yuli Barcohen
2005-06-30 20:42 ` Tolunay Orkun
2005-06-30 21:02 ` Wolfgang Denk
2005-06-30 21:53 ` Tolunay Orkun
2005-06-30 23:59 ` Wolfgang Denk
2005-07-01 16:25 ` Tolunay Orkun [this message]
2005-07-01 16:09 ` Yusuf Ibrahim Ozkok
2005-07-01 22:53 ` Wolfgang Denk
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=42C56E70.5060800@orkun.us \
--to=listmember@orkun.us \
--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