From: "Sangmoon Kim" <dogoil@etinsys.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: File System on 64-bit-bus-width Flash memory
Date: Fri, 17 May 2002 10:13:10 +0900 [thread overview]
Message-ID: <003501c1fd40$034dd010$1a11efcb@industrialDiv.hanasys.co.kr> (raw)
In-Reply-To: 20020514111336.A39B411960@denx.denx.de
Hi, all,
Thanks for the helps.
The 64bit buswith MTD support in ftp://ftp.denx.de/pub/LinuxPPC/usr/src/linux-2.4.4-2002-03-21.tar.bz2, which is Wolfgang Denk recommanded, is nice. But... Though it probably works well with MPC8260, it doesn't work with MPC107 which is a memory controller / PCI bridge from motorola. With MPC107 you can't access high 32 bit and low 32 bit separately. Because it doesn't have byte select or word select. Unfortunately my board uses MPC107.
The code in http://www.infradead.org/, which is Allen Curtis recommanded, has a different approach, but with some rack of functionality. First, It did not support probing for 64bit buswidth flash. Second, __raw_readll and __raw_writell, which may be 64bit read write functions, are not exist in kernel.
I changed the infradead code to support 64-bit buswith probing(I referenced the denx code). And made the __raw_writell and __raw_readll using floating load load store operation. I disabled the floating point interrupt to avoid the 'floating point used in kernel' message and re-enabled it. For now I only succeed in probing the chip. Does my approach correct? Is it OK to use floating point operations in kernel or device driver code?
Thank you.
-Sangmoon Kim-
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-17 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 11:05 File System on 64-bit-bus-width Flash memory Sangmoon Kim
2002-05-14 11:13 ` Wolfgang Denk
2002-05-14 13:00 ` Allen Curtis
2002-05-17 1:13 ` Sangmoon Kim [this message]
2002-05-14 11:17 ` Kenneth Johansson
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='003501c1fd40$034dd010$1a11efcb@industrialDiv.hanasys.co.kr' \
--to=dogoil@etinsys.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).