All of lore.kernel.org
 help / color / mirror / Atom feed
From: CityK <CityK@rogers.com>
To: Nicolas Will <nico@youplala.net>
Cc: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] TM6000 status
Date: Fri, 08 Feb 2008 09:23:58 -0500	[thread overview]
Message-ID: <47AC65FE.8080005@rogers.com> (raw)
In-Reply-To: <1202466494.6667.18.camel@acropora>

Nicolas Will wrote:
> Hello all,
>
> I've been talking with Michel Ludwig about the ADSTech Mini Dual TV
> (PTV-339) USB stick.
>
> It needs the xc2028/3028 module (in the main tree currently?) as well as
> the tm6000 module (and firmware).
>
> I see that these two hg branches exist:
>
> http://linuxtv.org/hg/~mchehab/tm6000/
> http://linuxtv.org/hg/~mchehab/tm6010/
>
> This wiki page exists, but look very outdated:
>
> http://linuxtv.org/v4lwiki/index.php/Trident_TM6000
>
> What's the status of all this ? What works?, What doesn't work? What is
> needed? Bugs, problems, show-stoppers? (no pressure, yet ;o), this is
> just for documentation's sake)
>
> I'm willing to clean-up/update the wiki when given information.
>
> Michel has my ADSTeck stick, and soon the remote as well, with him.
>
> Nico/camelreef

Hi Nico,

Mauro will definitely best know the answers to the status questions. I 
will only note that if your ADS device is similar to Mauro's 10moons 
device (which is also TM6000 & XC based) then you might require an older 
firmware for the XC tuner --- see Mauro's comment about it as 
encapsulated here:

http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028#About_the_Xceive_firmware


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

      reply	other threads:[~2008-02-08 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 10:28 [linux-dvb] TM6000 status Nicolas Will
2008-02-08 14:23 ` CityK [this message]

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=47AC65FE.8080005@rogers.com \
    --to=cityk@rogers.com \
    --cc=linux-dvb@linuxtv.org \
    --cc=nico@youplala.net \
    /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.