Re: rtl2832u support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I haven't seen any data sheets. At the other hand, Antti was able to create a separated (tuner vs demod) driver, except for IR.

http://linuxtv.org/hg/~anttip/rtl2831u/

http://linuxtv.org/hg/~anttip/qt1010/

I haven't seen a data sheet, but I doubt if it would be of more use than using this example code. My mail contacts (latest in may 2008) focused on getting the code to work and on signing off the code.

I'll give my mail contact a try, especially if you have questions that cannot be found in the current code base.

Maxim Levitsky wrote:
On Mon, 2010-12-06 at 16:45 +0100, Jan Hoogenraad wrote:
Could the tree from

http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2

which is really just an older version of the same code, go into staging
than as well ?
Yes, but the problem is that due to shaddy license status of the
'windows' driver, I am afraid to look seriously at it.
Up till now, I only experimented with IR code.

Jan, since you have contacts with Realtek, maybe it would be possible to
get datasheet for their hardware?

And the above code is guaraneed not to work on my card because even
their 'windows' driver v1.4 doesn't work here.
Only 2.0 driver works.

And you said that you couldn't seperate demod from bridge?
Is that nessesary?
I have seen few drivers that don't separate it in v4l source.

Tuners are of course another story.

Best regards,
	Maxim Levitsky



For that one, I have the signoff by RealTek already.

Mauro Carvalho Chehab wrote:
Em 20-11-2010 20:37, Maxim Levitsky escreveu:

Do we have a common agreement that this driver can go to staging as-is?

If yes, I have patch ready, just need to know where to send it (It is around 1 MB).

Yes, if people is interested on later fixing the issues. As Antti said
he already broke the driver into more consistent parts, maybe his tree
may be an start.


I would like to volunteer to clean up the driver for eventual merge.
At least I can start right away with low handing fruit.

Ok, Seems fine for me.

I have took the driver from

http://www.turnovfree.net/~stybla/linux/v4l-dvb/lv5tdlx/20101102_RTL2832_2836_2840_LINUX+RC-Dongle.rar


And it looks very recent, so that means that Realtek actually continues
to develop it.

The better would be to try to sync with Realtek to be sure that they'll
continue to develop the upstream driver, after having it merged. Otherwise,
someone will need to do the manual sync, and this can be very painful.

Greg KH, maybe you know how to contact Realteck to figure out the best
strategy in handling this code.

Meanwhile, lets put that into staging.
(The above driver doesn't compile due to changes in RC code, but it can
be removed (that what I did for now) or ported to new rc-core which what
I will do very soon).

Just send the patches. The better is to submit them via linux-media, and say, at
a TODO file, that patches for it should be submitted to linux-media@xxxxxxxxxxxxxxxx
Something similar to drivers/staging/tm6000/TODO.

Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html







--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux