public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: "Antti Palosaari" <crope@iki.fi>,
	"Sascha Wüstemann" <sascha@killerhippy.de>,
	linux-media@vger.kernel.org,
	"Thomas Holzeisen" <thomas@holzeisen.de>,
	stybla@turnovfree.net
Subject: Re: RTL2831U driver updates
Date: Tue, 21 Jun 2011 12:00:59 +0200	[thread overview]
Message-ID: <4E006BDB.8060000@hoogenraad.net> (raw)
In-Reply-To: <1308649292.3635.2.camel@maxim-laptop>

Can I put this somewhere in the git archive at the linuxtv site, so that 
we can share and have version control ?

Maxim Levitsky wrote:
> On Tue, 2011-06-21 at 01:22 +0300, 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...
>>
>
> Fine!
>
> In about month, after exams, I hope I will work on this to finish at
> least RTL2832/FC0012.
>
> For reference, this is the code I did so far.
>
>
> Best regards,
> Maxim Levitsky


-- 
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht

  reply	other threads:[~2011-06-21 10:01 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
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 [this message]
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=4E006BDB.8060000@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