[linux-dvb] AVerTV Hybrid Volar HX A827 - device ID not supported - no driver

2008-02-28 Thread Jelle de Jong

Fellow dvb'ers,

My friend bought a AVerTV Hybrid Volar HX A827 for is linux pc and hoped 
it would work. After he spent a day to get it working he asked my help.


I tried a hole list of things, and went through the code. I tried to get 
it working with the a800 driver and added some device ID's but i cant 
make it to work. There is no firmware or datasheets for the device.


Can the device be added to the list of not working devices?
Will somebody else be able to make a good driver for the device?

I added a lot of good info in the attachment.

Kind regards,

Jelle de Jong
dib3000-common.ko
dib3000mc.ko
dvb-usb.ko
dvb-usb-dibusb-common.ko
dvb-usb-a800.ko

sudo depmod -a

/lib/firmware/2.6.22-14-generic/dvb-usb-avertv-a800-02.fw

cp /lib/firmware/2.6.22-14-generic/dvb-usb-avertv-a800-02.fw 
/lib/firmware/dvb-usb-avertv-a800-02.fw
sudo cp --verbose /lib/firmware/2.6.22-14-generic/dvb-usb-avertv-a800-02.fw 
/lib/firmware/dvb-usb-avertv-a800-02.fw


sudo insmod 
/lib/modules/2.6.22-14-generic/kernel/drivers/media/dvb/frontends/dib3000mb.ko
sudo insmod 
/lib/modules/2.6.22-14-generic/kernel/drivers/media/dvb/frontends/dib3000mc.ko
sudo insmod 
/lib/modules/2.6.22-14-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb.ko
sudo insmod 
/lib/modules/2.6.22-14-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dibusb-common.ko
sudo insmod 
/lib/modules/2.6.22-14-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-a800.ko

sudo modprobe i2c-core
sudo modprobe dvb-core
sudo modprobe dib3000mc
sudo modprobe dvb-usb
sudo modprobe dvb-usb-dibusb-common
sudo modprobe dvb-usb-a800
sudo modprobe dib3000mb
sudo modprobe dibx000_common
sudo modprobe dib7000p
sudo modprobe dvb-usb-firmware

sudo rmmod -f i2c-core
sudo rmmod -f dvb-core
sudo rmmod -f dib3000mc
sudo rmmod -f dvb-usb
sudo rmmod -f dvb-usb-dibusb-common
sudo rmmod -f dvb-usb-a800
sudo rmmod -f dib3000mb
sudo rmmod -f dibx000_common
sudo rmmod -f dib7000p
sudo rmmod -f dvb-usb-firmware

sudo insmod /home/jelle/v4l-dvb/v4l/dvb-core.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dvb-pll.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dvb-usb-a800.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dvb-usb-dibusb-common.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dvb-usb-dibusb-mb.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dvb-usb-dibusb-mc.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dib3000mb.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dib3000mc.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dib7000p.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dib0070.ko
sudo insmod /home/jelle/v4l-dvb/v4l/dibx000_common.ko

sudo modprobe dvb-core
sudo modprobe dvb-pll
sudo modprobe dvb-usb-a800
sudo modprobe dvb-usb-dibusb-common
sudo modprobe dvb-usb-dibusb-mb
sudo modprobe dvb-usb-dibusb-mc
sudo modprobe dib3000mb
sudo modprobe dib3000mc
sudo modprobe dib7000p
sudo modprobe dib0070
sudo modprobe dibx000_common

http://www.mythtv.org/wiki/index.php/AVerTV_DVB-T_Volar

sudo apt-get install dvb-utils mercurial build-essential linux-headers-$(uname 
-r)


hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
make
sudo make install
sudo depmod -a

sudo find . '*' -type f -exec sudo grep -H -n 0x07ca '{}' \;
sudo find . '*' -type f -exec sudo grep -H -n 0xa827 '{}' \;

sudo find . '*' -type f -exec sudo grep -H -n 0xa800 '{}' \;
sudo find . '*' -type f -exec sudo grep -H -n AVERMEDIA '{}' \;

cd $HOME
vim ./v4l-dvb/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
vim ./v4l-dvb/linux/drivers/media/dvb/dvb-usb/a800.c

sudo modinfo /home/jelle/v4l-dvb/v4l/dvb-usb-a800.ko
sudo modinfo dvb-usb-a800

AVerTV Hybrid Volar HX A827
http://www.avermedia.com/AVerTV/Product/ProductDetail.aspx?Id=293

Bus 002 Device 003: ID 07ca:a827 AVerMedia Technologies, Inc.
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x07ca AVerMedia Technologies, Inc.
  idProduct  0xa827
  bcdDevice1.03
  iManufacturer   1 AVerMedia
  iProduct2 AVerTV
  iSerial 3 300367002364
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  219
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  1
  bInterfaceProtocol  1
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer Type

Re: [linux-dvb] AVerTV Hybrid Volar HX A827 - device ID not supported - no driver

2008-02-28 Thread Zdenek Kabelac
2008/2/28, Jelle de Jong [EMAIL PROTECTED]:
 Fellow dvb'ers,

  My friend bought a AVerTV Hybrid Volar HX A827 for is linux pc and hoped
  it would work. After he spent a day to get it working he asked my help.

  I tried a hole list of things, and went through the code. I tried to get
  it working with the a800 driver and added some device ID's but i cant
  make it to work. There is no firmware or datasheets for the device.

  Can the device be added to the list of not working devices?
  Will somebody else be able to make a good driver for the device?


Manu Abraham is already working on Afatech chip support
But it's probably hard task as it takes quite some time... :(
(Find out my post from December)

Zdenek

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2008-01-02 Thread Zdenek Kabelac
2008/1/1, Manu Abraham [EMAIL PROTECTED]:
 Zdenek Kabelac wrote:
  There is a OSS driver upcoming, supported by the chip manufacturer 
  themselves
  (AFA Technologies.) I have been a bit involved in that process.
 
  Yep - looks nice - and do you have any idea about the release date?

 I don't have a date, but the chip manufacturer as well as everybody involved 
 is under

I mean - is it question for few weeks or couple months?

  Maybe I could help with testing and reporting bugs ?
  As I can see it would be probably useless to try hacking any code for
  this device myself.

 The current state of testing is that, one needs to understand the chip 
 internals and
 the testing happens in the Labs alone (lot of undocumented things in there,
 documentation being really crap), with some basic tests we have going on. As 
 soon

Well I wouldn't be afraid even from this kind of testing - I think I
have enough skills for this.

If you have some pieces of chip docs you could pass to me...

 I have redone the driver a few times by now, trying to handle the different 
 aspects.
 There have been some discussions on this ML also, on the same a while back.

Actually I've done some search through the list and I've found this:

It looks like there are actually 3 different drivers for Afatech chip:
(and look quite different)

1.) on from you: http://jusst.de/hg(last commit before 7 weeks)
2.) another from Antti Palosaari  (crope)
3.) by afatech ??  http://af.zsolttech.com/ by Rick Huang

Which leads me to the question - is it actually coordinated somehow?

What is the plan - which driver will go to kernel ??
(IMHO the current situation looks a bit weird at this moment)

And when you are say you are working on some driver - by this you mean
only af901x ? (So I could try those other two if they will not work by
some miracle)

Or when you release your code my AverTV HX will work out-of-the-box?
(with the support for SAA and TDA  chips)

Regards

Zdenek

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2008-01-02 Thread Manu Abraham
Zdenek Kabelac wrote:
 2008/1/1, Manu Abraham [EMAIL PROTECTED]:
 Zdenek Kabelac wrote:
 There is a OSS driver upcoming, supported by the chip manufacturer 
 themselves
 (AFA Technologies.) I have been a bit involved in that process.
 Yep - looks nice - and do you have any idea about the release date?
 I don't have a date, but the chip manufacturer as well as everybody involved 
 is under
 
 I mean - is it question for few weeks or couple months?

I guess it would be a few weeks. In fact working on a similar but different 
device as of now.

 
 Maybe I could help with testing and reporting bugs ?
 As I can see it would be probably useless to try hacking any code for
 this device myself.
 The current state of testing is that, one needs to understand the chip 
 internals and
 the testing happens in the Labs alone (lot of undocumented things in there,
 documentation being really crap), with some basic tests we have going on. As 
 soon
 
 Well I wouldn't be afraid even from this kind of testing - I think I
 have enough skills for this.
 
 If you have some pieces of chip docs you could pass to me...

I would suggest that you request AFA for docs. One needs to be under NDA or so. 
(Though the docs are quite confusing)

 
 I have redone the driver a few times by now, trying to handle the different 
 aspects.
 There have been some discussions on this ML also, on the same a while back.
 
 Actually I've done some search through the list and I've found this:
 
 It looks like there are actually 3 different drivers for Afatech chip:
 (and look quite different)
 
 1.) on from you: http://jusst.de/hg(last commit before 7 weeks)
 2.) another from Antti Palosaari  (crope)
 3.) by afatech ??  http://af.zsolttech.com/ by Rick Huang
 
 Which leads me to the question - is it actually coordinated somehow?
 
 What is the plan - which driver will go to kernel ??
 (IMHO the current situation looks a bit weird at this moment)

Nothing weird, the chip is a bit flexible, with that flexibility it brings in a 
lot of troubles.

1) a second attempt at getting it right (got many things right, but some went 
wrong. 
Works with just one device alone)

2) a RE driver for the AF9015 chip based, for a MASTER device based 
configuration.

3) an AF9015 driver which was done by AFA for one customer, who violated the 
NDA, 
which is almost the source for 2 but very much specifically written for one 
tuner in mind.
 
According to AFA Tech, None of these they would like to have in kernel, since 
they 
wouldn't be able to support newer configurations based on them.
 
 And when you are say you are working on some driver - by this you mean
 only af901x ? (So I could try those other two if they will not work by
 some miracle)

Neither 3 will work. Lot of differences, what's common is very small.
 
 Or when you release your code my AverTV HX will work out-of-the-box?

At least digital should work for you (when done), though there will be the need 
for a 
small stub additionally.


Regards,
Manu

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2008-01-01 Thread Manu Abraham
Zdenek Kabelac wrote:
 Hi Manu
 
 I'd like to hear it clearly - should I safe my time to play with this device?
 
 Do you mean by this answer that you know someone already writes the
 driver for AsusTV Hybrid Volar HX USB device ?
 
 (And driver will be opensource and usable with any kernel I need ?)
 
 What is the timeplan of this event ?
 
 Thanks for your answers.
 

There is a OSS driver upcoming, supported by the chip manufacturer themselves 
(AFA Technologies.) I have been a bit involved in that process. 

Currently it is tested on some few devices only and is not a generic driver as 
it is 
(due to the complexities involved in the various configurations of the device, 
Single USB, Dual USB, Platform mode, PCI/PCIe based devices. even SPI is 
supported 
on it for some tuners -- for a Consumer Electronics product that runs Windows 
CE). 
The upcoming driver is meant to be usable in all these configurations, and will 
be supported by them in the future as well, for newer designs. (Lot more devices
to appear, based on this chipset)

There have been some peripheral manufacturers who have been also involved in the
process such as Terratec, Azurewave, DigitalNow and Pinnacle, other than 
Avermedia.
There are some 5 unbranded Chinese manufacturers too.
(I had asked the chip manufacturer about your device, for which Avermedia has 2 
products based on the same, a USB based and a PCIe Dual demodulator based 
device.) 

The current state is that there are some tests going on in the AFA labs on the 
driver 
for the chip (currently, 2nd round) due to all the Hardware hacks on the chip 
to handle 
all these diverse configurations.

Will post details on the same, on this list as it arrives.

Regards,
Manu


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


Re: [linux-dvb] AverTV Hybrid Volar HX

2008-01-01 Thread Zdenek Kabelac
2008/1/1, Manu Abraham [EMAIL PROTECTED]:
 Zdenek Kabelac wrote:
  Hi Manu
 

 There is a OSS driver upcoming, supported by the chip manufacturer themselves
 (AFA Technologies.) I have been a bit involved in that process.

Yep - looks nice - and do you have any idea about the release date?


 The current state is that there are some tests going on in the AFA labs on 
 the driver
 for the chip (currently, 2nd round) due to all the Hardware hacks on the chip 
 to handle

Maybe I could help with testing and reporting bugs ?
As I can see it would be probably useless to try hacking any code for
this device myself.

Regards

Zdenek

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2008-01-01 Thread Manu Abraham
Zdenek Kabelac wrote:
 2008/1/1, Manu Abraham [EMAIL PROTECTED]:
 Zdenek Kabelac wrote:
 Hi Manu

 There is a OSS driver upcoming, supported by the chip manufacturer themselves
 (AFA Technologies.) I have been a bit involved in that process.
 
 Yep - looks nice - and do you have any idea about the release date?

I don't have a date, but the chip manufacturer as well as everybody involved is 
under 
pressure, due to the large usage of the chip by different peripheral 
manufacturers.
It has to come out soon, looking at the list of supported device configurations 
by now, 
nothing less than 33 configurations documented list as i have now, just PC 
based 
configurations alone, CE equipments excluded.

 The current state is that there are some tests going on in the AFA labs on 
 the driver
 for the chip (currently, 2nd round) due to all the Hardware hacks on the 
 chip to handle
 
 Maybe I could help with testing and reporting bugs ?
 As I can see it would be probably useless to try hacking any code for
 this device myself.

The current state of testing is that, one needs to understand the chip 
internals and 
the testing happens in the Labs alone (lot of undocumented things in there, 
documentation being really crap), with some basic tests we have going on. As 
soon 
as it get's past this stage, there is something for users to test.

I have redone the driver a few times by now, trying to handle the different 
aspects.
There have been some discussions on this ML also, on the same a while back.

Regards,
Manu

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2008-01-01 Thread hermann pitton
Am Dienstag, den 01.01.2008, 20:33 +0400 schrieb Manu Abraham:
 Zdenek Kabelac wrote:
  2008/1/1, Manu Abraham [EMAIL PROTECTED]:
  Zdenek Kabelac wrote:
  Hi Manu
 
  There is a OSS driver upcoming, supported by the chip manufacturer 
  themselves
  (AFA Technologies.) I have been a bit involved in that process.
  
  Yep - looks nice - and do you have any idea about the release date?
 
 I don't have a date, but the chip manufacturer as well as everybody involved 
 is under 
 pressure, due to the large usage of the chip by different peripheral 
 manufacturers.
 It has to come out soon, looking at the list of supported device 
 configurations by now, 
 nothing less than 33 configurations documented list as i have now, just PC 
 based 
 configurations alone, CE equipments excluded.
 
  The current state is that there are some tests going on in the AFA labs on 
  the driver
  for the chip (currently, 2nd round) due to all the Hardware hacks on the 
  chip to handle
  
  Maybe I could help with testing and reporting bugs ?
  As I can see it would be probably useless to try hacking any code for
  this device myself.
 
 The current state of testing is that, one needs to understand the chip 
 internals and 
 the testing happens in the Labs alone (lot of undocumented things in there, 
 documentation being really crap), with some basic tests we have going on. As 
 soon 
 as it get's past this stage, there is something for users to test.
 
 I have redone the driver a few times by now, trying to handle the different 
 aspects.
 There have been some discussions on this ML also, on the same a while back.
 
 Regards,
 Manu
 

Manu,

where do you have your mission from?

As far as I can see, _excactly Nobody_ asked you to do it.

If you have a GO for this by Linus and Andrew, and that I seriuously
doubt, I stay away for ever ...

Cheers,
Hermann





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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-31 Thread Steven Toth
Manu Abraham wrote:
 Michael Krufky wrote:
 Manu Abraham wrote:
 Zdenek Kabelac wrote:
   
 2007/12/31, Michael Krufky [EMAIL PROTECTED]:
 
 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.

- Steve

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-31 Thread Steven Toth
Michael Krufky wrote:
 Manu Abraham wrote:
 Zdenek Kabelac wrote:
   
 2007/12/31, Michael Krufky [EMAIL PROTECTED]:
 
 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.

Mike,

Is their something Hauppauge can do to help with this?

- Steve

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-31 Thread Manu Abraham
Steven Toth wrote:
 Manu Abraham wrote:
 Michael Krufky wrote:
 Manu Abraham wrote:
 Zdenek Kabelac wrote:
  
 2007/12/31, Michael Krufky [EMAIL PROTECTED]:

 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


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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-31 Thread Michael Krufky
Steven Toth wrote:
 Michael Krufky wrote:
 Manu Abraham wrote:
   
 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.
 
 Mike,
 
 Is their something Hauppauge can do to help with this?

No.

If there are no bug reports, then there are no bugs to be fixed. (do you like 
the satire?)

If someone REPORTS a bug, then we can look at the problem.

Let me re-phrase -- Hauppauge can help, if interested, by finding somebody to 
write a GPL'd driver for a DVB-T demod found on a board that also uses the 
tda18271 -- after that, I'll be able to test DVB-T.

Until now, AFAIK, the tda18271 module works in all analog modes, ATSC / QAM, 
and has only been tested for use with DVB-T (and DMB-T) in a closed circuit.

There are a few obvious places that need adjusting to improve the tuning 
quality -- I am working on improving the tuning algorithm and rf tracking 
filter calibration scheme.

If there is any bug anywhere preventing DVB-T from working, it would be related 
to the std bits / IF (all found in tda18271_set_params).  I believe that there 
may be some device-specific configuration that I've been thinking of moving 
into an attach-time parameter, but until I see a need for it ( bug reports ? ) 
I'll leave it as-is.

I have not spend much time with DVB-T support on this tuner, since I don't have 
any devices with all known supported hardware except for the new tuner.  If 
there were drivers available for newer demods that are usually found with this 
tuner on DVB-T boards, then maybe I'd have an easier time testing it.

Right now, I am working on adding support for the C2 revision of this device.  
I already have digital mode working, tested with QAM256 so far, and I have a 
rock-solid signal.  Analog works too, but it's really just limping for now.  I 
have not pushed up the c2 support yet -- my tda18271c2 tree is just a staging 
area, and still only supports the c1 tuner.

If the mystery vendor X has a C2 tuner, it _will_not_ work with the driver in 
my public repository.

I will not merge in C2 support until after I clean up my patches here in my 
local sandbox, unless anybody out there is specifically interested in testing 
it... If so, send me an email and I'll push up today's snapshot to a test 
repository.  Even still, I'd rather clean it up first -- should just take a few 
more hours of work.

Manu Abraham wrote:
 
 Some of the vendors (more than one) wrote to me that the TDA18271 driver 
 doesn't work. That was the basis of my statement.


Silly vendors.  Why write to _you_ about somebody else's work?

If they are interested in participating in the open source community, they 
should file their own bug reports, and be sure that they are received by the 
author of said driver.

-Mike Krufky

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-31 Thread Manu Abraham
Michael Krufky wrote:

 Manu Abraham wrote:
 Some of the vendors (more than one) wrote to me that the TDA18271 driver 
 doesn't work. That was the basis of my statement.
 
 
 Silly vendors.  Why write to _you_ about somebody else's work?


One of the vendors cc'd me, since they did ask you and had no response from you
They asked me to work on a driver from ground up or fix your driver, since you 
told
them that you had no time.

I hope some ghost didn't write the inlined mail.

Manu




Max-

I apologize -- I have been extremely busy these past few months I 
moved to a new apartment AND started a new job.

Anyway, back to business...  I requested that my current tda18271 driver 
be merged into the master development branch.  The current driver works 
for all analog video standards, and has support for atsc / qam / dvb-t 
...  although the digital tuning is so far untested.  I will be working 
on atsc / qam in the next few weeks, testing with hardware that I have here.

I'd also like to work on DVB-T, but I don't have a driver for the 
tda10048 -- have you worked on this?  I have devices here using tda10048 
and a dvb-t test feed... if you have a demod driver, it would help me to 
finish the dvb-t support in the tuner module.

Otherwise, I was thinking of working on such a tda10048 driver myself, 
although I probably won't have time to get started on that for a few 
months.  If you already have started on one, it would be quicker.

Again, I apologize for my slow response -- I promise to be better about 
this from now on  ;-) 

Regards,

Mike Krufky



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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-31 Thread Michael Krufky
Manu Abraham wrote:
 Michael Krufky wrote:
 
 Manu Abraham wrote:
 Some of the vendors (more than one) wrote to me that the TDA18271 driver 
 doesn't work. That was the basis of my statement.

 Silly vendors.  Why write to _you_ about somebody else's work?

 
 One of the vendors cc'd me, since they did ask you and had no response from 
 you
 They asked me to work on a driver from ground up or fix your driver, since 
 you told
 them that you had no time.
 
 I hope some ghost didn't write the inlined mail.

[quoted mail snipped]

Manu,

I'd appreciate it if you would NOT post private email threads to a public 
mailing list.

(haven't we gone down this road before?)

Max got the tda18271 driver working on his device -- a typo was identified that 
had prevented DVB-T / DMB-T tuning from working.

The fix has already been applied to the master repository:

# HG changeset patch
# User Michael Krufky mkrufky at linuxtv dot org
# Date 1198258126 18000
# Node ID 4a790ca9ee23434a466ea9003910138ed6d30165
# Parent b9f149a476dd82c2098e4864179c3765c0bb7b70
tda18271: fix typo in RF tracking filter calibration

From: Michael Krufky mkrufky at linuxtv dot org

We want to set bits 1  2 on easy programming byte 4, not extended byte 4.

Thanks to David Wong for pointing this out.

Cc: David Wong davidtlwong at gmail dot com
Signed-off-by: Michael Krufky mkrufky at linuxtv dot org

--- a/linux/drivers/media/dvb/frontends/tda18271-fe.c   Tue Dec 18 08:42:33 
2007 -0500
+++ b/linux/drivers/media/dvb/frontends/tda18271-fe.c   Fri Dec 21 12:28:46 
2007 -0500
@@ -414,7 +414,7 @@ static int tda18271_tune(struct dvb_fron
tda18271_write_regs(fe, R_EB20, 1);
 
/* set CAL mode to RF tracking filter calibration */
-   regs[R_EB4]  |= 0x03;
+   regs[R_EP4]  |= 0x03;
 
/* calculate CAL PLL */
 

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-31 Thread Manu Abraham
Michael Krufky wrote:
 Manu Abraham wrote:
 Michael Krufky wrote:

 Manu Abraham wrote:
 Some of the vendors (more than one) wrote to me that the TDA18271 driver 
 doesn't work. That was the basis of my statement.
 Silly vendors.  Why write to _you_ about somebody else's work?

 One of the vendors cc'd me, since they did ask you and had no response from 
 you
 They asked me to work on a driver from ground up or fix your driver, since 
 you told
 them that you had no time.

 I hope some ghost didn't write the inlined mail.
 
 [quoted mail snipped]
 
 Manu,
 
 I'd appreciate it if you would NOT post private email threads to a public 
 mailing list.
 
 (haven't we gone down this road before?)
 

Mike,

When you talk 2 different tongues, that's the only way left .. 
Sorry about that.

 Max got the tda18271 driver working on his device -- a typo was identified 
 that had prevented DVB-T / DMB-T tuning from working.
 

Maybe, but afaih not.

Manu

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-31 Thread Zdenek Kabelac
2007/12/31, Manu Abraham [EMAIL PROTECTED]:
 Zdenek Kabelac wrote:
  2007/12/31, Michael Krufky [EMAIL PROTECTED]:
  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.


Hi Manu

I'd like to hear it clearly - should I safe my time to play with this device?

Do you mean by this answer that you know someone already writes the
driver for AsusTV Hybrid Volar HX USB device ?

(And driver will be opensource and usable with any kernel I need ?)

What is the timeplan of this event ?

Thanks for your answers.

Regards

Zdenek

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


[linux-dvb] AverTV Hybrid Volar HX

2007-12-30 Thread Zdenek Kabelac
Hello

I should start a new thread about this USB2.0 device.

I'd like to get this device working - from another thread on this list
it looks like it should be possible to achieve.

So I'd like to get some information (and eventually some irc
help/short introduction) how to make it working.

I've tried simply to extend current Aver Volar Dib0700 code :) however
except from the fact I get  firmware loader somewhere, I'm for this
moment lost (well it's been just a wild blind try what will happen ;))

I'll repeat which chips I could find in the USB device -
SAA7136E,CY7C68013A,TDA18271HDC1

So how could I connect these pieces together into some usable stage
(at least for DVB-T for this moment.

Which tree should I select (where all these chips would be supported
at the some time - from the first overview it looks like there is way
too many different trees.

Regards,

Zdenek

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-30 Thread Michael Krufky
Zdenek Kabelac wrote:
 Hello
 
 I should start a new thread about this USB2.0 device.
 
 I'd like to get this device working - from another thread on this list
 it looks like it should be possible to achieve.
 
 So I'd like to get some information (and eventually some irc
 help/short introduction) how to make it working.
 
 I've tried simply to extend current Aver Volar Dib0700 code :) however
 except from the fact I get  firmware loader somewhere, I'm for this
 moment lost (well it's been just a wild blind try what will happen ;))
 
 I'll repeat which chips I could find in the USB device -
 SAA7136E,CY7C68013A,TDA18271HDC1
 
 So how could I connect these pieces together into some usable stage
 (at least for DVB-T for this moment.
 
 Which tree should I select (where all these chips would be supported
 at the some time - from the first overview it looks like there is way
 too many different trees.

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?

Regards,

Mike

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-30 Thread Zdenek Kabelac
2007/12/31, Michael Krufky [EMAIL PROTECTED]:
 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.

Here is the text list of chips I could have identify.

NXP
SAA7136E/1/G
SH0780.1  06
ZSG07361

CY7C68013A-56LFXC 0731
B 04 KOR
CYP 640386

AF9013-N1
0732 HKH2Y

TDA18271HDC1
P2KHT08 03
cmG07121Y
9423

LBNJN256721

H207H

2464WP

24.000
H.ELE.7K

A827-C

Regards

Zdenek

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-30 Thread Michael Krufky
Sorry for sending this twice -- I forgot to cc the list last time.

Zdenek Kabelac wrote:

  2007/12/31, Michael Krufky [EMAIL PROTECTED]:
   
 
   
  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.
  
  Here is the text list of chips I could have identify.
   

  AF9013-N1
  0732 HKH2Y
   


I believe that this afatech device is what you want to start off working with, 
for dvb support.  Unfortunately, I don't know much about those, but I think 
there is somebody working on it.

-Mike



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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-30 Thread Manu Abraham
Zdenek Kabelac wrote:
 2007/12/31, Michael Krufky [EMAIL PROTECTED]:
 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.

Manu

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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-30 Thread Michael Krufky
Manu Abraham wrote:
 Zdenek Kabelac wrote:
   
 2007/12/31, Michael Krufky [EMAIL PROTECTED]:
 
 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.

Regards,

Mike Krufky


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


Re: [linux-dvb] AverTV Hybrid Volar HX

2007-12-30 Thread Manu Abraham
Michael Krufky wrote:
 Manu Abraham wrote:
 Zdenek Kabelac wrote:
   
 2007/12/31, Michael Krufky [EMAIL PROTECTED]:
 
 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)

Manu

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