From: David Brownell <david-b@pacbell.net>
To: Koen Kooi <k.kooi@student.utwente.nl>
Cc: "linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>,
Ajay Kumar Gupta <ajay.gupta@ti.com>
Subject: Re: DVB-T problems with MUSB
Date: Tue, 7 Oct 2008 12:32:27 -0700 [thread overview]
Message-ID: <200810071232.27362.david-b@pacbell.net> (raw)
In-Reply-To: <70E3439A-A4CE-442B-928A-EEBAB253F279@student.utwente.nl>
On Tuesday 07 October 2008, Koen Kooi wrote:
> Is this a problem with MUSB, omap dma or the dvb stack?
ISTR a similar problem discussed on Linux-USB in the last
few months ...
Don't recall the outcome for sure, but I think the problem
was the DVB stack passing a DMA-unsafe buffer to USB. If the
buffer came from vmalloc rather than kmalloc or get_pages,
passing it to USB is not allowed.
- Dave
next prev parent reply other threads:[~2008-10-07 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 19:03 DVB-T problems with MUSB Koen Kooi
2008-10-07 19:32 ` David Brownell [this message]
2008-10-07 23:10 ` Kimmo Jukarainen
2008-10-08 1:17 ` David Brownell
2008-10-08 8:32 ` Koen Kooi
2009-10-21 15:43 ` [PATCH] omapfb: Wrong test on unsigned? Koen Kooi
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=200810071232.27362.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=ajay.gupta@ti.com \
--cc=k.kooi@student.utwente.nl \
--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