From: Tolunay Orkun <t5amj@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] cfi_flash is now working with 64 bit port width
Date: Thu, 30 Jun 2005 15:42:22 -0500 [thread overview]
Message-ID: <42C4592E.7080009@orkun.us> (raw)
In-Reply-To: <009b01c57d4d$0005c8a0$0606010a@aselsan.com.tr>
Yusuf Ibrahim Ozkok wrote:
> The patch (unformatted):
>
> 1. The following function is added.
> static void write_via_fpu (vu_long * addr, ulong * data)
> {
> __asm__ __volatile__ ("lfd 1, 0(%0)"::"r" (data));
> __asm__ __volatile__ ("stfd 1, 0(%0)"::"r" (addr));
> }
This is probably not acceptable for cfi_flash.c. cfi_flash.c is used by
multiple CPU architectures so PowerPC assembly cannot be used. You have
to find a solution based on "C" only.
> 2. in /drivers/cfi_flash.c
> line 850;
> - *addr.llp = cword.ll;
> + write_via_fpu((vu_long*)addr.llp, (ulong*)&cword.ll);
>
> line 1159;
> - cptr.llp[0] = cword.ll;
> + write_via_fpu((vu_long*)cptr.llp, (ulong*)&cword.ll);
How did you use "double" and it did not work? Please give example of the
work you tried...
If you tried to assign the value to the double variable, the internal
format will be different (IEEE floating point normalized). You can copy
your intended data to the double variable via memcpy() or use a union of
"long long" and "double", assign to "long long" member and use "double"
one for storing.
> Finally, I would like to ask about the Tolunay Orkun's patch about tout
> in flash_status_check function. what is the last thought for that patch
>
> Is it planned to be released? Because it's really a bug! (Last post for
> the thread; http://sourceforge.net/mailarchive/message.php?msg_id=11936556)
I've not forgotten that. I've been extremely busy. I will try to get the
patch in a couple of days.
> Attention:
> This e-mail message is privileged and confidential. If you are not the
> intended recipient please delete the message and notify the sender.
Please get this crap out of mails sent to public mailing lists. By
sending to public lists you cannot make any claim confidentiality... If
you have anything truely confidential do not expect others to protect
it. Just do not send it to the public lists...
Best regards,
Tolunay
next prev parent reply other threads:[~2005-06-30 20:42 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 [this message]
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
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=42C4592E.7080009@orkun.us \
--to=t5amj@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