From: Joshua Emele <jemele@trellisware.com>
To: linux-omap@vger.kernel.org
Subject: Re: MUSB problem
Date: Mon, 14 May 2012 23:13:12 +0000 (UTC) [thread overview]
Message-ID: <loom.20120515T010853-466@post.gmane.org> (raw)
In-Reply-To: 4F97EE60.4090406@mlbassoc.com
> Actually, I was too hasty saying that this worked even with this
> error. I can ping out from my board, but any higher level of traffic,
> e.g. SSH into the box, falls over
>
> The problems vanish when I disable MUSB DMA.
>
> What gives?
>
I'm also seeing this on a variety of kernels, from 2.6.34 to 3.3.0. I must
explicitly set musb_hdrc.use_dma=n for the smsc95xx card to function.
The latest kernel I have tested this against is:
Linux WC-11003A 3.3.0 #1 PREEMPT Fri May 11 18:05:35 PDT 2012 armv7l GNU/Linux
prev parent reply other threads:[~2012-05-14 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 12:19 MUSB problem Gary Thomas
2012-04-25 12:30 ` Gary Thomas
2012-05-14 23:13 ` Joshua Emele [this message]
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=loom.20120515T010853-466@post.gmane.org \
--to=jemele@trellisware.com \
--cc=linux-omap@vger.kernel.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