All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter D." <peter_s_d@fastmail.com.au>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] auto detection of Flytv duo/hybrid and pci/cardbus confusion
Date: Sun, 17 Feb 2008 14:28:10 +1100	[thread overview]
Message-ID: <200802171428.10859.peter_s_d@fastmail.com.au> (raw)

Hi, 

I've finally gotten around to reading the code and trying to get my 
PCI MSI TV@nywhere A/D card auto detected. 

First clarification, duo versus hybrid.  
Are "duo" cards equipped with two independent tuners that can both be 
used at the same time?  
Are "hybrid" cards necessarily equipped with digital and analogue tuners?  
Can a two tuner card be both a duo and a hybrid, if one tuner is digital 
the other is analogue and they can both be used at the same time?  

Second clarification, PCI versus cardbus.  
They don't look anything like each other, but can they be logically 
interchangeable?  If the code for a cardbus tuner happens to work for 
a PCI tuner is there anything wrong with referring to the PCI tuner 
as a cardbus device?  

Looking at <http://www.linuxtv.org/wiki/index.php/DVB-T_PCMCIA_Cards> 
there does not appear to be any such thing as a 
SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS, despite the entry (number 94) 
in saa7134.h.  Looking at 
<http://www.linuxtv.org/wiki/index.php/DVB-T_PCI_Cards#LifeView> 
there is a PCI version - but there is no PCI version in saa7134.h.  

Should 
"SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS" be changed to 
"SAA7134_BOARD_FLYDVBT_HYBRID"?

It appears that both PCI and cardbus versions of the Flytv duo exist 
and are listed in saa7134.h - despite slightly inconsistent punctuation; 
SAA7134_BOARD_FLYDVBTDUO versus 
SAA7134_BOARD_FLYDVBT_DUO_CARDBUS.  

Should 
"SAA7134_BOARD_FLYDVBTDUO" be changed to 
"SAA7134_BOARD_FLYDVBT_DUO"?

I have an MSI TV@nywhere A/D PCI card that works with the option card=94

There appears to not be an entry in struct pci_device_id saa7134_pci_tbl[] 
in saa7134-cards.c for my card.  There is a reference to a 
"TV@nywhere DUO" which I guess is a valid entry for a different card.  

Is the entry; 

          {
                .vendor       = PCI_VENDOR_ID_PHILIPS,
                .device       = PCI_DEVICE_ID_PHILIPS_SAA7133,
                .subvendor    = 0x4e42,
                .subdevice    = 0x3502,
                .driver_data  = SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS
        },

supposed to be;

           {
                .vendor       = PCI_VENDOR_ID_PHILIPS,
                .device       = PCI_DEVICE_ID_PHILIPS_SAA7133,
                .subvendor    = 0x4E42,         /* MSI */
                .subdevice    = 0x3306,         /* TV@nywhere Hybrid A/D */
                driver_data  = SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS,
        },

with the subdevice changed, or possibly;

           {
                .vendor       = PCI_VENDOR_ID_PHILIPS,
                .device       = PCI_DEVICE_ID_PHILIPS_SAA7133,
                .subvendor    = 0x4E42,         /* MSI */
                .subdevice    = 0x3306,         /* TV@nywhere Hybrid A/D */
                driver_data  = SAA7134_BOARD_FLYDVBT_HYBRID,
        },

with the subdevice and driver_data changed, or should there be an extra 
entry in the list?  

Thank you.  


-- 
sig goes here...
Peter D.

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

             reply	other threads:[~2008-02-17  3:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17  3:28 Peter D. [this message]
2008-02-17 20:19 ` [linux-dvb] auto detection of Flytv duo/hybrid and pci/cardbus confusion hermann pitton
2008-02-17 20:53   ` Peter Missel
2008-02-19 23:25     ` hermann pitton
2008-02-22 13:11       ` Peter D.
2008-02-23 20:05         ` hermann pitton
2008-02-22 13:03   ` Peter D.
  -- strict thread matches above, loose matches on Subject: below --
2008-02-20 22:41 Werner Braun
2008-02-21 22:49 ` hermann pitton
2008-02-22 19:57   ` Peter Missel

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=200802171428.10859.peter_s_d@fastmail.com.au \
    --to=peter_s_d@fastmail.com.au \
    --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 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.