All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Moore <moore@free.fr>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb]  Looking for original source of an old DVB tree
Date: Sun, 24 Jan 2010 09:00:20 +0100	[thread overview]
Message-ID: <4B5BFE14.30501@free.fr> (raw)

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?

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 fould nothing resembling it in kernel.org, linux-mips.org and 
linuxtv.org.

TIA.

Cheers,
Chris



_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

             reply	other threads:[~2010-01-24  8:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24  8:00 Chris Moore [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2010-01-26  6:19   ` 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=4B5BFE14.30501@free.fr \
    --to=moore@free.fr \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@vger.kernel.org \
    /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.