From: Jarod Wilson <jarod@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: acano@fastmail.fm, linux-media@vger.kernel.org
Subject: Re: [PATCH] em28xx: kworld 340u
Date: Mon, 20 Jul 2009 09:53:20 -0400 [thread overview]
Message-ID: <200907200953.21506.jarod@redhat.com> (raw)
In-Reply-To: <829197380907181513mbd8dc5ag7facc128a2b2a951@mail.gmail.com>
On Saturday 18 July 2009 18:13:30 Devin Heitmueller wrote:
> On Sat, Jul 18, 2009 at 5:34 PM, <acano@fastmail.fm> wrote:
> > support for kworld 340u. 8vsb and qam256 work, qam64 untested.
>
> Hello Acano,
>
> You should talk to Jarod Wilson about this. He did a bunch of work to
> get the 340u working over the last couple of months, and you two could
> probably collaborate on a unified solution.
Hrm. I really probably should have sent something to the list that
mentioned I'd done this, to prevent duplication... Oops.
> There were also some
> problems related to the fact that the device can have either the
> tda18271c1 or the c2 (both have the same USB id), which would have to
> be accommodated in the final solution.
But with luck, some combination of dvb_gpio changes will get them
both behaving... But yeah, this is the main thing currently holding
back what I've got being merged.
> The patch itself also needs alot of cleanup and doesn't meet the
> coding standards. It would need considerable cleanup before it could
> be taken upstream.
Just took a quick look. I don't think there's anything in there I
haven't already got covered, and covered in a way that should already
be up to kernel coding standards. The other major difference with my
approach, is that rather than use the lgdt3304 driver to handle the
demod, I'm using a modified lgdt3305 driver with 3304 support added,
as its a FAR more complete driver, and the two are incredibly similar.
WIP patches from a few weeks back:
http://jwilson.fedorapeople.org/misc/lgdt3305-add-lgdt3304-support-20090623.patch
http://jwilson.fedorapeople.org/misc/em28xx-add-kworld-340u-using-lgdt3305-20090623.patch
But yeah, we still need to work out properly supporting both the C1 and
C2 variant of the stick -- my C1 works perfectly, Mike Krufky's C2 does
not... But it could be as simple as fixing up the dvb_gpio settings,
just need to get around to figuring out what the bare minimum are that
need to be reset on the C1, then see if that works better for the C2...
--
Jarod Wilson
jarod@redhat.com
prev parent reply other threads:[~2009-07-20 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 21:34 [PATCH] em28xx: kworld 340u acano
2009-07-18 22:13 ` Devin Heitmueller
2009-07-20 13:53 ` Jarod Wilson [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=200907200953.21506.jarod@redhat.com \
--to=jarod@redhat.com \
--cc=acano@fastmail.fm \
--cc=dheitmueller@kernellabs.com \
--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