From: Gary Thomas <gary@mlbassoc.com>
To: ken king <kknhuntsville@yahoo.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] PowerPC FEC problems
Date: Sat, 07 May 2005 00:10:00 -0000 [thread overview]
Message-ID: <1115421658.1464.49.camel@hermes> (raw)
In-Reply-To: <20050506231553.27475.qmail@web60221.mail.yahoo.com>
On Fri, 2005-05-06 at 16:15 -0700, ken king wrote:
> IT WORKED!!!! (once anyway)
>
> Much thanks to Mr. Andrew Lunn for telling me to
> read the data book. And to Mr.Gary Thomas for
> confidence, you told me the driver worked.
>
> There are two statements in the FEC description
> that probably should be in bold type:
>
> 1--The DB and buffers must be in external memory.
> Apparently that means, for this version of this
> part, they can not be in EPPC memory.
>
> 2--Something like, to save overhead the FEC DMA
> uses burst. Apparently that means the the DB and
> Buffers MUST be in burstable memory.
What revision of the processor (not just model) do you have?
You can read this off the chip, or by printing the value of
the PVR SPR.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-05-06 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 23:21 ken king
2005-05-07 0:10 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-09 21:04 ken king
2005-05-06 15:26 ken king
2005-05-06 15:49 ` Gary Thomas
2005-05-06 11:44 ken king
2005-05-06 11:49 ` Andrew Lunn
2005-05-06 2:02 ken king
2005-05-06 8:42 ` Andrew Lunn
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=1115421658.1464.49.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=kknhuntsville@yahoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).