linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Bob Doyle <doyle@primenet.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: GCC PPC Inline Assembly Help
Date: Mon, 15 Jan 2001 23:39:02 -0500	[thread overview]
Message-ID: <3A63D066.F050245C@mvista.com> (raw)
In-Reply-To: 3A63B634.44E32CF8@primenet.com


Bob Doyle wrote:

> Nope.

Sorry.  I've seen a couple of questions about this lately.

> The MPC8240 can only read/write 64 bits at a time when the PortX/Flash
> bus is configured to be 64 bits wide.

Oh, you tried to find a use for PortX beyond just simple stuff :-).
I thought is was on the 60x bus.

> The MPC8240 doesn't have 'byte-lane' signals for the FLASH

Yes, yes....

> Flash file system.

I was afraid that was the answer :-).


> .....That's why I'm trying
> to force the 64-bit write to use fr0, so I can save/restore it's
> value.  Thus the need for inline asm in gcc.

Or, just write a simple assembler function and stick it in misc.S
or something.  In a past message I responded with the necessary
steps.....disable all exception, enable FPU, save data register,
do your memory operation, restore the data register, disable FPU,
enable exceptions.

The other thing that would work is to copy-back cache the space
and use cache operations to clear and push the cache line.

> Actually I'm using it the way that Circle-M meant it to be used.

Well.....If you notice in any of their documentation, they only
show ROM interfaces in 64-bit mode.  Their Flash examples are either
8- or 32-bit with external logic to decode chip enables.....

Have Fun :-)!


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-01-16  4:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15  4:59 GCC PPC Inline Assembly Help Bob Doyle
2001-01-15  5:56 ` Dan Malek
2001-01-16  2:47   ` Bob Doyle
2001-01-16  4:39     ` Dan Malek [this message]

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=3A63D066.F050245C@mvista.com \
    --to=dan@mvista.com \
    --cc=doyle@primenet.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).