From: Michael Thompson <mickey@berkeley.innomedia.com>
To: mtd@infradead.org
Subject: Re: CFI problems with 32bit bus and 4 devices
Date: Wed, 10 Jan 2001 14:45:23 -0800 (PST) [thread overview]
Message-ID: <200101102245.OAA31035@berkeley.innomedia.com> (raw)
dwmw2 wrote:
>
> Technically, I think this setup would fit into the original model as
> buswidth == 8, and we should be using read64/write64 for accesses to the
> flash.
>
> Just how crap is gcc's long long support these days? Could we use __u64
> for this?
Actually, I just got buswidth==8 working on a 32-bit ppc (my configuration
is 4 devices in 16 bit mode). However, I found that I could use __u64 for
passing data around, but __u64 would not work when accessing the devices..
For this, I had to use a little trick: floating point loads and stores.
On the ppc, these are 64 bits wide.
I'd be willing to submit patches... Shall I send them to you?
-Michael Thompson
mickey@berkeley.innomedia.com
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2001-01-10 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 22:45 Michael Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 19:15 CFI problems with 32bit bus and 4 devices Stéphane Laroche
2001-01-10 20:13 ` Nicolas Pitre
2001-01-10 20:37 ` David Woodhouse
2001-01-10 21:06 ` Stéphane Laroche
2001-01-10 22:35 ` David Woodhouse
2001-01-10 21:37 ` Nicolas Pitre
2001-01-10 22:22 ` David Woodhouse
2001-01-10 22:39 ` Stéphane Laroche
2001-01-10 23:06 ` David Woodhouse
2001-01-11 0:21 ` Nicolas Pitre
2001-01-10 23:34 ` Alice Hennessy
2001-01-10 23:55 ` Alice Hennessy
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=200101102245.OAA31035@berkeley.innomedia.com \
--to=mickey@berkeley.innomedia.com \
--cc=mtd@infradead.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