[linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

I have a machine that has an internal card that's a Lifeview DVB and
works fine using the v4l-dvb mercurial sources.

I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
using the v4l-dvb sources but does work using the v4l-dvb-kernel
version.

1.  Will the number of em28xx cards supported by v4l-dvb be increased
shortly?  (My card id was 94 IIRC ).

2.  Can I mix and match from the sources...i.e. can I graft the em28xx
stuff from v4l-dvb-kernel into the v4l-dvb source and compile
successfully or has the underlying code changed at a more strategic
level?

3.  Why did the sources branch?  Was there a good technical reason for this?

4.  If I can't use the v4l-dvb sources to get my em28xx working what's
the chances of getting the v4l-dvb-kernel stuff working for the
lifeview flydvb card?

Thanks in advance.

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Markus Rechberger]

On 3/31/08, Another Sillyname <anothersname@googlemail.com> wrote:
> I have a machine that has an internal card that's a Lifeview DVB and
> works fine using the v4l-dvb mercurial sources.
>
> I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
> using the v4l-dvb sources but does work using the v4l-dvb-kernel
> version.
>
> 1. Will the number of em28xx cards supported by v4l-dvb be increased
> shortly? (My card id was 94 IIRC ).
>
> 2. Can I mix and match from the sources...i.e. can I graft the em28xx
> stuff from v4l-dvb-kernel into the v4l-dvb source and compile
> successfully or has the underlying code changed at a more strategic
> level?
>
> 3. Why did the sources branch? Was there a good technical reason for this?
>
> 4. If I can't use the v4l-dvb sources to get my em28xx working what's
> the chances of getting the v4l-dvb-kernel stuff working for the
> lifeview flydvb card?
>

Hi,

do you have the pinnacle 330e or the 320e?
(following is the 320e)
http://www.compareindia.com/media/images/2007/jul/img_5282_2601_pinnacle.jpg

Markus

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

It's a 320...specifically a eb1a:2881 Pinnacle badged empia technology unit..

If you like I could reinstall the v4l-dvb-kernel sources and give you
a complete breakdown on the unit?

Thanks Markus



On 31/03/2008, Markus Rechberger <mrechberger@gmail.com> wrote:
> On 3/31/08, Another Sillyname <anothersname@googlemail.com> wrote:
>  > I have a machine that has an internal card that's a Lifeview DVB and
>  > works fine using the v4l-dvb mercurial sources.
>  >
>  > I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
>  > using the v4l-dvb sources but does work using the v4l-dvb-kernel
>  > version.
>  >
>  > 1. Will the number of em28xx cards supported by v4l-dvb be increased
>  > shortly? (My card id was 94 IIRC ).
>  >
>  > 2. Can I mix and match from the sources...i.e. can I graft the em28xx
>  > stuff from v4l-dvb-kernel into the v4l-dvb source and compile
>  > successfully or has the underlying code changed at a more strategic
>  > level?
>  >
>  > 3. Why did the sources branch? Was there a good technical reason for this?
>  >
>  > 4. If I can't use the v4l-dvb sources to get my em28xx working what's
>  > the chances of getting the v4l-dvb-kernel stuff working for the
>  > lifeview flydvb card?
>  >
>
>
> Hi,
>
>  do you have the pinnacle 330e or the 320e?
>  (following is the 320e)
>  http://www.compareindia.com/media/images/2007/jul/img_5282_2601_pinnacle.jpg
>
>
>  Markus
>

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

Markus

You still out there?

I've got to hit the sack shortly.

J

On 31/03/2008, Another Sillyname <anothersname@googlemail.com> wrote:
> It's a 320...specifically a eb1a:2881 Pinnacle badged empia technology unit..
>
>  If you like I could reinstall the v4l-dvb-kernel sources and give you
>  a complete breakdown on the unit?
>
>  Thanks Markus
>
>
>
>
>  On 31/03/2008, Markus Rechberger <mrechberger@gmail.com> wrote:
>  > On 3/31/08, Another Sillyname <anothersname@googlemail.com> wrote:
>  >  > I have a machine that has an internal card that's a Lifeview DVB and
>  >  > works fine using the v4l-dvb mercurial sources.
>  >  >
>  >  > I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
>  >  > using the v4l-dvb sources but does work using the v4l-dvb-kernel
>  >  > version.
>  >  >
>  >  > 1. Will the number of em28xx cards supported by v4l-dvb be increased
>  >  > shortly? (My card id was 94 IIRC ).
>  >  >
>  >  > 2. Can I mix and match from the sources...i.e. can I graft the em28xx
>  >  > stuff from v4l-dvb-kernel into the v4l-dvb source and compile
>  >  > successfully or has the underlying code changed at a more strategic
>  >  > level?
>  >  >
>  >  > 3. Why did the sources branch? Was there a good technical reason for this?
>  >  >
>  >  > 4. If I can't use the v4l-dvb sources to get my em28xx working what's
>  >  > the chances of getting the v4l-dvb-kernel stuff working for the
>  >  > lifeview flydvb card?
>  >  >
>  >
>  >
>  > Hi,
>  >
>  >  do you have the pinnacle 330e or the 320e?
>  >  (following is the 320e)
>  >  http://www.compareindia.com/media/images/2007/jul/img_5282_2601_pinnacle.jpg
>  >
>  >
>  >  Markus
>  >
>

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Markus Rechberger]

On Mon, Mar 31, 2008 at 4:20 AM, Another Sillyname
<anothersname@googlemail.com> wrote:
> Markus
>
>  You still out there?
>
>  I've got to hit the sack shortly.
>
>

Sorry I've been busy yesterday...
I'll do some tests with your device tonight..

Markus

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

[-- Attachment #1: Type: text/plain, Size: 748 bytes --]

Hi Markus

Just so you know here's my dmesgs (shortened for obvious reasons)

em28xxnotworking installed the card using v4l-dvb but as you can see
the SAA Flyview card is working correctly.

em28xxworkingdmesg installed the card using v4l-dvb-kernel where the
em28xx card is working fully and correctly but now the SAA is not
working correctly.

All ideas gratefully received.....

J



On 31/03/2008, Markus Rechberger <mrechberger@gmail.com> wrote:
> On Mon, Mar 31, 2008 at 4:20 AM, Another Sillyname
>  <anothersname@googlemail.com> wrote:
>  > Markus
>  >
>  >  You still out there?
>  >
>  >  I've got to hit the sack shortly.
>  >
>  >
>
>
> Sorry I've been busy yesterday...
>  I'll do some tests with your device tonight..
>
>
>  Markus
>

[-- Attachment #2: em28xxnotworkingshort.txt --]
[-- Type: text/plain, Size: 6820 bytes --]

ALSA sound/usb/usbaudio.c:2753: 6:2:1: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 6:2:2: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 6:2:3: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 6:2:4: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 6:2:5: add audio endpoint 0x83
ALSA sound/usb/usbmixer.c:989: [2] FU [PCM Capture Switch] ch = 1, val = 0/1/1
PCI: Enabling device 0000:03:05.0 (0015 -> 0017)
ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 16 (level, low) -> IRQ 16
ALSA sound/usb/usbmixer.c:406: cannot set ctl value: req = 0x4, wValue = 0x200, wIndex = 0x201, type = 4, data = 0x0/0x1
ALSA sound/usb/usbmixer.c:989: [2] FU [PCM Capture Volume] ch = 1, val = 0/0/512
usbcore: registered new interface driver snd-usb-audio
input: PC Speaker as /class/input/input7
Linux video capture interface: v2.00
em28xx v4l2 driver version 0.1.0 loaded
em28xx new video device (eb1a:2881): interface 0, class 255
em28xx Has usb audio class
em28xx #0: Alternate settings: 8
em28xx #0: Alternate setting 0, max size= 0
em28xx #0: Alternate setting 1, max size= 0
em28xx #0: Alternate setting 2, max size= 1448
em28xx #0: Alternate setting 3, max size= 2048
em28xx #0: Alternate setting 4, max size= 2304
em28xx #0: Alternate setting 5, max size= 2580
em28xx #0: Alternate setting 6, max size= 2892
em28xx #0: Alternate setting 7, max size= 3072
em28xx #0: em28xx chip ID = 36
saa7130/34: v4l2 driver version 0.2.14 loaded
saa7133[0]: found at 0000:03:03.0, rev: 209, irq: 19, latency: 64, mmio: 0xfe8ff800
saa7133[0]: subsystem: 5168:3307, board: LifeView FlyDVB-T Hybrid Cardbus/MSI TV @nywhere A/D NB [card=94,autodetected]
saa7133[0]: board init: gpio is 10000
ALSA sound/core/init.c:137: cannot find the slot for index 0 (range 0-0), error: -16
ALSA sound/pci/hda/hda_intel.c:1880: hda-intel: Error creating card!
HDA Intel: probe of 0000:00:1b.0 failed with error -12
em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 81 28 58 12 5c 00 6a 20 6a 00
em28xx #0: i2c eeprom 10: 00 00 04 57 64 57 00 00 60 f4 00 00 02 02 00 00
em28xx #0: i2c eeprom 20: 56 00 01 00 00 00 02 00 b8 00 00 00 5b 1e 00 00
em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 10 02 00 00 00 00 00 00
em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 20 03 55 00 53 00
em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 38 00 31 00 20 00 56 00
em28xx #0: i2c eeprom 80: 69 00 64 00 65 00 6f 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom e0: 5a 00 55 aa 79 55 54 03 00 17 98 01 00 00 00 00
em28xx #0: i2c eeprom f0: 0c 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00
EEPROM ID= 0x9567eb1a, hash = 0xb8846b20
Vendor/Product ID= eb1a:2881
AC97 audio (5 sample rates)
USB Remote wakeup capable
500mA max power
Table at 0x04, strings=0x206a, 0x006a, 0x0000
em28xx #0: found i2c device @ 0x1e [???]
em28xx #0: found i2c device @ 0xa0 [eeprom]
em28xx #0: found i2c device @ 0xb8 [tvp5150a]
em28xx #0: found i2c device @ 0xc2 [tuner (analog)]
em28xx #0: Your board has no unique USB ID and thus need a hint to be detected.
em28xx #0: You may try to use card=<n> insmod option to workaround that.
em28xx #0: Please send an email with this log to:
em28xx #0: 	V4L Mailing List <video4linux-list@redhat.com>
em28xx #0: Board eeprom hash is 0xb8846b20
em28xx #0: Board i2c devicelist hash is 0x944d008f
em28xx #0: Here is a list of valid choices for the card=<n> insmod option:
em28xx #0:     card=0 -> Unknown EM2800 video grabber
em28xx #0:     card=1 -> Unknown EM2750/28xx video grabber
em28xx #0:     card=2 -> Terratec Cinergy 250 USB
em28xx #0:     card=3 -> Pinnacle PCTV USB 2
em28xx #0:     card=4 -> Hauppauge WinTV USB 2
em28xx #0:     card=5 -> MSI VOX USB 2.0
em28xx #0:     card=6 -> Terratec Cinergy 200 USB
em28xx #0:     card=7 -> Leadtek Winfast USB II
em28xx #0:     card=8 -> Kworld USB2800
em28xx #0:     card=9 -> Pinnacle Dazzle DVC 90/DVC 100
em28xx #0:     card=10 -> Hauppauge WinTV HVR 900
em28xx #0:     card=11 -> Terratec Hybrid XS
em28xx #0:     card=12 -> Kworld PVR TV 2800 RF
em28xx #0:     card=13 -> Terratec Prodigy XS
em28xx #0:     card=14 -> Pixelview Prolink PlayTV USB 2.0
em28xx #0:     card=15 -> V-Gear PocketTV
em28xx #0:     card=16 -> Hauppauge WinTV HVR 950
saa7133[0]: i2c eeprom 00: 68 51 07 33 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: 00 00 62 08 ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 03 03 01 01 03 08 ff 01 17 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 05 00 01 16 22 15 ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
tuner' 1-0061: chip found @ 0xc2 (em28xx #0)
tuner' 2-004b: chip found @ 0x96 (saa7133[0])
tvp5150 1-005c: tvp5150am1 detected.
tda829x 2-004b: setting tuner address to 61
tda829x 2-004b: type set to tda8290+75a
em28xx #0: V4L2 device registered as /dev/video0 and /dev/vbi0
em28xx #0: Found Unknown EM2750/28xx video grabber
usbcore: registered new interface driver em28xx
saa7133[0]: registered device video1 [v4l2]
saa7133[0]: registered device vbi1
saa7133[0]: registered device radio0
DVB: registering new adapter (saa7133[0])
DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
tda1004x: setting up plls for 48MHz sampling clock
SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
tda1004x: found firmware revision 29 -- ok
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok
ALSA sound/usb/usbaudio.c:1327: setting usb interface 2:2

[-- Attachment #3: em28xxworkingdmesgshort.txt --]
[-- Type: text/plain, Size: 5584 bytes --]

ALSA sound/usb/usbaudio.c:2753: 6:2:1: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 6:2:2: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 6:2:3: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 6:2:4: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 6:2:5: add audio endpoint 0x83
ALSA sound/usb/usbmixer.c:989: [2] FU [PCM Capture Switch] ch = 1, val = 0/1/1
ALSA sound/usb/usbmixer.c:406: cannot set ctl value: req = 0x4, wValue = 0x200, wIndex = 0x201, type = 4, data = 0x0/0x1
ALSA sound/usb/usbmixer.c:989: [2] FU [PCM Capture Volume] ch = 1, val = 0/0/512
usbcore: registered new interface driver snd-usb-audio
Linux video capture interface: v2.00
em28xx v4l2 driver version 0.0.1 loaded
em28xx new video device (eb1a:2881): interface 0, class 255
em28xx: device is attached to a USB 2.0 bus
em28xx: you're using the experimental/unstable tree from mcentral.de
em28xx: there's also a stable tree available but which is limited to
em28xx: linux <=2.6.19.2
em28xx: it's fine to use this driver but keep in mind that it will move
em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's
em28xx: proved to be stable
em28xx #0: Alternate settings: 8
em28xx #0: Alternate setting 0, max size= 0
em28xx #0: Alternate setting 1, max size= 0
em28xx #0: Alternate setting 2, max size= 1448
em28xx #0: Alternate setting 3, max size= 2048
em28xx #0: Alternate setting 4, max size= 2304
em28xx #0: Alternate setting 5, max size= 2580
em28xx #0: Alternate setting 6, max size= 2892
em28xx #0: Alternate setting 7, max size= 3072
ALSA sound/core/init.c:137: cannot find the slot for index 0 (range 0-0), error: -16
ALSA sound/pci/hda/hda_intel.c:1880: hda-intel: Error creating card!
saa7130/34: v4l2 driver version 0.2.14 loaded
saa7133[0]: found at 0000:03:03.0, rev: 209, irq: 19, latency: 64, mmio: 0xfe8ff800
saa7133[0]: subsystem: 5168:3307, board: UNKNOWN/GENERIC [card=0,autodetected]
saa7133[0]: board init: gpio is 10000
tuner 1-004b: chip found @ 0x96 (saa7133[0])
/usr/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback
/usr/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback
saa7133[0]: i2c eeprom 00: 68 51 07 33 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: 00 00 62 08 ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 03 03 01 01 03 08 ff 01 17 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 05 00 01 16 22 15 ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
input: em2880/em2870 remote control as /class/input/input8
em28xx-input.c: remote control handler attached
attach_inform: eeprom detected.
em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 81 28 58 12 5c 00 6a 20 6a 00
em28xx #0: i2c eeprom 10: 00 00 04 57 64 57 00 00 60 f4 00 00 02 02 00 00
em28xx #0: i2c eeprom 20: 56 00 01 00 00 00 02 00 b8 00 00 00 5b 1e 00 00
em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 10 02 00 00 00 00 00 00
em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 20 03 55 00 53 00
em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 38 00 31 00 20 00 56 00
em28xx #0: i2c eeprom 80: 69 00 64 00 65 00 6f 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom e0: 5a 00 55 aa 79 55 54 03 00 17 98 01 00 00 00 00
em28xx #0: i2c eeprom f0: 0c 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00
EEPROM ID= 0x9567eb1a
Vendor/Product ID= eb1a:2881
AC97 audio (5 sample rates)
USB Remote wakeup capable
500mA max power
Table at 0x04, strings=0x206a, 0x006a, 0x0000
tuner 2-0061: chip found @ 0xc2 (em28xx #0)
attach inform (default): detected I2C address c2
/usr/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback
tuner 0x61: Configuration acknowledged
/usr/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback
/usr/src/v4l-dvb-kernel/v4l/xc3028-tuner.c: attach request!
/usr/src/v4l-dvb-kernel/v4l/tuner-core.c: xc3028 tuner successfully loaded
attach_inform: tvp5150 detected.
tvp5150 2-005c: tvp5150am1 detected.
Loading base firmware: xc3028_init0.i2c.fw
Loading default analogue TV settings: xc3028_BG_PAL_A2_A.i2c.fw
xc3028-tuner.c: firmware 2.7
ANALOG TV REQUEST
em28xx #0: V4L2 VBI device registered as /dev/vbi1
em28xx #0: V4L2 device registered as /dev/video1
em28xx #0: Found Pinnacle Hybrid Pro
usbcore: registered new interface driver em28xx
em2880-dvb.c: DVB Init
Loading base firmware: xc3028_8MHz_init0.i2c.fw
Loading specific dtv settings: xc3028_DTV6_ATSC_2620.i2c.fw
xc3028-tuner.c: firmware 2.7
Sending extra call for Digital TV!
/usr/src/v4l-dvb-kernel/v4l/xc3028-tuner.c: attach request!
DVB: registering new adapter (em2880 DVB-T)
DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
Em28xx: Initialized (Em2880 DVB Extension) extension
ALSA sound/usb/usbaudio.c:1327: setting usb interface 2:2

[-- Attachment #4: Type: text/plain, Size: 150 bytes --]

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Aidan Thornton]

On Mon, Mar 31, 2008 at 12:40 AM, Another Sillyname
<anothersname@googlemail.com> wrote:
> I have a machine that has an internal card that's a Lifeview DVB and
>  works fine using the v4l-dvb mercurial sources.
>
>  I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
>  using the v4l-dvb sources but does work using the v4l-dvb-kernel
>  version.
>
>  1.  Will the number of em28xx cards supported by v4l-dvb be increased
>  shortly?  (My card id was 94 IIRC ).

If it's supported by v4l-dvb-kernel, it's entirely possible, yes.

>  2.  Can I mix and match from the sources...i.e. can I graft the em28xx
>  stuff from v4l-dvb-kernel into the v4l-dvb source and compile
>  successfully or has the underlying code changed at a more strategic
>  level?

Not trivially, since v4l-dvb-kernel contains changes to the core code
that the em28xx driver relies on and that are incompatible with
changes in the main v4l-dvb repository since. You can try
http://www.makomk.com/hg/v4l-dvb-makomk - it's the em28xx and xc3028
drivers grafted onto a version of v4l-dvb that's about 5 months old at
this point - though it's really not a great starting point for porting
them onto newer versions, since you'd want to drop the xc3028 driver
in favour of the newer one

>  3.  Why did the sources branch?  Was there a good technical reason for this?

Supporting the xc3028 silicon tuner needed some changes to support
hybrid analog/digital tuners better. Unfortunately, Markus couldn't
come to an agreement with the rest of the developers on how to do it.
(I think the main concern were that the changes he were proposing were
rather more invasive than they needed to be and risked breaking
existing drivers). In the end, someone else coded the equivalent
functionality in a more backwards-compatible way and merged it in
stages.

(It's actually relatively easy to port code from Markus' hybrid tuner
framework to the v4l-dvb one, though he will never admit so.)

>  4.  If I can't use the v4l-dvb sources to get my em28xx working what's
>  the chances of getting the v4l-dvb-kernel stuff working for the
>  lifeview flydvb card?

Not good. Its support for other hardware is, if anything, going to be
slowly getting worse over time as other drivers have to be modified or
disabled to make it compile on newer kernels.

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

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

Aidan

Any idea when the next 'batch' of em28xx cards will be added to
v4l-dvb or would that question be better asked on the dev list?

Thanks

On 31/03/2008, Aidan Thornton <makosoft@googlemail.com> wrote:
> On Mon, Mar 31, 2008 at 12:40 AM, Another Sillyname
>  <anothersname@googlemail.com> wrote:
>  > I have a machine that has an internal card that's a Lifeview DVB and
>  >  works fine using the v4l-dvb mercurial sources.
>  >
>  >  I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
>  >  using the v4l-dvb sources but does work using the v4l-dvb-kernel
>  >  version.
>  >
>  >  1.  Will the number of em28xx cards supported by v4l-dvb be increased
>  >  shortly?  (My card id was 94 IIRC ).
>
>
> If it's supported by v4l-dvb-kernel, it's entirely possible, yes.
>
>
>  >  2.  Can I mix and match from the sources...i.e. can I graft the em28xx
>  >  stuff from v4l-dvb-kernel into the v4l-dvb source and compile
>  >  successfully or has the underlying code changed at a more strategic
>  >  level?
>
>
> Not trivially, since v4l-dvb-kernel contains changes to the core code
>  that the em28xx driver relies on and that are incompatible with
>  changes in the main v4l-dvb repository since. You can try
>  http://www.makomk.com/hg/v4l-dvb-makomk - it's the em28xx and xc3028
>  drivers grafted onto a version of v4l-dvb that's about 5 months old at
>  this point - though it's really not a great starting point for porting
>  them onto newer versions, since you'd want to drop the xc3028 driver
>  in favour of the newer one
>
>
>  >  3.  Why did the sources branch?  Was there a good technical reason for this?
>
>
> Supporting the xc3028 silicon tuner needed some changes to support
>  hybrid analog/digital tuners better. Unfortunately, Markus couldn't
>  come to an agreement with the rest of the developers on how to do it.
>  (I think the main concern were that the changes he were proposing were
>  rather more invasive than they needed to be and risked breaking
>  existing drivers). In the end, someone else coded the equivalent
>  functionality in a more backwards-compatible way and merged it in
>  stages.
>
>  (It's actually relatively easy to port code from Markus' hybrid tuner
>  framework to the v4l-dvb one, though he will never admit so.)
>
>
>  >  4.  If I can't use the v4l-dvb sources to get my em28xx working what's
>  >  the chances of getting the v4l-dvb-kernel stuff working for the
>  >  lifeview flydvb card?
>
>
> Not good. Its support for other hardware is, if anything, going to be
>  slowly getting worse over time as other drivers have to be modified or
>  disabled to make it compile on newer kernels.
>
>  >  Thanks in advance.
>  >
>  >  _______________________________________________
>  >  linux-dvb mailing list
>  >  linux-dvb@linuxtv.org
>  >  http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>  >
>

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Markus Rechberger]

On 3/31/08, Aidan Thornton <makosoft@googlemail.com> wrote:
> On Mon, Mar 31, 2008 at 12:40 AM, Another Sillyname
> <anothersname@googlemail.com> wrote:
> > I have a machine that has an internal card that's a Lifeview DVB and
> > works fine using the v4l-dvb mercurial sources.
> >
> > I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
> > using the v4l-dvb sources but does work using the v4l-dvb-kernel
> > version.
> >
> > 1. Will the number of em28xx cards supported by v4l-dvb be increased
> > shortly? (My card id was 94 IIRC ).
>
> If it's supported by v4l-dvb-kernel, it's entirely possible, yes.
>
> > 2. Can I mix and match from the sources...i.e. can I graft the em28xx
> > stuff from v4l-dvb-kernel into the v4l-dvb source and compile
> > successfully or has the underlying code changed at a more strategic
> > level?
>
> Not trivially, since v4l-dvb-kernel contains changes to the core code
> that the em28xx driver relies on and that are incompatible with
> changes in the main v4l-dvb repository since. You can try
> http://www.makomk.com/hg/v4l-dvb-makomk - it's the em28xx and xc3028
> drivers grafted onto a version of v4l-dvb that's about 5 months old at
> this point - though it's really not a great starting point for porting
> them onto newer versions, since you'd want to drop the xc3028 driver
> in favour of the newer one
>

Makomk,
spreading around your even more broken tree won't help anyone.

This device already had some issues with the v4l-dvb-kernel tree, this
is what I'll do in April.

> > 3. Why did the sources branch? Was there a good technical reason for
> this?
>
> Supporting the xc3028 silicon tuner needed some changes to support
> hybrid analog/digital tuners better. Unfortunately, Markus couldn't
> come to an agreement with the rest of the developers on how to do it.
> (I think the main concern were that the changes he were proposing were
> rather more invasive than they needed to be and risked breaking
> existing drivers). In the end, someone else coded the equivalent
> functionality in a more backwards-compatible way and merged it in
> stages.
>
> (It's actually relatively easy to port code from Markus' hybrid tuner
> framework to the v4l-dvb one, though he will never admit so.)
>

The reason is my trust is gone I asked in September if it's possible
to get those devices work with what's available and I got the answer
it's not.
This stupid fight lasts for more than 2 years already, but I'm the one
who spent weeks on writing code for getting those things supported and
even rewrote code although there was no serious participation in the
discussions I tried to trigger...

If I tell a company that I will add support for something till a given
date I'll do so to keep up the good contacts. Unfortunately this is
not how some people at linuxtv behave and it slows down everything
even for other manufacturers where I'm not involved.

It's me who mostly spent his time on writing any code on mcentral.de,
the code didn't write itself especially Aidan has no respect about
that, neither do some other people. Maybe it's really better to
provide binary only blobs to remember especially such people that it
requires alot work to get those things work.

> > 4. If I can't use the v4l-dvb sources to get my em28xx working what's
> > the chances of getting the v4l-dvb-kernel stuff working for the
> > lifeview flydvb card?
>
> Not good. Its support for other hardware is, if anything, going to be
> slowly getting worse over time as other drivers have to be modified or
> disabled to make it compile on newer kernels.
>

that for the other repository (em28xx-userspace2/userspace-drivers on
mcentral.de/hg) is available, although it needs some work with that
device.

Markus

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Markus Rechberger]

On 4/1/08, Markus Rechberger <mrechberger@gmail.com> wrote:
> On 3/31/08, Aidan Thornton <makosoft@googlemail.com> wrote:
> > On Mon, Mar 31, 2008 at 12:40 AM, Another Sillyname
> > <anothersname@googlemail.com> wrote:
> > > I have a machine that has an internal card that's a Lifeview DVB and
> > > works fine using the v4l-dvb mercurial sources.
> > >
> > > I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
> > > using the v4l-dvb sources but does work using the v4l-dvb-kernel
> > > version.
> > >
> > > 1. Will the number of em28xx cards supported by v4l-dvb be increased
> > > shortly? (My card id was 94 IIRC ).
> >
> > If it's supported by v4l-dvb-kernel, it's entirely possible, yes.
> >
> > > 2. Can I mix and match from the sources...i.e. can I graft the em28xx
> > > stuff from v4l-dvb-kernel into the v4l-dvb source and compile
> > > successfully or has the underlying code changed at a more strategic
> > > level?
> >
> > Not trivially, since v4l-dvb-kernel contains changes to the core code
> > that the em28xx driver relies on and that are incompatible with
> > changes in the main v4l-dvb repository since. You can try
> > http://www.makomk.com/hg/v4l-dvb-makomk - it's the em28xx and xc3028
> > drivers grafted onto a version of v4l-dvb that's about 5 months old at
> > this point - though it's really not a great starting point for porting
> > them onto newer versions, since you'd want to drop the xc3028 driver
> > in favour of the newer one
> >
>
> Makomk,
> spreading around your even more broken tree won't help anyone.
>
> This device already had some issues with the v4l-dvb-kernel tree, this
> is what I'll do in April.
>
> > > 3. Why did the sources branch? Was there a good technical reason for
> > this?
> >
> > Supporting the xc3028 silicon tuner needed some changes to support
> > hybrid analog/digital tuners better. Unfortunately, Markus couldn't
> > come to an agreement with the rest of the developers on how to do it.
> > (I think the main concern were that the changes he were proposing were
> > rather more invasive than they needed to be and risked breaking
> > existing drivers). In the end, someone else coded the equivalent
> > functionality in a more backwards-compatible way and merged it in
> > stages.
> >
> > (It's actually relatively easy to port code from Markus' hybrid tuner
> > framework to the v4l-dvb one, though he will never admit so.)
> >
>
> The reason is my trust is gone I asked in September if it's possible
> to get those devices work with what's available and I got the answer
> it's not.
> This stupid fight lasts for more than 2 years already, but I'm the one
> who spent weeks on writing code for getting those things supported and
> even rewrote code although there was no serious participation in the
> discussions I tried to trigger...
>
> If I tell a company that I will add support for something till a given
> date I'll do so to keep up the good contacts. Unfortunately this is
> not how some people at linuxtv behave and it slows down everything
> even for other manufacturers where I'm not involved.
>
> It's me who mostly spent his time on writing any code on mcentral.de,
> the code didn't write itself especially Aidan has no respect about
> that, neither do some other people. Maybe it's really better to
> provide binary only blobs to remember especially such people that it
> requires alot work to get those things work.
>

there is still one thing which I remember when I attended the European
Linux Kernel summit 2007.
Jonathan Corbet held a presentation about kernel development, and
there was one sentence "we mustn't loose another developer".
This whole issue could be solved within 1 hour, and the fight of 2
years could be over immediately nearly without any work.
There's not much more to write about this.

> > > 4. If I can't use the v4l-dvb sources to get my em28xx working what's
> > > the chances of getting the v4l-dvb-kernel stuff working for the
> > > lifeview flydvb card?
> >
> > Not good. Its support for other hardware is, if anything, going to be
> > slowly getting worse over time as other drivers have to be modified or
> > disabled to make it compile on newer kernels.
> >
>
> that for the other repository (em28xx-userspace2/userspace-drivers on
> mcentral.de/hg) is available, although it needs some work with that
> device.
>
> Markus
>

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

Markus thanks for the response.

Am I correct in saying that your work will be on the v4l-dvb-kernel
branch and focused purely on the em28xx devices? Then you'll then be
migrating this work to v4l-dvb?

Or are you looking to 'clean up' the code that's currently in
v4l-dvb-kernel? without migrating it to v4l-dvb?

Obviously as I'm looking to get one device working from each branch
I'm a bit hamstrung at the moment.

Regards  and Thanks

On 01/04/2008, Markus Rechberger <mrechberger@gmail.com> wrote:
> On 4/1/08, Markus Rechberger <mrechberger@gmail.com> wrote:
>  > On 3/31/08, Aidan Thornton <makosoft@googlemail.com> wrote:
>  > > On Mon, Mar 31, 2008 at 12:40 AM, Another Sillyname
>  > > <anothersname@googlemail.com> wrote:
>  > > > I have a machine that has an internal card that's a Lifeview DVB and
>  > > > works fine using the v4l-dvb mercurial sources.
>  > > >
>  > > > I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
>  > > > using the v4l-dvb sources but does work using the v4l-dvb-kernel
>  > > > version.
>  > > >
>  > > > 1. Will the number of em28xx cards supported by v4l-dvb be increased
>  > > > shortly? (My card id was 94 IIRC ).
>  > >
>  > > If it's supported by v4l-dvb-kernel, it's entirely possible, yes.
>  > >
>  > > > 2. Can I mix and match from the sources...i.e. can I graft the em28xx
>  > > > stuff from v4l-dvb-kernel into the v4l-dvb source and compile
>  > > > successfully or has the underlying code changed at a more strategic
>  > > > level?
>  > >
>  > > Not trivially, since v4l-dvb-kernel contains changes to the core code
>  > > that the em28xx driver relies on and that are incompatible with
>  > > changes in the main v4l-dvb repository since. You can try
>  > > http://www.makomk.com/hg/v4l-dvb-makomk - it's the em28xx and xc3028
>  > > drivers grafted onto a version of v4l-dvb that's about 5 months old at
>  > > this point - though it's really not a great starting point for porting
>  > > them onto newer versions, since you'd want to drop the xc3028 driver
>  > > in favour of the newer one
>  > >
>  >
>  > Makomk,
>  > spreading around your even more broken tree won't help anyone.
>  >
>  > This device already had some issues with the v4l-dvb-kernel tree, this
>  > is what I'll do in April.
>  >
>  > > > 3. Why did the sources branch? Was there a good technical reason for
>  > > this?
>  > >
>  > > Supporting the xc3028 silicon tuner needed some changes to support
>  > > hybrid analog/digital tuners better. Unfortunately, Markus couldn't
>  > > come to an agreement with the rest of the developers on how to do it.
>  > > (I think the main concern were that the changes he were proposing were
>  > > rather more invasive than they needed to be and risked breaking
>  > > existing drivers). In the end, someone else coded the equivalent
>  > > functionality in a more backwards-compatible way and merged it in
>  > > stages.
>  > >
>  > > (It's actually relatively easy to port code from Markus' hybrid tuner
>  > > framework to the v4l-dvb one, though he will never admit so.)
>  > >
>  >
>  > The reason is my trust is gone I asked in September if it's possible
>  > to get those devices work with what's available and I got the answer
>  > it's not.
>  > This stupid fight lasts for more than 2 years already, but I'm the one
>  > who spent weeks on writing code for getting those things supported and
>  > even rewrote code although there was no serious participation in the
>  > discussions I tried to trigger...
>  >
>  > If I tell a company that I will add support for something till a given
>  > date I'll do so to keep up the good contacts. Unfortunately this is
>  > not how some people at linuxtv behave and it slows down everything
>  > even for other manufacturers where I'm not involved.
>  >
>  > It's me who mostly spent his time on writing any code on mcentral.de,
>  > the code didn't write itself especially Aidan has no respect about
>  > that, neither do some other people. Maybe it's really better to
>  > provide binary only blobs to remember especially such people that it
>  > requires alot work to get those things work.
>  >
>
>
> there is still one thing which I remember when I attended the European
>  Linux Kernel summit 2007.
>  Jonathan Corbet held a presentation about kernel development, and
>  there was one sentence "we mustn't loose another developer".
>  This whole issue could be solved within 1 hour, and the fight of 2
>  years could be over immediately nearly without any work.
>  There's not much more to write about this.
>
>
>  > > > 4. If I can't use the v4l-dvb sources to get my em28xx working what's
>  > > > the chances of getting the v4l-dvb-kernel stuff working for the
>  > > > lifeview flydvb card?
>  > >
>  > > Not good. Its support for other hardware is, if anything, going to be
>  > > slowly getting worse over time as other drivers have to be modified or
>  > > disabled to make it compile on newer kernels.
>  > >
>  >
>  > that for the other repository (em28xx-userspace2/userspace-drivers on
>  > mcentral.de/hg) is available, although it needs some work with that
>  > device.
>  >
>  > Markus
>  >
>

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Markus Rechberger]

On 4/1/08, Another Sillyname <anothersname@googlemail.com> wrote:
> Markus thanks for the response.
>
> Am I correct in saying that your work will be on the v4l-dvb-kernel
> branch and focused purely on the em28xx devices? Then you'll then be
> migrating this work to v4l-dvb?
>
> Or are you looking to 'clean up' the code that's currently in
> v4l-dvb-kernel? without migrating it to v4l-dvb?
>
> Obviously as I'm looking to get one device working from each branch
> I'm a bit hamstrung at the moment.
>

I already cut out the em28xx support so that it's possible to get it
work with v4l-dvb from linuxtv.org. Although this one only focussed at
a few newer devices for now I'm adding support for all the other
devices from this month on. The biggest part is to go through all the
videostandards and different input methods (svideo/composite).

v4l-dvb-kernel has support for several other devices too which are not
em28xx based and which I got work last year, it wasn't entirely em28xx
focussed.

Markus

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Aidan Thornton]

On 3/31/08, Markus Rechberger <mrechberger@gmail.com> wrote:
> On 3/31/08, Aidan Thornton <makosoft@googlemail.com> wrote:
> > On Mon, Mar 31, 2008 at 12:40 AM, Another Sillyname
> > <anothersname@googlemail.com> wrote:
> > > I have a machine that has an internal card that's a Lifeview DVB and
> > > works fine using the v4l-dvb mercurial sources.
> > >
> > > I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
> > > using the v4l-dvb sources but does work using the v4l-dvb-kernel
> > > version.
> > >
> > > 1. Will the number of em28xx cards supported by v4l-dvb be increased
> > > shortly? (My card id was 94 IIRC ).
> >
> > If it's supported by v4l-dvb-kernel, it's entirely possible, yes.
> >
> > > 2. Can I mix and match from the sources...i.e. can I graft the em28xx
> > > stuff from v4l-dvb-kernel into the v4l-dvb source and compile
> > > successfully or has the underlying code changed at a more strategic
> > > level?
> >
> > Not trivially, since v4l-dvb-kernel contains changes to the core code
> > that the em28xx driver relies on and that are incompatible with
> > changes in the main v4l-dvb repository since. You can try
> > http://www.makomk.com/hg/v4l-dvb-makomk - it's the em28xx and xc3028
> > drivers grafted onto a version of v4l-dvb that's about 5 months old at
> > this point - though it's really not a great starting point for porting
> > them onto newer versions, since you'd want to drop the xc3028 driver
> > in favour of the newer one
> >
>
> Makomk,
> spreading around your even more broken tree won't help anyone.

My tree is not substantially more broken, thank you very much. I think
it has at least one issue that v4l-dvb-kernel/v4l-dvb-experimental did
not (HVR-950 support is rumoured to be broken - probably an issue with
ATSC support in xc3028, which I couldn't test), but it also fixes one
annoying bug (DVB-T only xc3028 based devices didn't work). I hear
rumours that v4l-dvb-kernel also has issues with core changes breaking
the other drivers in the tree, something this shouldn't have.

Also, in case you haven't guesses, the reason I spread my tree around
so much is because I think that it might be helpful to people, either
because they need something that isn't possible with
v4l-dvb-experimental or (in one memorable past case) because you'd
decided to erase all trace of -experimental from your site and I would
actually be able to maintain the -makomk branch (unlike -experimental,
which was hell to work with in places).

> This device already had some issues with the v4l-dvb-kernel tree, this
> is what I'll do in April.
>
> > > 3. Why did the sources branch? Was there a good technical reason for
> > this?
> >
> > Supporting the xc3028 silicon tuner needed some changes to support
> > hybrid analog/digital tuners better. Unfortunately, Markus couldn't
> > come to an agreement with the rest of the developers on how to do it.
> > (I think the main concern were that the changes he were proposing were
> > rather more invasive than they needed to be and risked breaking
> > existing drivers). In the end, someone else coded the equivalent
> > functionality in a more backwards-compatible way and merged it in
> > stages.
> >
> > (It's actually relatively easy to port code from Markus' hybrid tuner
> > framework to the v4l-dvb one, though he will never admit so.)
> >
>
> The reason is my trust is gone I asked in September if it's possible
> to get those devices work with what's available and I got the answer
> it's not.

That's odd; early September was when I started on the v4l-dvb-makomk
branch, which does exactly that. (Admittedly, it does rely on a
slightly evil hack to share info between the analog and digital
support in the xc3028 code, though one of the other devs figured out a
better way of doing it. The xc3028 driver in now v4l-dvb is
suprisingly good; far better than the previous drivers, and rewritten
from scratch.)

Looking at the mailing lists, September was when you were pushing your
userspace drivers idea, which stood a whelk's chance in a supernova of
getting merged. (It (a) didn't do anything that couldn't be done
in-kernel, (b) would make it much easier to release binary
closed-source tuner drivers that only work on specific hardware and
(c) was intentionally created to fork bits of v4l-dvb. Of course, you
PMing me and threating to take your code closed source if anyone
released changed versions - something this would make far, far easier
- probably didn't exactly help, but it was obviously doomed before
then.)

> This stupid fight lasts for more than 2 years already, but I'm the one
> who spent weeks on writing code for getting those things supported and
> even rewrote code although there was no serious participation in the
> discussions I tried to trigger...

The mailing list developed some really nasty atmosphere, and you were
part of the reason. (You probably haven't realised this, but when
professional trolls decide it'd be fun to take your side, you ought to
take a really close look at your behaviour.) I can't remember much of
the details - I think I tried to stay out of it as much as possible.

> If I tell a company that I will add support for something till a given
> date I'll do so to keep up the good contacts. Unfortunately this is
> not how some people at linuxtv behave and it slows down everything
> even for other manufacturers where I'm not involved.
>
> It's me who mostly spent his time on writing any code on mcentral.de,
> the code didn't write itself especially Aidan has no respect about
> that, neither do some other people. Maybe it's really better to
> provide binary only blobs to remember especially such people that it
> requires alot work to get those things work.

Yeah, you did some good coding work (and some not so good, but let's
leave that aside). Unfortunately, IMO you exhausted any residual
goodwill left over from that ages ago, for far too many reasons to go
into. Also, you're forgetting all the other people who contributed
time to testing and debugging your code - including me - as well as
all the pre-existing code that you built on (including the initial
version of em28xx itself).

Still, you did write some good code and do some good RE work, and I'll
fully admit to that - it's why I'm reusing some of it for my modified
drivers. After all, it'd be silly to let your hard work go to waste.
(Admittedly, it's currently mostly down to some trivial code in
em2880-dvb that's probably in "Writing Linux Drivers for USB DVB-T
Devices For Dummies" and some init/modeswitching code that I
practically know by heart, at least in the driver I'm using now, but
I'm sure there's more useful code in there.)

> > > 4. If I can't use the v4l-dvb sources to get my em28xx working what's
> > > the chances of getting the v4l-dvb-kernel stuff working for the
> > > lifeview flydvb card?
> >
> > Not good. Its support for other hardware is, if anything, going to be
> > slowly getting worse over time as other drivers have to be modified or
> > disabled to make it compile on newer kernels.
> >
>
> that for the other repository (em28xx-userspace2/userspace-drivers on
> mcentral.de/hg) is available, although it needs some work with that
> device.

Yeah, that... works, though it's still slightly lacking in both
well-testedness and hardware support, and some of the code makes me
wince.

Anyway, this is starting to get tiresome, so I think I'll leave it
here. This is basically all I have to say on the matter.

Aidan

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

Aidan

So are you working on integrating the em28xx devices that are working
in v4l-dvb-kernel version into v4l-dvb (or ever your own version of
same)?

Or will it require changes to too much code?

I have to say as a user/observer I find it ridiculous that there are
two branches of working code that are pretty close to the same and
won't work with each other.  If there's one area that Linux really
clearly pi**es on Windows it's the handling of media and stuff like
this just switches people off.

While not looking at the code or drawing any conclusions therein a new
layer on top of v4l-dvb (whichever version) seems counter productive
to me.

Ho hum.....can someone please just tell me how to get my kit working
without having to re-invent the wheel.

Thanks in advance.

J

On 01/04/2008, Aidan Thornton <makosoft@googlemail.com> wrote:
> On 3/31/08, Markus Rechberger <mrechberger@gmail.com> wrote:
>  > On 3/31/08, Aidan Thornton <makosoft@googlemail.com> wrote:
>  > > On Mon, Mar 31, 2008 at 12:40 AM, Another Sillyname
>  > > <anothersname@googlemail.com> wrote:
>  > > > I have a machine that has an internal card that's a Lifeview DVB and
>  > > > works fine using the v4l-dvb mercurial sources.
>  > > >
>  > > > I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
>  > > > using the v4l-dvb sources but does work using the v4l-dvb-kernel
>  > > > version.
>  > > >
>  > > > 1. Will the number of em28xx cards supported by v4l-dvb be increased
>  > > > shortly? (My card id was 94 IIRC ).
>  > >
>  > > If it's supported by v4l-dvb-kernel, it's entirely possible, yes.
>  > >
>  > > > 2. Can I mix and match from the sources...i.e. can I graft the em28xx
>  > > > stuff from v4l-dvb-kernel into the v4l-dvb source and compile
>  > > > successfully or has the underlying code changed at a more strategic
>  > > > level?
>  > >
>  > > Not trivially, since v4l-dvb-kernel contains changes to the core code
>  > > that the em28xx driver relies on and that are incompatible with
>  > > changes in the main v4l-dvb repository since. You can try
>  > > http://www.makomk.com/hg/v4l-dvb-makomk - it's the em28xx and xc3028
>  > > drivers grafted onto a version of v4l-dvb that's about 5 months old at
>  > > this point - though it's really not a great starting point for porting
>  > > them onto newer versions, since you'd want to drop the xc3028 driver
>  > > in favour of the newer one
>  > >
>  >
>  > Makomk,
>  > spreading around your even more broken tree won't help anyone.
>
>
> My tree is not substantially more broken, thank you very much. I think
>  it has at least one issue that v4l-dvb-kernel/v4l-dvb-experimental did
>  not (HVR-950 support is rumoured to be broken - probably an issue with
>  ATSC support in xc3028, which I couldn't test), but it also fixes one
>  annoying bug (DVB-T only xc3028 based devices didn't work). I hear
>  rumours that v4l-dvb-kernel also has issues with core changes breaking
>  the other drivers in the tree, something this shouldn't have.
>
>  Also, in case you haven't guesses, the reason I spread my tree around
>  so much is because I think that it might be helpful to people, either
>  because they need something that isn't possible with
>  v4l-dvb-experimental or (in one memorable past case) because you'd
>  decided to erase all trace of -experimental from your site and I would
>  actually be able to maintain the -makomk branch (unlike -experimental,
>  which was hell to work with in places).
>
>
>  > This device already had some issues with the v4l-dvb-kernel tree, this
>  > is what I'll do in April.
>  >
>  > > > 3. Why did the sources branch? Was there a good technical reason for
>  > > this?
>  > >
>  > > Supporting the xc3028 silicon tuner needed some changes to support
>  > > hybrid analog/digital tuners better. Unfortunately, Markus couldn't
>  > > come to an agreement with the rest of the developers on how to do it.
>  > > (I think the main concern were that the changes he were proposing were
>  > > rather more invasive than they needed to be and risked breaking
>  > > existing drivers). In the end, someone else coded the equivalent
>  > > functionality in a more backwards-compatible way and merged it in
>  > > stages.
>  > >
>  > > (It's actually relatively easy to port code from Markus' hybrid tuner
>  > > framework to the v4l-dvb one, though he will never admit so.)
>  > >
>  >
>  > The reason is my trust is gone I asked in September if it's possible
>  > to get those devices work with what's available and I got the answer
>  > it's not.
>
>
> That's odd; early September was when I started on the v4l-dvb-makomk
>  branch, which does exactly that. (Admittedly, it does rely on a
>  slightly evil hack to share info between the analog and digital
>  support in the xc3028 code, though one of the other devs figured out a
>  better way of doing it. The xc3028 driver in now v4l-dvb is
>  suprisingly good; far better than the previous drivers, and rewritten
>  from scratch.)
>
>  Looking at the mailing lists, September was when you were pushing your
>  userspace drivers idea, which stood a whelk's chance in a supernova of
>  getting merged. (It (a) didn't do anything that couldn't be done
>  in-kernel, (b) would make it much easier to release binary
>  closed-source tuner drivers that only work on specific hardware and
>  (c) was intentionally created to fork bits of v4l-dvb. Of course, you
>  PMing me and threating to take your code closed source if anyone
>  released changed versions - something this would make far, far easier
>  - probably didn't exactly help, but it was obviously doomed before
>  then.)
>
>
>  > This stupid fight lasts for more than 2 years already, but I'm the one
>  > who spent weeks on writing code for getting those things supported and
>  > even rewrote code although there was no serious participation in the
>  > discussions I tried to trigger...
>
>
> The mailing list developed some really nasty atmosphere, and you were
>  part of the reason. (You probably haven't realised this, but when
>  professional trolls decide it'd be fun to take your side, you ought to
>  take a really close look at your behaviour.) I can't remember much of
>  the details - I think I tried to stay out of it as much as possible.
>
>
>  > If I tell a company that I will add support for something till a given
>  > date I'll do so to keep up the good contacts. Unfortunately this is
>  > not how some people at linuxtv behave and it slows down everything
>  > even for other manufacturers where I'm not involved.
>  >
>  > It's me who mostly spent his time on writing any code on mcentral.de,
>  > the code didn't write itself especially Aidan has no respect about
>  > that, neither do some other people. Maybe it's really better to
>  > provide binary only blobs to remember especially such people that it
>  > requires alot work to get those things work.
>
>
> Yeah, you did some good coding work (and some not so good, but let's
>  leave that aside). Unfortunately, IMO you exhausted any residual
>  goodwill left over from that ages ago, for far too many reasons to go
>  into. Also, you're forgetting all the other people who contributed
>  time to testing and debugging your code - including me - as well as
>  all the pre-existing code that you built on (including the initial
>  version of em28xx itself).
>
>  Still, you did write some good code and do some good RE work, and I'll
>  fully admit to that - it's why I'm reusing some of it for my modified
>  drivers. After all, it'd be silly to let your hard work go to waste.
>  (Admittedly, it's currently mostly down to some trivial code in
>  em2880-dvb that's probably in "Writing Linux Drivers for USB DVB-T
>  Devices For Dummies" and some init/modeswitching code that I
>  practically know by heart, at least in the driver I'm using now, but
>  I'm sure there's more useful code in there.)
>
>
>  > > > 4. If I can't use the v4l-dvb sources to get my em28xx working what's
>  > > > the chances of getting the v4l-dvb-kernel stuff working for the
>  > > > lifeview flydvb card?
>  > >
>  > > Not good. Its support for other hardware is, if anything, going to be
>  > > slowly getting worse over time as other drivers have to be modified or
>  > > disabled to make it compile on newer kernels.
>  > >
>  >
>  > that for the other repository (em28xx-userspace2/userspace-drivers on
>  > mcentral.de/hg) is available, although it needs some work with that
>  > device.
>
>
> Yeah, that... works, though it's still slightly lacking in both
>  well-testedness and hardware support, and some of the code makes me
>  wince.
>
>  Anyway, this is starting to get tiresome, so I think I'll leave it
>  here. This is basically all I have to say on the matter.
>
>
>  Aidan
>

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[hermann pitton]

Hi,

Am Mittwoch, den 02.04.2008, 00:41 +0100 schrieb Another Sillyname:
> Aidan
> 
> So are you working on integrating the em28xx devices that are working
> in v4l-dvb-kernel version into v4l-dvb (or ever your own version of
> same)?
> 
> Or will it require changes to too much code?
> 
> I have to say as a user/observer I find it ridiculous that there are
> two branches of working code that are pretty close to the same and
> won't work with each other.  If there's one area that Linux really
> clearly pi**es on Windows it's the handling of media and stuff like
> this just switches people off.
> 
> While not looking at the code or drawing any conclusions therein a new
> layer on top of v4l-dvb (whichever version) seems counter productive
> to me.
> 
> Ho hum.....can someone please just tell me how to get my kit working
> without having to re-invent the wheel.
> 
> Thanks in advance.
> 
> J
> 

did not look up what Markus currently has, but as a interim solution,
did you try modprobe/options saa7134 card=94 for the LifeView DVB-T?

Basically we have support for such kind of cards since longer, should
not be that difficult to get in in as a workaround for now.

Cheers,
Hermann





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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[hermann pitton]

Am Dienstag, den 01.04.2008, 22:06 +0100 schrieb Aidan Thornton:
> On 3/31/08, Markus Rechberger <mrechberger@gmail.com> wrote:
> > On 3/31/08, Aidan Thornton <makosoft@googlemail.com> wrote:
> > > On Mon, Mar 31, 2008 at 12:40 AM, Another Sillyname
> > > <anothersname@googlemail.com> wrote:
> > > > I have a machine that has an internal card that's a Lifeview DVB and
> > > > works fine using the v4l-dvb mercurial sources.
> > > >
> > > > I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
> > > > using the v4l-dvb sources but does work using the v4l-dvb-kernel
> > > > version.
> > > >
> > > > 1. Will the number of em28xx cards supported by v4l-dvb be increased
> > > > shortly? (My card id was 94 IIRC ).
> > >
> > > If it's supported by v4l-dvb-kernel, it's entirely possible, yes.
> > >
> > > > 2. Can I mix and match from the sources...i.e. can I graft the em28xx
> > > > stuff from v4l-dvb-kernel into the v4l-dvb source and compile
> > > > successfully or has the underlying code changed at a more strategic
> > > > level?
> > >
> > > Not trivially, since v4l-dvb-kernel contains changes to the core code
> > > that the em28xx driver relies on and that are incompatible with
> > > changes in the main v4l-dvb repository since. You can try
> > > http://www.makomk.com/hg/v4l-dvb-makomk - it's the em28xx and xc3028
> > > drivers grafted onto a version of v4l-dvb that's about 5 months old at
> > > this point - though it's really not a great starting point for porting
> > > them onto newer versions, since you'd want to drop the xc3028 driver
> > > in favour of the newer one
> > >
> >
> > Makomk,
> > spreading around your even more broken tree won't help anyone.
> 
> My tree is not substantially more broken, thank you very much. I think
> it has at least one issue that v4l-dvb-kernel/v4l-dvb-experimental did
> not (HVR-950 support is rumoured to be broken - probably an issue with
> ATSC support in xc3028, which I couldn't test), but it also fixes one
> annoying bug (DVB-T only xc3028 based devices didn't work). I hear
> rumours that v4l-dvb-kernel also has issues with core changes breaking
> the other drivers in the tree, something this shouldn't have.
> 
> Also, in case you haven't guesses, the reason I spread my tree around
> so much is because I think that it might be helpful to people, either
> because they need something that isn't possible with
> v4l-dvb-experimental or (in one memorable past case) because you'd
> decided to erase all trace of -experimental from your site and I would
> actually be able to maintain the -makomk branch (unlike -experimental,
> which was hell to work with in places).
> 
> > This device already had some issues with the v4l-dvb-kernel tree, this
> > is what I'll do in April.
> >
> > > > 3. Why did the sources branch? Was there a good technical reason for
> > > this?
> > >
> > > Supporting the xc3028 silicon tuner needed some changes to support
> > > hybrid analog/digital tuners better. Unfortunately, Markus couldn't
> > > come to an agreement with the rest of the developers on how to do it.
> > > (I think the main concern were that the changes he were proposing were
> > > rather more invasive than they needed to be and risked breaking
> > > existing drivers). In the end, someone else coded the equivalent
> > > functionality in a more backwards-compatible way and merged it in
> > > stages.
> > >
> > > (It's actually relatively easy to port code from Markus' hybrid tuner
> > > framework to the v4l-dvb one, though he will never admit so.)
> > >
> >
> > The reason is my trust is gone I asked in September if it's possible
> > to get those devices work with what's available and I got the answer
> > it's not.
> 
> That's odd; early September was when I started on the v4l-dvb-makomk
> branch, which does exactly that. (Admittedly, it does rely on a
> slightly evil hack to share info between the analog and digital
> support in the xc3028 code, though one of the other devs figured out a
> better way of doing it. The xc3028 driver in now v4l-dvb is
> suprisingly good; far better than the previous drivers, and rewritten
> from scratch.)
> 
> Looking at the mailing lists, September was when you were pushing your
> userspace drivers idea, which stood a whelk's chance in a supernova of
> getting merged. (It (a) didn't do anything that couldn't be done
> in-kernel, (b) would make it much easier to release binary
> closed-source tuner drivers that only work on specific hardware and
> (c) was intentionally created to fork bits of v4l-dvb. Of course, you
> PMing me and threating to take your code closed source if anyone
> released changed versions - something this would make far, far easier
> - probably didn't exactly help, but it was obviously doomed before
> then.)
> 
> > This stupid fight lasts for more than 2 years already, but I'm the one
> > who spent weeks on writing code for getting those things supported and
> > even rewrote code although there was no serious participation in the
> > discussions I tried to trigger...
> 
> The mailing list developed some really nasty atmosphere, and you were
> part of the reason. (You probably haven't realised this, but when
> professional trolls decide it'd be fun to take your side, you ought to
> take a really close look at your behaviour.) I can't remember much of
> the details - I think I tried to stay out of it as much as possible.
> 
> > If I tell a company that I will add support for something till a given
> > date I'll do so to keep up the good contacts. Unfortunately this is
> > not how some people at linuxtv behave and it slows down everything
> > even for other manufacturers where I'm not involved.
> >
> > It's me who mostly spent his time on writing any code on mcentral.de,
> > the code didn't write itself especially Aidan has no respect about
> > that, neither do some other people. Maybe it's really better to
> > provide binary only blobs to remember especially such people that it
> > requires alot work to get those things work.
> 
> Yeah, you did some good coding work (and some not so good, but let's
> leave that aside). Unfortunately, IMO you exhausted any residual
> goodwill left over from that ages ago, for far too many reasons to go
> into. Also, you're forgetting all the other people who contributed
> time to testing and debugging your code - including me - as well as
> all the pre-existing code that you built on (including the initial
> version of em28xx itself).
> 
> Still, you did write some good code and do some good RE work, and I'll
> fully admit to that - it's why I'm reusing some of it for my modified
> drivers. After all, it'd be silly to let your hard work go to waste.
> (Admittedly, it's currently mostly down to some trivial code in
> em2880-dvb that's probably in "Writing Linux Drivers for USB DVB-T
> Devices For Dummies" and some init/modeswitching code that I
> practically know by heart, at least in the driver I'm using now, but
> I'm sure there's more useful code in there.)
> 
> > > > 4. If I can't use the v4l-dvb sources to get my em28xx working what's
> > > > the chances of getting the v4l-dvb-kernel stuff working for the
> > > > lifeview flydvb card?
> > >
> > > Not good. Its support for other hardware is, if anything, going to be
> > > slowly getting worse over time as other drivers have to be modified or
> > > disabled to make it compile on newer kernels.
> > >
> >
> > that for the other repository (em28xx-userspace2/userspace-drivers on
> > mcentral.de/hg) is available, although it needs some work with that
> > device.
> 
> Yeah, that... works, though it's still slightly lacking in both
> well-testedness and hardware support, and some of the code makes me
> wince.
> 
> Anyway, this is starting to get tiresome, so I think I'll leave it
> here. This is basically all I have to say on the matter.
> 
> Aidan


Hi Aidan,

nice story, but we might have it all slightly different.

Better stop to believe in that "professional troll" myth, on my list I
still count up to only one ;)

It was about exclusive contacts to manufacturers and data sheets
_previously_, before Markus, and who is allowed and who not.

The "who rules by the sword, must die by the sword" was only a not so
nice side effect, if you even noticed.

Nobody can come with crocodile tears in the eyes later on, if _by will_
are no sufficient rules in the jungle.

Major stuff is taken into the kernel, for which often only one single
developer has the NDA with the details and manufacturer contacts for,
stressing generations of users and testers.

Since Markus and all who helped did really hack this from bare bones
with lot of work, maybe now slightly coming into a better position, and
after even offering to take v4l-dvb all over if needed ;), if his
patches don't go in finally, unfortunately with a much to narrow time
frame, 24 hours, which was a impossible to resolve ultimatum, it went
like it did and I don't wonder ... 

Cheers,
Hermann







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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Aidan Thornton]

On 4/2/08, Another Sillyname <anothersname@googlemail.com> wrote:
> Aidan
>
> So are you working on integrating the em28xx devices that are working
> in v4l-dvb-kernel version into v4l-dvb (or ever your own version of
> same)?
>
> Or will it require changes to too much code?

Occasionally, yes - I can do, and generally it's fairly trivial, but
since I don't have access to all this hardware myself, unless
someone's willing to test it there's not much I can do. In fact, I
just added untested support for the card to
http://www.makomk.com/hg/v4l-dvb-em28xx. You'll need to "modprobe
em28xx card=17", though, since your device uses a generic USB ID and I
can't add autodetection without a copy of the dmesg output when
loading the driver without card=17. (Also, while my version of the
driver should in theory support DVB-T, the v4l-dvb version doesn't and
probably won't any time soon.)

> I have to say as a user/observer I find it ridiculous that there are
> two branches of working code that are pretty close to the same and
> won't work with each other.  If there's one area that Linux really
> clearly pi**es on Windows it's the handling of media and stuff like
> this just switches people off.
>
> While not looking at the code or drawing any conclusions therein a new
> layer on top of v4l-dvb (whichever version) seems counter productive
> to me.
>
> Ho hum.....can someone please just tell me how to get my kit working
> without having to re-invent the wheel.

Also, you might be able to get it working with v4l-dvb-experimental by
passing "card=94" to saa7134. No guarantees, though.

> Thanks in advance.
>
> J
>
> On 01/04/2008, Aidan Thornton <makosoft@googlemail.com> wrote:

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]

Hi Aidan

I've played around with this for a few hours now and we have moved
forward but not quite working yet.....

The card is getting loaded properly (when I use the appropriate
card=17 option) however loading the em2880-dvb module then borks.....

I've attached the edited dmesg file.....any ideas?

Thanks

J

On 02/04/2008, Aidan Thornton <makosoft@googlemail.com> wrote:
> On 4/2/08, Another Sillyname <anothersname@googlemail.com> wrote:
>  > Aidan
>  >
>  > So are you working on integrating the em28xx devices that are working
>  > in v4l-dvb-kernel version into v4l-dvb (or ever your own version of
>  > same)?
>  >
>  > Or will it require changes to too much code?
>
>
> Occasionally, yes - I can do, and generally it's fairly trivial, but
>  since I don't have access to all this hardware myself, unless
>  someone's willing to test it there's not much I can do. In fact, I
>  just added untested support for the card to
>  http://www.makomk.com/hg/v4l-dvb-em28xx. You'll need to "modprobe
>  em28xx card=17", though, since your device uses a generic USB ID and I
>  can't add autodetection without a copy of the dmesg output when
>  loading the driver without card=17. (Also, while my version of the
>  driver should in theory support DVB-T, the v4l-dvb version doesn't and
>  probably won't any time soon.)
>
>
>  > I have to say as a user/observer I find it ridiculous that there are
>  > two branches of working code that are pretty close to the same and
>  > won't work with each other.  If there's one area that Linux really
>  > clearly pi**es on Windows it's the handling of media and stuff like
>  > this just switches people off.
>  >
>  > While not looking at the code or drawing any conclusions therein a new
>  > layer on top of v4l-dvb (whichever version) seems counter productive
>  > to me.
>  >
>  > Ho hum.....can someone please just tell me how to get my kit working
>  > without having to re-invent the wheel.
>
>
> Also, you might be able to get it working with v4l-dvb-experimental by
>  passing "card=94" to saa7134. No guarantees, though.
>
>
>  > Thanks in advance.
>  >
>  > J
>  >
>  > On 01/04/2008, Aidan Thornton <makosoft@googlemail.com> wrote:
>

[-- Attachment #2: dmesg28xxnotworking --]
[-- Type: application/octet-stream, Size: 7384 bytes --]

Linux video capture interface: v2.00
em28xx v4l2 driver version 0.1.0 loaded
em28xx new video device (eb1a:2881): interface 0, class 255
em28xx Has usb audio class
em28xx #0: Alternate settings: 8
em28xx #0: Alternate setting 0, max size= 0
em28xx #0: Alternate setting 1, max size= 0
em28xx #0: Alternate setting 2, max size= 1448
em28xx #0: Alternate setting 3, max size= 2048
em28xx #0: Alternate setting 4, max size= 2304
em28xx #0: Alternate setting 5, max size= 2580
em28xx #0: Alternate setting 6, max size= 2892
em28xx #0: Alternate setting 7, max size= 3072
em28xx #0: em28xx chip ID = 36
saa7130/34: v4l2 driver version 0.2.14 loaded
ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 19 (level, low) -> IRQ 19
ACPI: PCI Interrupt 0000:00:1b.0[A] -> <6>saa7133[0]: found at 0000:03:03.0, rev: 209, irq: 19, latency: 64, mmio: 0xfe8ff800
saa7133[0]: subsystem: 5168:3307, board: LifeView FlyDVB-T Hybrid Cardbus/MSI TV @nywhere A/D NB [card=94,autodetected]
saa7133[0]: board init: gpio is 10000
PCI: Setting latency timer of device 0000:00:1b.0 to 64
ALSA sound/pci/hda/hda_intel.c:732: codec_mask = 0x3
hda_codec: Unknown model for ALC880, trying auto-probe from BIOS...
ALSA sound/pci/hda/hda_codec.c:2757: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:2761:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:2765:    hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:2773:    inputs: mic=0x18, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0
em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 81 28 58 12 5c 00 6a 20 6a 00
em28xx #0: i2c eeprom 10: 00 00 04 57 64 57 00 00 60 f4 00 00 02 02 00 00
em28xx #0: i2c eeprom 20: 56 00 01 00 00 00 02 00 b8 00 00 00 5b 1e 00 00
em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 10 02 00 00 00 00 00 00
em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 20 03 55 00 53 00
em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 38 00 31 00 20 00 56 00
em28xx #0: i2c eeprom 80: 69 00 64 00 65 00 6f 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom e0: 5a 00 55 aa 79 55 54 03 00 17 98 01 00 00 00 00
em28xx #0: i2c eeprom f0: 0c 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00
EEPROM ID= 0x9567eb1a, hash = 0xb8846b20
Vendor/Product ID= eb1a:2881
AC97 audio (5 sample rates)
USB Remote wakeup capable
500mA max power
Table at 0x04, strings=0x206a, 0x006a, 0x0000
saa7133[0]: i2c eeprom 00: 68 51 07 33 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: 00 00 62 08 ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 03 03 01 01 03 08 ff 01 17 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 05 00 01 16 22 15 ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
tuner' 2-004b: chip found @ 0x96 (saa7133[0])
tda829x 2-004b: setting tuner address to 61
tda829x 2-004b: type set to tda8290+75a
firewire_core: created device fw0: GUID 00000ae6ff5a577d, S400
tvp5150 1-005c: tvp5150am1 detected.
em28xx #0: V4L2 device registered as /dev/video0 and /dev/vbi0
em28xx #0: Found Pinnacle Hybrid Pro (EM2881)
em28xx audio device (eb1a:2881): interface 1, class 1
em28xx audio device (eb1a:2881): interface 2, class 1
usbcore: registered new interface driver em28xx
ALSA sound/usb/usbaudio.c:2753: 5:2:1: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 5:2:2: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 5:2:3: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 5:2:4: add audio endpoint 0x83
ALSA sound/usb/usbaudio.c:2753: 5:2:5: add audio endpoint 0x83
ALSA sound/usb/usbmixer.c:989: [2] FU [PCM Capture Switch] ch = 1, val = 0/1/1
ALSA sound/usb/usbmixer.c:406: cannot set ctl value: req = 0x4, wValue = 0x200, wIndex = 0x201, type = 4, data = 0x0/0x1
ALSA sound/usb/usbmixer.c:989: [2] FU [PCM Capture Volume] ch = 1, val = 0/0/512
usbcore: registered new interface driver snd-usb-audio
saa7133[0]: registered device video1 [v4l2]
saa7133[0]: registered device vbi1
saa7133[0]: registered device radio0
DVB: registering new adapter (saa7133[0])
DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
tda1004x: setting up plls for 48MHz sampling clock
SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
tda1004x: found firmware revision 29 -- ok
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ALSA sound/usb/usbaudio.c:1327: setting usb interface 2:5
ALSA sound/usb/usbaudio.c:1327: setting usb interface 2:2
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
ADDRCONF(NETDEV_UP): wlan0: link is not ready
[drm] Initialized drm 1.1.0 20060810
PCI: Setting latency timer of device 0000:00:02.0 to 64
[drm] Initialized i915 1.6.0 20060119 on minor 0
ALSA sound/usb/usbaudio.c:1327: setting usb interface 2:2
em2880-dvb.c: DVB Init
em28xx_acquire: acquired, mode = 3
zl10353_read_register: readreg error (reg=127, ret==-19)
em2880-dvb.c: failed initializing zl10353 DVB-T demodulator
em2880-dvb.c: retrying with mt352 DVB-T demodulator
mt352_read_register: readreg error (reg=127, ret==-19)
em2880-dvb.c: no luck with mt352 demodulator, not attaching em2880-dvb
em2880-dvb.c: DVB-T demodulator not reachable, giving up
em28xx_release: released, mode = 3
Em28xx: Initialized (Em2880 DVB Extension) extension
em28xx_acquire: acquired, mode = 2
tvp5150 1-005c: tvp5150am1 detected.
em28xx_release: released, mode = 2
em28xx_acquire: acquired, mode = 2
em28xx_release: released, mode = 2
em28xx_acquire: acquired, mode = 2
em28xx_release: released, mode = 2
em28xx_acquire: acquired, mode = 2
em28xx_release: released, mode = 2
em28xx_acquire: acquired, mode = 2
em28xx_release: released, mode = 2
em28xx_acquire: acquired, mode = 2
em28xx_release: released, mode = 2
em28xx_acquire: acquired, mode = 2
em28xx_release: released, mode = 2
em28xx_acquire: acquired, mode = 2
em28xx_release: released, mode = 2
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: found firmware revision 29 -- ok

[-- Attachment #3: Type: text/plain, Size: 150 bytes --]

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Aidan Thornton]

On 4/3/08, Another Sillyname <anothersname@googlemail.com> wrote:
> Hi Aidan
>
> I've played around with this for a few hours now and we have moved
> forward but not quite working yet.....
>
> The card is getting loaded properly (when I use the appropriate
> card=17 option) however loading the em2880-dvb module then borks.....
>
> I've attached the edited dmesg file.....any ideas?
>
> Thanks
>
> J

Hi,

Sorry about that - I forgot to copy over a couple of extra GPIO writes
needed to switch the device to DVB-T mode. (I knew some devices needed
them, I'd just forgotten about it and didn't think to check). Try
again now.

Aidan

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

Aidan

That seems to have done it thanks.....I'm still getting a couple of
issues with mythtv but I think these are cardid tweaks I need to do.

Thanks for the help much appreciated and I'll let you know when it's
100% stable.

J

On 03/04/2008, Aidan Thornton <makosoft@googlemail.com> wrote:
> On 4/3/08, Another Sillyname <anothersname@googlemail.com> wrote:
>  > Hi Aidan
>  >
>  > I've played around with this for a few hours now and we have moved
>  > forward but not quite working yet.....
>  >
>  > The card is getting loaded properly (when I use the appropriate
>  > card=17 option) however loading the em2880-dvb module then borks.....
>  >
>  > I've attached the edited dmesg file.....any ideas?
>  >
>  > Thanks
>  >
>  > J
>
>
> Hi,
>
>  Sorry about that - I forgot to copy over a couple of extra GPIO writes
>  needed to switch the device to DVB-T mode. (I knew some devices needed
>  them, I'd just forgotten about it and didn't think to check). Try
>  again now.
>
>
>  Aidan
>

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Another Sillyname]

Aidan

Just to let you know that after tweaking around I've managed to get it
working stable.  I had to add a sleep in modprobe.conf else the
em2880-dvb module was trying to load before em28xx had 'settled'.

Just in case you see the problem in the future I added this to my
modprobe.conf file to fix the problem.....

install em28xx /sbin/modprobe --ignore-install em28xx; /bin/sleep 2;
/sbin/modprobe em2880-dvb

I've been reading that once 2.6.25 kernel is released there will be a
lot more support for the em28 products....hopefully it'll reduce some
of these issues going forward.

Best Regards and once again thanks for your help.

J

On 03/04/2008, Aidan Thornton <makosoft@googlemail.com> wrote:
> On 4/3/08, Another Sillyname <anothersname@googlemail.com> wrote:
>  > Hi Aidan
>  >
>  > I've played around with this for a few hours now and we have moved
>  > forward but not quite working yet.....
>  >
>  > The card is getting loaded properly (when I use the appropriate
>  > card=17 option) however loading the em2880-dvb module then borks.....
>  >
>  > I've attached the edited dmesg file.....any ideas?
>  >
>  > Thanks
>  >
>  > J
>
>
> Hi,
>
>  Sorry about that - I forgot to copy over a couple of extra GPIO writes
>  needed to switch the device to DVB-T mode. (I knew some devices needed
>  them, I'd just forgotten about it and didn't think to check). Try
>  again now.
>
>
>  Aidan
>

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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Simon Kenyon]

On Mon, 2008-03-31 at 21:02 +0100, Aidan Thornton wrote:
> Not trivially, since v4l-dvb-kernel contains changes to the core code
> that the em28xx driver relies on and that are incompatible with
> changes in the main v4l-dvb repository since. You can try
> http://www.makomk.com/hg/v4l-dvb-makomk - it's the em28xx and xc3028
> drivers grafted onto a version of v4l-dvb that's about 5 months old at
> this point - though it's really not a great starting point for porting
> them onto newer versions, since you'd want to drop the xc3028 driver
> in favour of the newer one

thanks for making that work with 2.6.24
works for my terratec cinergy xs device

regards
--
simon
PS output included for the record

usb 1-1: new high speed USB device using ehci_hcd and address 4
usb 1-1: configuration #1 chosen from 1 choice
Linux video capture interface: v2.00
em28xx v4l2 driver version 0.0.1 loaded
em28xx new video device (0ccd:0042): interface 0, class 255
em28xx: device is attached to a USB 2.0 bus
em28xx: you're using the experimental/unstable tree from mcentral.de
em28xx: there's also a stable tree available but which is limited to
em28xx: linux <=2.6.19.2
em28xx: it's fine to use this driver but keep in mind that it will move
em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's
em28xx: proved to be stable
em28xx #0: Alternate settings: 8
em28xx #0: Alternate setting 0, max size= 0
em28xx #0: Alternate setting 1, max size= 0
em28xx #0: Alternate setting 2, max size= 1448
em28xx #0: Alternate setting 3, max size= 2048
em28xx #0: Alternate setting 4, max size= 2304
em28xx #0: Alternate setting 5, max size= 2580
em28xx #0: Alternate setting 6, max size= 2892
em28xx #0: Alternate setting 7, max size= 3072
Picked tuner type 71
input: em2880/em2870 remote control as /class/input/input6
em28xx-input.c: remote control handler attached
attach_inform: eeprom detected.
em28xx #0: i2c eeprom 00: 1a eb 67 95 cd 0c 42 00 50 12 5c 03 6a 32 9c
34
em28xx #0: i2c eeprom 10: 00 00 06 57 46 07 00 00 00 00 00 00 00 00 00
00
em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10 31 00 b8 00 14 00 5b 00 00
00
em28xx #0: i2c eeprom 30: 00 00 20 40 20 6e 02 20 10 01 00 00 00 00 00
00
em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 32 03 43 00 69
00
em28xx #0: i2c eeprom 70: 6e 00 65 00 72 00 67 00 79 00 20 00 48 00 79
00
em28xx #0: i2c eeprom 80: 62 00 72 00 69 00 64 00 20 00 54 00 20 00 55
00
em28xx #0: i2c eeprom 90: 53 00 42 00 20 00 58 00 53 00 00 00 34 03 54
00
em28xx #0: i2c eeprom a0: 65 00 72 00 72 00 61 00 54 00 65 00 63 00 20
00
em28xx #0: i2c eeprom b0: 45 00 6c 00 65 00 63 00 74 00 72 00 6f 00 6e
00
em28xx #0: i2c eeprom c0: 69 00 63 00 20 00 47 00 6d 00 62 00 48 00 00
00
em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
EEPROM ID= 0x9567eb1a
Vendor/Product ID= 0ccd:0042
AC97 audio (5 sample rates)
500mA max power
Table at 0x06, strings=0x326a, 0x349c, 0x0000
tuner 4-0061: chip found @ 0xc2 (em28xx #0)
attach inform (default): detected I2C address c2
/opt/v4l-dvb-makomk/v4l/xc3028.c: attach request!
tuner 4-0061: type set to XC3028
/opt/v4l-dvb-makomk/v4l/xc3028.c: attach request!
tuner 4-0061: type set to XC3028
attach_inform: tvp5150 detected.
tvp5150 4-005c: tvp5150am1 detected.
xc3208: DEBUG freq=9076 mode=2 audmode=1 std=0
xc3028 debug: XC3028_GET_MODE returned 0
ANALOG TV REQUEST
Loading base firmware: xc3028_init0.i2c.fw
upload_firmware_new, Loading default analogue TV settings:
xc3028_BG_PAL_A2_A.i                                            2c.fw
xc3028-tuner.c: firmware 2.7
em28xx #0: V4L2 VBI device registered as /dev/vbi0
em28xx #0: V4L2 device registered as /dev/video0
em28xx #0: Found Terratec Hybrid XS
em28xx audio device (0ccd:0042): interface 1, class 1
em28xx audio device (0ccd:0042): interface 2, class 1
usbcore: registered new interface driver em28xx
em2880-dvb.c: DVB Init
em28xx_acquire: acquired, mode = 3
/opt/v4l-dvb-makomk/v4l/xc3028.c: attach request!
DVB: registering new adapter (em2880 DVB-T)
DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
em28xx_release: released, mode = 3
Em28xx: Initialized (Em2880 DVB Extension) extension



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

Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help

[Aidan Thornton]

[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]

On 4/4/08, Another Sillyname <anothersname@googlemail.com> wrote:
> Aidan
>
> Just to let you know that after tweaking around I've managed to get it
> working stable.  I had to add a sleep in modprobe.conf else the
> em2880-dvb module was trying to load before em28xx had 'settled'.
>
> Just in case you see the problem in the future I added this to my
> modprobe.conf file to fix the problem.....
>
> install em28xx /sbin/modprobe --ignore-install em28xx; /bin/sleep 2;
> /sbin/modprobe em2880-dvb

That really shouldn't happen. What problems were you seeing, exactly?

> I've been reading that once 2.6.25 kernel is released there will be a
> lot more support for the em28 products....hopefully it'll reduce some
> of these issues going forward.

The 2.6.25 code is basically just a slightly older version of v4l-dvb
upstream - it adds (analog only) support for a few devices. While
hopefully analog support for this device should at least make 2.6.26
as long as I get a patch tested and submitted on time, I don't expect
DVB-T support for any em28xx-based device will. Perhaps for 2.6.27,
perhaps not.

(By the way, if it's not too much hassle, could you check if the
attached patch against  http://linuxtv.org/hg/v4l-dvb works for
analog, especially that the device works correctly after being freshly
plugged in and that sound works? It shouldn't need the card= option,
and neither should the latest http://www.makomk.com/hg/v4l-dvb-em28xx.
If you do test the patch, be careful not to load em2880-dvb - it's not
compatible and you won't be able to unload it short of rebooting.)

> Best Regards and once again thanks for your help.
>
> J

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: em28xx-pinnacle-hybrid-pro-support.patch --]
[-- Type: text/x-patch; name=em28xx-pinnacle-hybrid-pro-support.patch, Size: 2945 bytes --]

diff -r 37d5a01a14ca linux/Documentation/video4linux/CARDLIST.em28xx
--- a/linux/Documentation/video4linux/CARDLIST.em28xx	Wed Apr 02 11:10:59 2008 -0700
+++ b/linux/Documentation/video4linux/CARDLIST.em28xx	Fri Apr 04 17:04:07 2008 +0100
@@ -15,3 +15,4 @@
  14 -> Pixelview Prolink PlayTV USB 2.0         (em2820/em2840)
  15 -> V-Gear PocketTV                          (em2800)
  16 -> Hauppauge WinTV HVR 950                  (em2880)        [2040:6513]
+ 17 -> Pinnacle Hybrid Pro (EM2881)             (em2881)
diff -r 37d5a01a14ca linux/drivers/media/video/em28xx/em28xx-cards.c
--- a/linux/drivers/media/video/em28xx/em28xx-cards.c	Wed Apr 02 11:10:59 2008 -0700
+++ b/linux/drivers/media/video/em28xx/em28xx-cards.c	Fri Apr 04 17:04:07 2008 +0100
@@ -72,6 +72,7 @@
 #define EM2820_BOARD_PROLINK_PLAYTV_USB2	14
 #define EM2800_BOARD_VGEAR_POCKETTV             15
 #define EM2880_BOARD_HAUPPAUGE_WINTV_HVR_950	16
+#define EM2881_BOARD_PINNACLE_HYBRID_PRO	17
 
 struct em28xx_board em28xx_boards[] = {
 	[EM2800_BOARD_UNKNOWN] = {
@@ -405,6 +406,27 @@
 			.amux     = EM28XX_AMUX_LINE_IN,
 		} },
 	},
+	[EM2881_BOARD_PINNACLE_HYBRID_PRO] = {
+		.name         = "Pinnacle Hybrid Pro (EM2881)",
+		.vchannels    = 3,
+		.tuner_type   = TUNER_XC2028,
+		.mts_firmware = 1,
+		.decoder      = EM28XX_TVP5150,
+		.input          = { {
+			.type     = EM28XX_VMUX_TELEVISION,
+			.vmux     = TVP5150_COMPOSITE0,
+			.amux     = 0,
+		}, {
+			.type     = EM28XX_VMUX_COMPOSITE1,
+			.vmux     = TVP5150_COMPOSITE1,
+			.amux     = 1,
+		}, {
+			.type     = EM28XX_VMUX_SVIDEO,
+			.vmux     = TVP5150_SVIDEO,
+			.amux     = 1,
+		} },
+		.analog_gpio = 0x08007d6d,
+	},
 };
 const unsigned int em28xx_bcount = ARRAY_SIZE(em28xx_boards);
 
@@ -458,6 +480,7 @@
 static struct em28xx_hash_table em28xx_eeprom_hash [] = {
 	/* P/N: SA 60002070465 Tuner: TVF7533-MF */
 	{0x6ce05a8f, EM2820_BOARD_PROLINK_PLAYTV_USB2, TUNER_YMEC_TVF_5533MF},
+	{0xb8846b20, EM2881_BOARD_PINNACLE_HYBRID_PRO, TUNER_XC2028},
 };
 
 /* I2C devicelist hash table for devices with generic USB IDs */
@@ -743,6 +766,30 @@
 #endif
 		break;
 	}
+	case EM2881_BOARD_PINNACLE_HYBRID_PRO:
+	{
+		em28xx_write_regs(dev, I2C_CLK_REG, "\x4c", 1);
+		msleep(10);
+		em28xx_write_regs(dev, 0x04, "\x08", 1);
+		msleep(100);
+		em28xx_write_regs(dev, 0x08, "\xfd", 1);
+		msleep(100);
+		em28xx_write_regs(dev, 0x08, "\xfd", 1);
+		msleep(100);
+		em28xx_write_regs(dev, 0x08, "\xff", 1);
+		msleep(5);
+		em28xx_write_regs(dev, XCLK_REG, "\x27", 1); /* switch em2880 rc protocol */
+#if 0
+		em2880_ir_attach(dev,ir_codes_pinnacle2,ARRAY_SIZE(ir_codes_pinnacle2), em2880_get_key_pinnacle);
+#endif
+
+		em28xx_write_regs(dev, 0x08, "\x6d", 1);
+		msleep(10);
+		em28xx_write_regs(dev, 0x08, "\x7d", 1);
+		msleep(10);
+		break;
+	}
+	
 	case EM2820_BOARD_KWORLD_PVRTV2800RF:
 		/* GPIO enables sound on KWORLD PVR TV 2800RF */
 		em28xx_write_regs_req(dev, 0x00, 0x08, "\xf9", 1);

[-- Attachment #3: Type: text/plain, Size: 150 bytes --]

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