From: Antti Palosaari <crope@iki.fi>
To: Chris Moore <moore@free.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: [linux-dvb] Looking for original source of an old DVB tree
Date: Sun, 24 Jan 2010 14:19:11 +0200 [thread overview]
Message-ID: <4B5C3ABF.4000807@iki.fi> (raw)
In-Reply-To: <4B5BFFE3.30003@free.fr>
On 01/24/2010 10:08 AM, Chris Moore wrote:
> Hello,
>
> Short version:
> I am looking for the original source code of a Linux DVB tree containing
> in particular
> drivers/media/dvb/dibusb/microtune_mt2060.c
> and the directory
> drivers/media/dvb/dibusb/mt2060_api
>
> Googling for microtune_mt2060.c and mt2060_api is no help.
> Could anyone kindly point me in the right direction, please?
It is mt2060.c, mt2060_priv.h (IIRC) and mt2060.h.
> Longer version:
> I am trying to get my USB DVB-T stick running on my Xtreamer.
> Xtreamer uses an old 2.6.12.6 kernel heavily modified by Realtek and
> possibly also modified by MIPS.
> I have the source code but it would be a tremendous effort to change to
> a recent kernel.
> The DVB subtree seems to have been dirtily hacked by Realtek to support
> their frontends.
> In the process they seem to have lost support for other frontends.
> I have been trying to find the source code for the original version.
> I have found nothing resembling it in kernel.org, linux-mips.org and
> linuxtv.org.
I am not sure what kind of device Xtreamer is, but try this:
http://linuxtv.org/hg/~anttip/rtl2831u/
It is for Realtek RTL2831U + MT2060 based USB sticks.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2010-01-24 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 8:08 [linux-dvb] Looking for original source of an old DVB tree Chris Moore
2010-01-24 12:19 ` Antti Palosaari [this message]
2010-01-26 6:19 ` Chris Moore
-- strict thread matches above, loose matches on Subject: below --
2010-01-24 8:00 Chris Moore
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=4B5C3ABF.4000807@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=moore@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.