From: Dan Malek <dan@mvista.com>
To: Tim Montgomery <tjmontgo@mailbag.com>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 64 bit memory access
Date: Fri, 29 Dec 2000 13:09:56 -0500 [thread overview]
Message-ID: <3A4CD374.40754688@mvista.com> (raw)
In-Reply-To: 3A4CC527.BF9431A7@mailbag.com
Tim Montgomery wrote:
> I need to:
> 1.) figure out a way to perform a 64bit write via other means
Cache the location. When you access the space the processor will
do a 64-bit read. You will have to run in copyback mode then when
done updating the location push the cache line to the device.
> Any suggestions/insight would be appreciated.
Using 64-bit only I/O, and FP registers on a 32-bit processor is
an interesting hardware/software hack, but not a very good system
design.
I guess we could write some kernel 64-bit I/O functions that use
an FP register. This would require disabling interrupts, enabling
the FPU in the kernel, saving a register, doing the I/O, restoring the
register, disabling the FPU, and enabling interrupts. Not very efficient
when a proper 60x bus implementation that allowed sizing would have
been really fast.........
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-29 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 17:08 64 bit memory access Tim Montgomery
2000-12-29 18:09 ` Dan Malek [this message]
2000-12-29 20:52 ` Tony Mantler
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=3A4CD374.40754688@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tjmontgo@mailbag.com \
/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).