From: "Dominique Letty" <dletty@interfaceconcept.com>
To: "'John Nikiforos'" <ppclinuxuser@yahoo.gr>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Problem with MPC8260 buffer descriptor
Date: Thu, 17 Oct 2002 14:36:51 +0200 [thread overview]
Message-ID: <000e01c275da$33148ba0$3501a8c0@none> (raw)
In-Reply-To: <20021017075647.54441.qmail@web13114.mail.yahoo.com>
I don't find any information about this ECE bit in MPC8260UM and 603eUM.
Where can I enable it?
Thinks for your help.
Dominique
-----Message d'origine-----
De : John Nikiforos [mailto:ppclinuxuser@yahoo.gr]
Envoye : jeudi 17 octobre 2002 09:57
A : acurtis@onz.com; Dominique Letty; linuxppc-embedded@lists.linuxppc.org
Objet : RE: Problem with MPC8260 buffer descriptor
Is the ECE bit enabled?
(Cache coherency for the 8260, so that the
CPM wont get any stalled data)
John
--- Allen Curtis <acurtis@onz.com> έγραψε: >
> > Now I try to port this driver under Linux 2.4.17
> Kernel for a MPC8260. I
> > have allocated
> > Buffer Descriptors in DPRAM and Data Buffers in
> SDRAM. When I try
> > to send a
> > buffer, I fill
> > a data buffer and the first BD registers, I think,
> with the
> > correct values.
> > It doesn't work
> > anytimes. When the buffer is transmited, the
> sending data are correct. The
> > problem seems to
> > come from the CPM which can't access to the BD
> modifications in the DPRAM.
> >
> > Does anyone have already meet these problems?
>
> Would it be a problem to post your:
>
> 1. GSMRH & GSRM_L initialization
> 2. SCC Parameter RAM configuration
> 3. Location of your BDs in DPRAM
>
> THX
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-17 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 14:56 Problem with MPC8260 buffer descriptor Dominique Letty
2002-10-16 15:15 ` Allen Curtis
2002-10-17 7:56 ` John Nikiforos
2002-10-17 12:36 ` Dominique Letty [this message]
2002-10-17 13:50 ` John Nikiforos
2002-10-17 14:30 ` Allen Curtis
2002-10-17 16:54 ` Dominique Letty
2002-10-17 17:08 ` Dominique Letty
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='000e01c275da$33148ba0$3501a8c0@none' \
--to=dletty@interfaceconcept.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ppclinuxuser@yahoo.gr \
/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).