From: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
To: Antti Palosaari <crope@iki.fi>, stybla@turnovfree.net
Cc: "Sascha Wüstemann" <sascha@killerhippy.de>,
linux-media@vger.kernel.org,
"Thomas Holzeisen" <thomas@holzeisen.de>,
"Maxim Levitsky" <maximlevitsky@gmail.com>
Subject: Re: RTL2831U driver updates
Date: Tue, 21 Jun 2011 07:40:13 +0200 [thread overview]
Message-ID: <4E002EBD.6050800@hoogenraad.net> (raw)
In-Reply-To: <4DFFC82B.10402@iki.fi>
Antti:
You are great !
So as far as I am concerned, it would be great if one of the others
could use up your work on the USB bridge, and add the IR remote
interface, based on the LIRC framework.
It actually should yield little code, and mainly requires a)
understanding of LIRC and b) comparing code tables to that the in-kernel
code tables can be re-used.
Note that Zdenek Styblik seems to have received updates from Realtek
THIS month
http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start
He has posted a Ver 2.2.0 of the driver at:
http://www.turnovfree.net/~stybla/linux/v4l-dvb/lv5tdlx/
It supports the RTL2832U and RTL2836 and way more tuners (MT2266 FC2580
TUA9001 and MXL5007T E4000 FC0012 tda18272 fc0013)
However, the code is not split up.
Antti Palosaari wrote:
> It is Maxim who have been hacking with RTL2832/RTL2832U lately. But I
> think he have given up since no noise anymore.
>
> I have taken now it again up to my desk and have been hacking two days
> now. Currently I am working with RTL2830 demod driver, I started it from
> scratch. Take sniffs, make scripts to generate code from USB traffic,
> copy pasted that to driver skeleton and now I have picture. Just
> implement all one-by-one until ready :-) I think I will implement it as
> minimum possible, no any signal statistic counters - lets add those
> later if someone wants to do that.
>
> USB-bridge part is rather OK as I did earlier and it is working with
> RTL2831U and RTL2832U at least. No remote support yet.
>
> I hope someone else would make missing driver for RTL2832U demod still...
>
>
> Antti
>
>
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
next prev parent reply other threads:[~2011-06-21 5:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 8:19 RTL2831U wont compile against 2.6.38 Thomas Holzeisen
2011-06-16 11:34 ` Sascha Wüstemann
2011-06-16 21:36 ` RTL2831U driver updates Jan Hoogenraad
2011-06-17 8:30 ` Sascha Wüstemann
2011-06-17 14:17 ` Thomas Holzeisen
2011-06-20 16:10 ` poma
2011-06-20 22:22 ` Antti Palosaari
2011-06-21 5:40 ` Jan Hoogenraad [this message]
2011-06-21 8:03 ` Steffen Barszus
2011-06-22 5:34 ` Jan Hoogenraad
2011-06-22 6:13 ` Steffen Barszus
2011-06-22 11:11 ` Antti Palosaari
2011-06-21 9:41 ` Maxim Levitsky
2011-06-21 10:00 ` Jan Hoogenraad
2011-07-09 3:27 ` Antti Palosaari
2011-08-04 23:43 ` Antti Palosaari
2011-08-06 3:56 ` Alistair Buxton
2011-08-06 5:13 ` Alistair Buxton
2011-08-08 19:50 ` Antti Palosaari
2011-08-09 13:22 ` Alistair Buxton
2011-10-21 20:41 ` Alistair Buxton
2011-06-17 10:39 ` RTL2831U wont compile against 2.6.38 Thomas Holzeisen
2011-06-17 19:28 ` Sascha Wüstemann
2011-06-18 12:44 ` Thomas Holzeisen
2011-06-18 12:56 ` Antti Palosaari
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=4E002EBD.6050800@hoogenraad.net \
--to=jan-conceptronic@hoogenraad.net \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=sascha@killerhippy.de \
--cc=stybla@turnovfree.net \
--cc=thomas@holzeisen.de \
/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