From: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
To: "Sascha Wüstemann" <sascha@killerhippy.de>
Cc: linux-media@vger.kernel.org,
Thomas Holzeisen <thomas@holzeisen.de>,
stybla@turnovfree.net, Maxim Levitsky <maximlevitsky@gmail.com>,
Antti Palosaari <crope@iki.fi>
Subject: RTL2831U driver updates
Date: Thu, 16 Jun 2011 23:36:08 +0200 [thread overview]
Message-ID: <4DFA7748.6000704@hoogenraad.net> (raw)
In-Reply-To: <4DF9EA62.2040008@killerhippy.de>
Sascha: Thanks for the links
Would you know how to contact poma ?
http://www.spinics.net/lists/linux-media/msg24890.html
I will be getting more info from Realtek soon.
I did not realize that they were putting out updated drivers.
Once the status becomes more clear, I'll update
http://www.linuxtv.org/wiki/index.php/Realtek_RTL2831U
Sascha Wüstemann wrote:
> Thomas Holzeisen wrote:
>> Hi there,
>>
>> I tried to get an RTL2831U dvb-t usb-stick running with a more recent kernel (2.6.38) and failed.
>>
>> The hg respository ~jhoogenraad/rtl2831-r2 aborts on countless drivers, the rc coding seem have to
>> changed a lot since it got touched the last time.
>>
>> The hg respository ~anttip/rtl2831u wont compile as well, since its even older.
>>
>> The recent git respositories for media_tree and anttip dont contain drivers for the rtl2831u.
>>
>> Has this device been abandoned, or is anyone working on it?
>>
>> greetings,
>> Thomas
>
> There are still people working on it and there is new sources, e.g. look at
> http://www.spinics.net/lists/linux-media/msg24890.html
> at the very bottom. Worked like a charm at my system with kernel 2.6.39.
>
> I think, there will be announcements later at
> http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start
>
> Greetings from Braunschweig, Germany.
> Sascha
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
next prev parent reply other threads:[~2011-06-16 21:36 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 ` Jan Hoogenraad [this message]
2011-06-17 8:30 ` RTL2831U driver updates 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
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=4DFA7748.6000704@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