Re: Drivers for Eyetv hybrid

2010-01-25 Thread Morten Friesgaard
Sound like a lot of work, and it would be easier just to buy a
functional tuner :)

Guess I'm busy enough. However, I did manage to find some more info,
for someone to use someday :)
/Morten

Model: EU 2008
USB Contoller: Empia EM2884
Stereo A/V Decoder: Micronas AVF 49x08
Hybrid Channel Decoder: Micronas DRX-K DRX3926K:A1 0.9.0

On Fri, Jan 22, 2010 at 5:27 PM, Devin Heitmueller
dheitmuel...@kernellabs.com wrote:
 On Fri, Jan 22, 2010 at 11:18 AM, Morten Friesgaard
 friesga...@gmail.com wrote:
 Actually I don't understand why this em28xx driver is the only one
 being patched, guess that reduces backward compability!? :-P

 There are many drivers actively being developed.  What I'm trying to
 say is that the new version of the EyeTV Hybrid is not an em28xx based
 hardware design.

 Well, I haven't given up, but no one has given me any pointers but /dev/null
 If this em28xx module would be startable with the usb id 0fd9:0018,
 I could tryout the old driver.
 If you say the hardware design is completely different, I guess it
 should still be possible to mount the usb device and fetch anything
 from the device (e.g. tvtime -d /dev/usbdev). The driver would be a
 matter of controlling the device to tune to the correct channel etc.

 No, that is not how USB drivers work.  You have to know how to program
 the various chips on the device (the bridge, demodulator, decoder,
 tuner), as well as knowing how to decode the packets coming back from
 the device.  If you want to get an understanding as to how complex the
 drivers are then feel free to look at some of them in the v4l-dvb
 source code.  You can get a better understanding as to how these
 devices are designed here:

 KernelLabs Blog:  How Tuners Work...
 http://www.kernellabs.com/blog/?p=1045

 When new hardware is introduced, how do you guys break down the task
 and implement a driver? (how much can be borrow from the mac os x
 drivers?)

 It largely depends on the device.  Usually you start by cracking it
 open and seeing what chips it contains, and from there you can see
 which components currently have a driver and which do not.  Whether
 the various components are already supported usually drives whether a
 whole new driver is required or just a board profile in an existing
 driver.  And whether datasheets are available publicly dictates how
 easy/hard it is to write a driver (the datasheets are usually *not*
 available for modern devices, or only available under NDA).

 Devin

 --
 Devin J. Heitmueller - Kernel Labs
 http://www.kernellabs.com

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Drivers for Eyetv hybrid

2010-01-25 Thread Devin Heitmueller
On Mon, Jan 25, 2010 at 3:05 PM, Morten Friesgaard friesga...@gmail.com wrote:
 Sound like a lot of work, and it would be easier just to buy a
 functional tuner :)

 Guess I'm busy enough. However, I did manage to find some more info,
 for someone to use someday :)
 /Morten

 Model: EU 2008
 USB Contoller: Empia EM2884
 Stereo A/V Decoder: Micronas AVF 49x08
 Hybrid Channel Decoder: Micronas DRX-K DRX3926K:A1 0.9.0

Correct, this is an em2884/drx-k/xc5000 design.  The em2884 work is
pretty straightforward, and the xc5000 driver should work as-is.
The big issue is the drx-k driver, for which there is no currently
driver at all.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Drivers for Eyetv hybrid

2010-01-22 Thread Morten Friesgaard
Actually I don't understand why this em28xx driver is the only one
being patched, guess that reduces backward compability!? :-P

Well, I haven't given up, but no one has given me any pointers but /dev/null
If this em28xx module would be startable with the usb id 0fd9:0018,
I could tryout the old driver.
If you say the hardware design is completely different, I guess it
should still be possible to mount the usb device and fetch anything
from the device (e.g. tvtime -d /dev/usbdev). The driver would be a
matter of controlling the device to tune to the correct channel etc.

When new hardware is introduced, how do you guys break down the task
and implement a driver? (how much can be borrow from the mac os x
drivers?)

/Morten



On Thu, Jan 21, 2010 at 5:06 PM, Simon Kenyon si...@koala.ie wrote:
 On 21/01/2010 12:07, Markus Rechberger wrote:

 On Thu, Jan 21, 2010 at 10:55 AM, Morten Friesgaard
 friesga...@gmail.com  wrote:


 To bad. I bought this tuner because of the cross platform compability :-/

 Well, it looks awfully alot like the TerraTec H5, would there be a
 driver this one?
 http://www.terratec.net/en/products/TerraTec_H5_83188.html



 just fyi. this Terratec device is not supported. We've been working on
 a device with equivalent features
 (DVB-T/C/AnalogTV/VBI/Composite/S-Video/FM-Radio/RDS/Remote Control)
 http://support.sundtek.com/index.php/topic,4.0.html
 We are also integrating additional flexible USB CI support for it.

 Best Regards,
 Markus Rechberger


 you just don't give up - do you?
 --
 To unsubscribe from this list: send the line unsubscribe linux-media in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Drivers for Eyetv hybrid

2010-01-22 Thread Devin Heitmueller
On Fri, Jan 22, 2010 at 11:18 AM, Morten Friesgaard
friesga...@gmail.com wrote:
 Actually I don't understand why this em28xx driver is the only one
 being patched, guess that reduces backward compability!? :-P

There are many drivers actively being developed.  What I'm trying to
say is that the new version of the EyeTV Hybrid is not an em28xx based
hardware design.

 Well, I haven't given up, but no one has given me any pointers but /dev/null
 If this em28xx module would be startable with the usb id 0fd9:0018,
 I could tryout the old driver.
 If you say the hardware design is completely different, I guess it
 should still be possible to mount the usb device and fetch anything
 from the device (e.g. tvtime -d /dev/usbdev). The driver would be a
 matter of controlling the device to tune to the correct channel etc.

No, that is not how USB drivers work.  You have to know how to program
the various chips on the device (the bridge, demodulator, decoder,
tuner), as well as knowing how to decode the packets coming back from
the device.  If you want to get an understanding as to how complex the
drivers are then feel free to look at some of them in the v4l-dvb
source code.  You can get a better understanding as to how these
devices are designed here:

KernelLabs Blog:  How Tuners Work...
http://www.kernellabs.com/blog/?p=1045

 When new hardware is introduced, how do you guys break down the task
 and implement a driver? (how much can be borrow from the mac os x
 drivers?)

It largely depends on the device.  Usually you start by cracking it
open and seeing what chips it contains, and from there you can see
which components currently have a driver and which do not.  Whether
the various components are already supported usually drives whether a
whole new driver is required or just a board profile in an existing
driver.  And whether datasheets are available publicly dictates how
easy/hard it is to write a driver (the datasheets are usually *not*
available for modern devices, or only available under NDA).

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Drivers for Eyetv hybrid

2010-01-21 Thread Morten Friesgaard
To bad. I bought this tuner because of the cross platform compability :-/

Well, it looks awfully alot like the TerraTec H5, would there be a
driver this one?
http://www.terratec.net/en/products/TerraTec_H5_83188.html

How hard is it to create a driver myself? I'm an engineer, have some
knowlege with building the linux kernel, patching firmware etc.

/Morten


On Wed, Jan 20, 2010 at 7:00 PM, Devin Heitmueller
dheitmuel...@kernellabs.com wrote:
 On Wed, Jan 20, 2010 at 12:26 PM, Morten Friesgaard
 friesga...@gmail.com wrote:
 Hello.
 I installed mythbuntu 9.10 this week on some old hardware, I had a
 Hauppauge 500MCE PVR in and made it work fairly easy. I'm used to
 gentoo

 However, I want to record HD signal, so I plugged in a Eyetv hybrid
 and followed this guide
 http://ubuntuforums.org/showthread.php?t=1015387

 I extracted the driver, put it in into /lib/firmware, modprobed
 em28xx, rebooted. When I plug in the device, it is not recognised. I
 tried both usb ports. The ID is 0fd9:0018, which is somewhat
 different from similar hardware e.g. Hauppauge wintv-hvr-950 (ID
 2040:6513 http://www.linuxtv.org/wiki/index.ph..._WinTV-HVR-950 )

 It's a totally different hardware design, nothing like the older
 version of the EyeTV Hybrid (which was just a clone of the HVR-950).

 It is unsupported currently (and nobody is working on it to my knowledge).

 Devin

 --
 Devin J. Heitmueller - Kernel Labs
 http://www.kernellabs.com

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Drivers for Eyetv hybrid

2010-01-21 Thread Markus Rechberger
On Thu, Jan 21, 2010 at 10:55 AM, Morten Friesgaard
friesga...@gmail.com wrote:
 To bad. I bought this tuner because of the cross platform compability :-/

 Well, it looks awfully alot like the TerraTec H5, would there be a
 driver this one?
 http://www.terratec.net/en/products/TerraTec_H5_83188.html


just fyi. this Terratec device is not supported. We've been working on
a device with equivalent features
(DVB-T/C/AnalogTV/VBI/Composite/S-Video/FM-Radio/RDS/Remote Control)
http://support.sundtek.com/index.php/topic,4.0.html
We are also integrating additional flexible USB CI support for it.

Best Regards,
Markus Rechberger
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Drivers for Eyetv hybrid

2010-01-21 Thread Simon Kenyon

On 21/01/2010 12:07, Markus Rechberger wrote:

On Thu, Jan 21, 2010 at 10:55 AM, Morten Friesgaard
friesga...@gmail.com  wrote:
   

To bad. I bought this tuner because of the cross platform compability :-/

Well, it looks awfully alot like the TerraTec H5, would there be a
driver this one?
http://www.terratec.net/en/products/TerraTec_H5_83188.html

 

just fyi. this Terratec device is not supported. We've been working on
a device with equivalent features
(DVB-T/C/AnalogTV/VBI/Composite/S-Video/FM-Radio/RDS/Remote Control)
http://support.sundtek.com/index.php/topic,4.0.html
We are also integrating additional flexible USB CI support for it.

Best Regards,
Markus Rechberger
   

you just don't give up - do you?
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Drivers for Eyetv hybrid

2010-01-20 Thread Morten Friesgaard
Hello.
I installed mythbuntu 9.10 this week on some old hardware, I had a
Hauppauge 500MCE PVR in and made it work fairly easy. I'm used to
gentoo

However, I want to record HD signal, so I plugged in a Eyetv hybrid
and followed this guide
http://ubuntuforums.org/showthread.php?t=1015387

I extracted the driver, put it in into /lib/firmware, modprobed
em28xx, rebooted. When I plug in the device, it is not recognised. I
tried both usb ports. The ID is 0fd9:0018, which is somewhat
different from similar hardware e.g. Hauppauge wintv-hvr-950 (ID
2040:6513 http://www.linuxtv.org/wiki/index.ph..._WinTV-HVR-950 )

I think the hardware has been updated, hope someone knows how to crack this one
Thanks, Morten


I have added some additional information below!
# uname -a
Linux m 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
i686 GNU/Linux

# lsmod | egrep -R video|em|video|v4l
em28xx 80968 0
ir_common 48512 1 em28xx
videobuf_vmalloc 6496 1 em28xx
videobuf_core 17952 2 em28xx,videobuf_vmalloc
v4l2_common 17500 6 em28xx,wm8775,tuner,cx25840,ivtv,cx2341x
videodev 36736 6 em28xx,wm8775,tuner,cx25840,ivtv,v4l2_common
v4l1_compat 14496 1 videodev
tveeprom 11872 2 em28xx,ivtv

# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0fd9:0018
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

# lsusb -v -d 0fd9:0018
Bus 002 Device 002: ID 0fd9:0018
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0fd9
idProduct 0x0018
bcdDevice 1.00
iManufacturer 3
iProduct 1
iSerial 2
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 305
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0280 1x 640 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class

Re: Drivers for Eyetv hybrid

2010-01-20 Thread Devin Heitmueller
On Wed, Jan 20, 2010 at 12:26 PM, Morten Friesgaard
friesga...@gmail.com wrote:
 Hello.
 I installed mythbuntu 9.10 this week on some old hardware, I had a
 Hauppauge 500MCE PVR in and made it work fairly easy. I'm used to
 gentoo

 However, I want to record HD signal, so I plugged in a Eyetv hybrid
 and followed this guide
 http://ubuntuforums.org/showthread.php?t=1015387

 I extracted the driver, put it in into /lib/firmware, modprobed
 em28xx, rebooted. When I plug in the device, it is not recognised. I
 tried both usb ports. The ID is 0fd9:0018, which is somewhat
 different from similar hardware e.g. Hauppauge wintv-hvr-950 (ID
 2040:6513 http://www.linuxtv.org/wiki/index.ph..._WinTV-HVR-950 )

It's a totally different hardware design, nothing like the older
version of the EyeTV Hybrid (which was just a clone of the HVR-950).

It is unsupported currently (and nobody is working on it to my knowledge).

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html