public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Will <nico@youplala.net>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Nova T-500 detection problem
Date: Tue, 11 Mar 2008 17:20:41 +0000	[thread overview]
Message-ID: <1205256041.7463.34.camel@acropora> (raw)
In-Reply-To: <004601c8839a$365ac620$4101a8c0@ians>


On Tue, 2008-03-11 at 17:06 +0000, Ian Liverton wrote:
> Hi,
> 
>  
> 
> I recently purchased two Nova T-500 (as far as I can tell it’s not one
> of the diversity range) cards one is the 99101 LF rev D8B5 and one is
> the 99102 LF rev C1B5.  The 99101 LF is detected, the other is not.
> The only difference I can see is the postfix of the Dib 0700 chips.
> The working one is the Dib0700C-XCXXa-G and the other is
> Dib0700-1211b-G.  With only the undetected card in, there is no
> mention of the dib0700 in dmesg and lspci shows:
> 
>  
> 
> 02:05.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 61)
> 
> 02:05.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 61)
> 
> 02:05.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
> 
>  
> 
> Which I presume is the VT6212L on the cards.
> 
>  
> 
> Is there something different I need to do for the second card or is it
> just not supported? Since I can get them both to work with the
> supplied Hauppauge software under Windows I am assuming it is not a
> faulty card.

What is lsusb saying ?

nico


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

  reply	other threads:[~2008-03-11 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 17:06 [linux-dvb] Nova T-500 detection problem Ian Liverton
2008-03-11 17:20 ` Nicolas Will [this message]
     [not found]   ` <005101c8839e$797bb140$4101a8c0@ians>
2008-03-11 19:11     ` Nicolas Will
  -- strict thread matches above, loose matches on Subject: below --
2008-03-11 23:30 Ian Liverton

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=1205256041.7463.34.camel@acropora \
    --to=nico@youplala.net \
    --cc=linux-dvb@linuxtv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox