[linux-dvb] AverTV Hybrid Volar HX

[Manu Abraham]

Steven Toth wrote:
> Manu Abraham wrote:
>> Michael Krufky wrote:
>>> Manu Abraham wrote:
>>>> Zdenek Kabelac wrote:
>>>>  
>>>>> 2007/12/31, Michael Krufky <mkrufky at linuxtv.org>:
>>>>>    
>>>>>> Zdenek Kabelac wrote:
>>>>>>      
>>>>>>> Hello
>>>>>>>
>>>>>>> I should start a new thread about this USB2.0 device.
>>>>>>>
>>>>>>> I'll repeat which chips I could find in the USB device -
>>>>>>> SAA7136E,CY7C68013A,TDA18271HDC1
>>>>>>>
>>>>>>>         
>>>>>> You should base your work off the master branch.  The tda18271
>>>>>> driver in that tree should work well enough for you.  I don't know
>>>>>> anything about the IF within the saa7136 -- I would guess it is
>>>>>> something like a tda8290 or tda8295, which may need some work for
>>>>>> analog support.  For digital tv, you can attach the tda18271 the
>>>>>> same way as is done in cx23885-dvb for the hvr1800, with alt_tuner=1.
>>>>>>
>>>>>> You'll have some work to do to get the saa7136 analog video
>>>>>> decoder working as well... I've heard it may be compatible with
>>>>>> the saa7134 code, but that driver currently expects to be used as
>>>>>> a PCI bridge.
>>>>>>
>>>>>> Given the CY7C68013A, you probably don't want to touch any of the
>>>>>> dib0700 code, although we still don't know what digital demod /
>>>>>> channel decoder is used in your device.  Are there any other chips
>>>>>> inside?
>>>>>>       
>>>>> Yeah - It's been just a trial if it will do something with my device.
>>>>>     
>>>> This device might be supported soon. Other than that, I guess the
>>>> TDA18271 driver doesn't support DVB-T as of now.
>>>>
>>>>   
>>> Actually, I have heard reports from some people that they have gotten
>>> the tda18271 to work for DVB-T in their tests.  I haven't been able to
>>> successfully test that yet myself, but I welcome patches if there are
>>> any problems with the driver.
>>>
>>
>> Some of the vendors (more than one) wrote to me that the TDA18271
>> driver doesn't work. That was the basis of my statement.
>> (maybe it works with some hauppauge product, don't know)
> 
> They should write to the list and contribute, or release facts (not
> conjecture) through a third party.
> 
> It would be good to know what devices it isn't working with, and which
> potentially it does. This would help the community refine the driver.
> 
> "Anything else is whining" ... as someone once said to me.

On one of the mails, i was cc'd on a mail to one of the folks at Hauppauge.
(the author of that module)

Funny i found that, another vendor has to write to hauppauge for their drivers.

Manu