From: Dan Malek <dan@embeddededge.com>
To: "Penn, John" <jpenn@magisnetworks.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8250 idma problem - cache?
Date: Mon, 17 Mar 2003 18:24:34 -0500 [thread overview]
Message-ID: <3E765932.7040206@embeddededge.com> (raw)
In-Reply-To: BD92DBD34D62AC4FA034933E33E53F7E1724D5@grog
Penn, John wrote:
> ...I seem
> to have a transmit problem that could be explained
> by the dcache holding the packet,
I guess you mean you wrote something into memory and
the IDMA didn't move it to the device on the local bus?
Can you use a bus analyzer to ensure the IDMA actually
ran as expected? What DMA mode are you using?
> snooping - tried enabling it on tx DGBL, no difference
> SIUMCR - ESE is enabled
If I understand "transmitting", that would be from main memory
to the device, so you need to set SGBL.
> using local bus memory instead of 603 memory for buffers
> I would rather use 603 memory
If you have a device on the local bus, that would be a wise choice. :-)
> the 8260 is fully cache coherent so you don't have
> to invalidate the dcache.
That's true, but in the case of transmitting you wouldn't want to
invalidate, you would want to flush.
> Now I am at the point of needing some clarification.
>
> 1. Do I have to invalidate dcache and if so how?
You do not need to do this.
> 2. Has anyone used the IDMA with 603 memory or must
> I use local bus memory?
The system (603) memory works fine, it just sounds like you
need to ensure the channel is correctly configured and your
device protocol on the local bus is working correctly.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-17 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 22:56 8250 idma problem - cache? Penn, John
2003-03-17 23:24 ` Dan Malek [this message]
[not found] <BD92DBD34D62AC4FA034933E33E53F7E1724D6@grog>
2003-03-18 14:37 ` 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=3E765932.7040206@embeddededge.com \
--to=dan@embeddededge.com \
--cc=jpenn@magisnetworks.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).