From: Jin Kazama <jin.ml@skynet.fr>
To: linux-media@vger.kernel.org
Subject: af9015/tda18218: Multiples (separates) usb devices errors/conflicts
Date: Fri, 23 Sep 2011 23:06:34 +0200 [thread overview]
Message-ID: <4E7CF4DA.5020607@skynet.fr> (raw)
In-Reply-To: <S1752295Ab1IWUja/20110923203930Z+74@vger.kernel.org>
Hello,
I've been testing af9015/tda18218 based usb DVB-T tuners on a 2.6.39.4
kernel with the latest v4l drivers avaiable (from git).
When I'm using a single USB module, (listed as /dev/dvb/adapter0),
everything works fine.
When I'm plugging another module, at first it looks like everything's
ok (/dev/dvb/adapter1) and if I try to use this module while the
adapter0 is not been used, it works - but if try to use both modules at
the same time, I get garbage output on both cards (error: warning:
discontinuity for PID... with dvblast on both cards.
Does anyone have any idea on how to fix this problem?
next parent reply other threads:[~2011-09-23 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1752295Ab1IWUja/20110923203930Z+74@vger.kernel.org>
2011-09-23 21:06 ` Jin Kazama [this message]
2011-09-23 22:06 ` af9015/tda18218: Multiples (separates) usb devices errors/conflicts Antti Palosaari
2011-09-24 18:47 ` Jin Kazama
2011-09-25 17:30 ` Josu Lazkano
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=4E7CF4DA.5020607@skynet.fr \
--to=jin.ml@skynet.fr \
--cc=linux-media@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