From: David Brownell <david-b@pacbell.net>
To: Kimmo Jukarainen <kimju-omap@inside.org>
Cc: Koen Kooi <k.kooi@student.utwente.nl>,
"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>,
Ajay Kumar Gupta <ajay.gupta@ti.com>,
linux-dvb@linuxtv.org
Subject: Re: DVB-T problems with MUSB
Date: Tue, 7 Oct 2008 18:17:00 -0700 [thread overview]
Message-ID: <200810071817.01014.david-b@pacbell.net> (raw)
In-Reply-To: <20081007231032.GB669@inside.org>
On Tuesday 07 October 2008, Kimmo Jukarainen wrote:
> On Tue, Oct 07, 2008 at 09:03:42PM +0200, Koen Kooi wrote:
> > Is this a problem with MUSB, omap dma or the dvb stack?
>
> I'd say dvb stack. This small patch fixed my dvb-t stick with
> a omap2 board:
>
> http://www.linuxtv.org/pipermail/linux-dvb/2008-January/023040.html
Looks like a fair fix, at a quick look.
I'm kind of surprised that bug has been known for what
looks like about a year now, with a trivial fix that
hasn't yet been merged through the DVB tree ...
> --- linux-2.6.20.4.orig/drivers/media/dvb/dvb-usb/usb-urb.c 2007-03-23 20:52:51.000000000 +0100
> +++ linux-2.6.20.4/drivers/media/dvb/dvb-usb/usb-urb.c 2007-10-25 12:19:50.000000000 +0200
> @@ -152,7 +152,8 @@
> stream->props.u.bulk.buffersize,
> usb_urb_complete, stream);
>
> - stream->urb_list[i]->transfer_flags = 0;
> + stream->urb_list[i]->transfer_flags = URB_NO_TRANSFER_DMA_MAP;
> + stream->urb_list[i]->transfer_dma = stream->dma_addr[i];
> stream->urbs_initialized++;
> }
> return 0;
next prev parent reply other threads:[~2008-10-08 1:17 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
2008-10-07 23:10 ` Kimmo Jukarainen
2008-10-08 1:17 ` David Brownell [this message]
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=200810071817.01014.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=ajay.gupta@ti.com \
--cc=k.kooi@student.utwente.nl \
--cc=kimju-omap@inside.org \
--cc=linux-dvb@linuxtv.org \
--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