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 00:56:33 -0500 [thread overview]
Message-ID: <3A629111.3F36CDE8@mvista.com> (raw)
In-Reply-To: 3A6283A7.C4327446@primenet.com
Bob Doyle wrote:
>
> I have an embedded platform (MPC8240) that requires flash memory
> be programmed 64-bits at a time. I believe that a floating-point
> store is the only way to generate this 64-bit write. I also
> understand that floating-point usage is prohibited in the kernel
> because the floating-point context is not saved.
Didn't you ask this not long ago?
Why does the flash memory need to be programmed 64-bits at a time?
Did you actually find some devices like this? If you have 8 8-bit,
or 4 16-bit devices, you can program these one at a time. Oh, that's
right, you didn't design the hardware correctly.........
Why do you have to do this in the kernel?
> How close am I?
Still pretty far off the mark, even if the assembler is OK. You need
to enable the FPU, which presents another set of problems that can
be somewhat eliminated by disabling interrupts.
If you can't write less than 64-bits, how do you ensure the memory
controller will always generate a cycle to read 64-bits? Sounds like
you have designed around lots of luck.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-15 5:56 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 [this message]
2001-01-16 2:47 ` Bob Doyle
2001-01-16 4:39 ` Dan Malek
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=3A629111.3F36CDE8@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).