From: Scott Wood <scottwood@freescale.com>
To: David Beamonte <dbeamonte@telnet-ri.es>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Host USB issue on MPC8272
Date: Fri, 05 Sep 2008 10:17:11 -0500 [thread overview]
Message-ID: <48C14D77.4040001@freescale.com> (raw)
In-Reply-To: <48C0DD6F.8070205@telnet-ri.es>
David Beamonte wrote:
> This issue seems to be related to one problem that we have always had.
> We can't configure buffers of SMCs, SCCs, etc, to be in SDRAM, because
> the processor hangs. We always have to configure buffers in DPRAM. In
> other drivers this has not been a problem, because the buffer size is
> not very large, so we can allocate it in DPRAM, but for this one, the
> buffer size is 0x8000 (32Kb) which exceeds DPRAM size.
>
> Has anybody had the same problem? Can it be an USB specific problem or a
> general one?
Make sure that BCR[PLDP] is not set, as per erratum SIU18.
-Scott
next prev parent reply other threads:[~2008-09-05 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 7:19 Host USB issue on MPC8272 David Beamonte
2008-09-05 15:17 ` Scott Wood [this message]
2008-09-08 14:24 ` David Beamonte
2008-09-09 6:18 ` David Beamonte
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=48C14D77.4040001@freescale.com \
--to=scottwood@freescale.com \
--cc=dbeamonte@telnet-ri.es \
--cc=linuxppc-embedded@ozlabs.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).