Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing

2008-02-15 Thread hermann pitton
Hi, Hartmut,

Am Freitag, den 15.02.2008, 01:32 +0100 schrieb Hartmut Hackmann:
 Hi, again
 
 snip
 
  So this one works as well, great! But which one is it?
  Please tell me the minor device id. I need to use it to separate the 2 
  sections.
  i will need to control the other one in a very different way.
  
  Seems default is some RF loopthrough.
  
  I'll need to measure too against loopthrough conditions, but for sure
  voltage is only on the upper connector and previously with the RF feed
  from the external receiver the lower connector was fine enough.
  
  No voltage in any previous testing and the 12Volts were always
  connected.
  
  Both slightly different Quads from different fabs work as well as the
  CTX948. In my case it is the 16be:0007 and to the 16be:0008 I have no
  access.
  
 Perfect, that's what i needed to know.
 
 snip
  
  We might be already through here and you might like to commit first ;)
  
 Indeed. I should also announce this status for the md8800...
 
 What's your opinion on this:
 According to the hints i got, the isl6405 is visible only on one section
 of the md8800. The other section has control over the voltage through
 a GPIO port. So unless i do something very dirty, there will either be the
 restriction
 - that the DVB-S decoder of the  16be:0007 section needs to be selected first.
   Otherwise the other DVB-S part will not work
 - or i will need to always fire up the LNB supply of the 0008 section as soon
   as DVB is initialized.
 The second approach has the advantage that it has little effect for the end
 user while the first needs to be explained.
 But i am not sure whether the isl6405 is fully short circuit proof. I will 
 read
 the datasheet again...
 

if the second approach is safe and the API says nothing different,
according to the MD8800 manual, it seems to be closer to the behavior of
the other OS, but I can't test it.

In opposite to what is stated for the switchable RF loopthrough on the
two hybrid tuners, the manual claims that the DVB-S inputs are separate
and not connected and nothing to switch there ...

Andrew has loopthrough enabled by default and that is what I even see
from the unused second DVB-S tuner to the first one I can use.

We might want to set has_loopthrough = 0 then too.

Funny stuff again. The latest revision of the manual _seems_ to be clear
for possible tuner/demod/bridge combinations, also states nothing about
concurrent usage of the other analog inputs.

Cheers,
Hermann





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


Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing

2008-02-14 Thread hermann pitton
Am Donnerstag, den 14.02.2008, 02:00 +0100 schrieb Hartmut Hackmann: 
 Hi, folks
 
 In my personal repository:
   http://linuxtv.org/hg/~hhackmann/v4l-dvb-experimental/
 you will find a driver that supports this card, DVB-T and DVB-S
 
 It might also work for
 - one section of the MD8800
 - similar boards based on saa713x, tda10086, tda826x, isl6405
 
 The board will show up as MD8800. According to Hermann, the configurations
 for analog TV and DVB-T are identical.
 If you want to use the board with DVB-S, you will need to load the
 saa7134-dvb module with the option use_frontend=1. The default 0 is
 DVB-T. For those who got the board from a second source: don't forget
 to connect the 12v (the floppy supply) connector.
 
 I don't have a dish, so i depend on your reports. To get the MD8800
 running, i need a volunteer who does the testing for me. He should be able
 to apply patches, compile the driver and read kernel logs.
 
 Good luck
   Hartmut
 

Hartmut,

great job, thank you very much!

Can't wait, result of a first voltage measurement on the md8800 Quad.

The upper LNB connector associated to the second saa7134 16be:0008
device has correct voltage.

Since my stuff is not in the original green PCI slot and I have only the
first 16be:0007 device active, can't test much more for now here.

People with the card in the original Medion PC could set
options saa7134-dvb use_frontend=1 debug=1
in /etc/modprobe.conf and then do depmod -a.

The Syntek v4l usb stkwebcam still produces a compilation error and
needs to be disabled in make xconfig or something else.

After make it is best to do make rmmod on top of your
v4l-dvb-experimental first. Those new to the v4l-dvb development stuff
might do also make rminstall and then check that no *.ko is left
in /lib/modules/kernel_in_use/kernel/drivers/media/*
Especially the old video_buf.ko in the video dir needs to be removed.
Check with ls -R |grep .ko and then make install.

Now I suggest to modprobe saa7134 card=117,96
In that case DVB-T is supported on the lower antenna connector and first
adapter and DVB-S on the upper LNB connector and second adapter.

Or to have it simple, it is safe to make rmmod and
modprobe saa7134 card=5,96 tuner=54,54
This way on the first device is only analog TV enabled, don't forget to
use it first to have good DVB-T reception later anyway, and the only
frontend is the DVB-S one in question for testing.

On the CTX948 voltage is OK

AND

Tuning to: Camera Deputati / autocount: 22
Using DVB device 0:0 Philips TDA10086 DVB-S
tuning DVB-S to 11804000 v 2750
inv:2 fecH:2
DiSEqC: switch pos 0, 13V, hiband (index 2)
DiSEqC: e0 10 38 f1 00 00
. LOCKED.
NOUT: 1
dvbEvents 0:0 started
Tuning delay: 373 ms
pipe opened
xine pipe opened /root/.kaxtv.ts
Asked to stop
pipe closed
Live stopped
dvbstream::run() end
dvbEvents 0:0 ended
fdDvr closed
Frontend closed
Tuning to: Dubai Sports-1 / autocount: 23
Using DVB device 0:0 Philips TDA10086 DVB-S
tuning DVB-S to 11747000 h 2750
inv:2 fecH:3
DiSEqC: switch pos 0, 18V, hiband (index 3)
DiSEqC: e0 10 38 f3 00 00
. LOCKED.
NOUT: 1
dvbEvents 0:0 started
Tuning delay: 374 ms
xine pipe opened /root/.kaxtv1.ts
pipe opened
Asked to stop
pipe closed
Live stopped
dvbstream::run() end
dvbEvents 0:0 ended
fdDvr closed
Frontend closed
Tuning to: ARD Das Erste / autocount: 24
Using DVB device 0:0 Philips TDA10086 DVB-S
tuning DVB-S to 11604000 h 2750
inv:2 fecH:5
DiSEqC: switch pos 0, 18V, loband (index 1)
DiSEqC: e0 10 38 f2 00 00
. LOCKED.
NOUT: 1
dvbEvents 0:0 started
Tuning delay: 379 ms
xine pipe opened /root/.kaxtv.ts
pipe opened
Asked to stop
pipe closed
Live stopped
dvbstream::run() end
dvbEvents 0:0 ended
fdDvr closed
Frontend closed
Tuning to: Abu Dhabi Sport / autocount: 25
Using DVB device 0:0 Philips TDA10086 DVB-S
tuning DVB-S to 12577000 h 2750
inv:2 fecH:3
DiSEqC: switch pos 0, 18V, hiband (index 3)
DiSEqC: e0 10 38 f3 00 00
. LOCKED.
NOUT: 1
dvbEvents 0:0 started
Tuning delay: 379 ms
xine pipe opened /root/.kaxtv1.ts
pipe opened
Asked to stop
pipe closed
Live stopped
dvbstream::run() end
dvbEvents 0:0 ended
fdDvr closed
Frontend closed
Tuning to: BBC World / autocount: 26
Using DVB device 0:0 Philips TDA10086 DVB-S
tuning DVB-S to 12596000 v 2750
inv:2 fecH:3
DiSEqC: switch pos 0, 13V, hiband (index 2)
DiSEqC: e0 10 38 f1 00 00
... LOCKED.
NOUT: 1
dvbEvents 0:0 started
Tuning delay: 560 ms
pipe opened
xine pipe opened /root/.kaxtv.ts

 pipe opened
Asked to stop
pipe closed
Live stopped
dvbstream::run() end
dvbEvents 0:0 ended
fdDvr closed
Frontend closed
Tuning to: All Music / autocount: 38
Using DVB device 0:0 Philips TDA10086 DVB-S
tuning DVB-S to 10949000 v 2750
inv:2 fecH:3
DiSEqC: switch pos 0, 13V, loband (index 0)
DiSEqC: e0 10 38 f0 00 00
. LOCKED.
NOUT: 1
dvbEvents 0:0 started
Tuning delay: 378 ms
xine pipe opened /root/.kaxtv.ts
pipe opened
   
Congratulations!

Cheers,
Hermann



___
linux-dvb 

Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing

2008-02-14 Thread hermann pitton
Hi,

Am Donnerstag, den 14.02.2008, 12:01 +0100 schrieb hermann pitton:
 Am Donnerstag, den 14.02.2008, 02:00 +0100 schrieb Hartmut Hackmann: 
  Hi, folks
  
  In my personal repository:
http://linuxtv.org/hg/~hhackmann/v4l-dvb-experimental/
  you will find a driver that supports this card, DVB-T and DVB-S
  
  It might also work for
  - one section of the MD8800
  - similar boards based on saa713x, tda10086, tda826x, isl6405
  
  The board will show up as MD8800. According to Hermann, the configurations
  for analog TV and DVB-T are identical.
  If you want to use the board with DVB-S, you will need to load the
  saa7134-dvb module with the option use_frontend=1. The default 0 is
  DVB-T. For those who got the board from a second source: don't forget
  to connect the 12v (the floppy supply) connector.
  
  I don't have a dish, so i depend on your reports. To get the MD8800
  running, i need a volunteer who does the testing for me. He should be able
  to apply patches, compile the driver and read kernel logs.
  
  Good luck
Hartmut
  
 
 Hartmut,
 
 great job, thank you very much!
 
 Can't wait, result of a first voltage measurement on the md8800 Quad.
 
 The upper LNB connector associated to the second saa7134 16be:0008
 device has correct voltage.
 
 Since my stuff is not in the original green PCI slot and I have only the
 first 16be:0007 device active, can't test much more for now here.

back on the machine and thinking about it twice ...

The Quad works for me as well on the upper LNB connector, despite of
that I previously used the lower one successfully with RF loopthrough
from an external receiver.

So, in case of the Quad, just let it be autodetected and try on the
first adapter and upper LNB connector.

Even more fun :)

Cheers,
Hermann

 People with the card in the original Medion PC could set
 options saa7134-dvb use_frontend=1 debug=1
 in /etc/modprobe.conf and then do depmod -a.
 
 The Syntek v4l usb stkwebcam still produces a compilation error and
 needs to be disabled in make xconfig or something else.
 
 After make it is best to do make rmmod on top of your
 v4l-dvb-experimental first. Those new to the v4l-dvb development stuff
 might do also make rminstall and then check that no *.ko is left
 in /lib/modules/kernel_in_use/kernel/drivers/media/*
 Especially the old video_buf.ko in the video dir needs to be removed.
 Check with ls -R |grep .ko and then make install.
 
 Now I suggest to modprobe saa7134 card=117,96
 In that case DVB-T is supported on the lower antenna connector and first
 adapter and DVB-S on the upper LNB connector and second adapter.
 
 Or to have it simple, it is safe to make rmmod and
 modprobe saa7134 card=5,96 tuner=54,54
 This way on the first device is only analog TV enabled, don't forget to
 use it first to have good DVB-T reception later anyway, and the only
 frontend is the DVB-S one in question for testing.
 
 On the CTX948 voltage is OK
 
 AND
 
 Tuning to: Camera Deputati / autocount: 22
 Using DVB device 0:0 Philips TDA10086 DVB-S
 tuning DVB-S to 11804000 v 2750
 inv:2 fecH:2
 DiSEqC: switch pos 0, 13V, hiband (index 2)
 DiSEqC: e0 10 38 f1 00 00
 . LOCKED.
 NOUT: 1
 dvbEvents 0:0 started
 Tuning delay: 373 ms
 pipe opened
 xine pipe opened /root/.kaxtv.ts
 Asked to stop
 pipe closed
 Live stopped
 dvbstream::run() end
 dvbEvents 0:0 ended
 fdDvr closed
 Frontend closed
 Tuning to: Dubai Sports-1 / autocount: 23
 Using DVB device 0:0 Philips TDA10086 DVB-S
 tuning DVB-S to 11747000 h 2750
 inv:2 fecH:3
 DiSEqC: switch pos 0, 18V, hiband (index 3)
 DiSEqC: e0 10 38 f3 00 00
 . LOCKED.
 NOUT: 1
 dvbEvents 0:0 started
 Tuning delay: 374 ms
 xine pipe opened /root/.kaxtv1.ts
 pipe opened
 Asked to stop
 pipe closed
 Live stopped
 dvbstream::run() end
 dvbEvents 0:0 ended
 fdDvr closed
 Frontend closed
 Tuning to: ARD Das Erste / autocount: 24
 Using DVB device 0:0 Philips TDA10086 DVB-S
 tuning DVB-S to 11604000 h 2750
 inv:2 fecH:5
 DiSEqC: switch pos 0, 18V, loband (index 1)
 DiSEqC: e0 10 38 f2 00 00
 . LOCKED.
 NOUT: 1
 dvbEvents 0:0 started
 Tuning delay: 379 ms
 xine pipe opened /root/.kaxtv.ts
 pipe opened
 Asked to stop
 pipe closed
 Live stopped
 dvbstream::run() end
 dvbEvents 0:0 ended
 fdDvr closed
 Frontend closed
 Tuning to: Abu Dhabi Sport / autocount: 25
 Using DVB device 0:0 Philips TDA10086 DVB-S
 tuning DVB-S to 12577000 h 2750
 inv:2 fecH:3
 DiSEqC: switch pos 0, 18V, hiband (index 3)
 DiSEqC: e0 10 38 f3 00 00
 . LOCKED.
 NOUT: 1
 dvbEvents 0:0 started
 Tuning delay: 379 ms
 xine pipe opened /root/.kaxtv1.ts
 pipe opened
 Asked to stop
 pipe closed
 Live stopped
 dvbstream::run() end
 dvbEvents 0:0 ended
 fdDvr closed
 Frontend closed
 Tuning to: BBC World / autocount: 26
 Using DVB device 0:0 Philips TDA10086 DVB-S
 tuning DVB-S to 12596000 v 2750
 inv:2 fecH:3
 DiSEqC: switch pos 0, 13V, hiband (index 2)
 DiSEqC: e0 10 38 f1 00 00
 ... LOCKED.
 NOUT: 1
 dvbEvents 0:0 started
 Tuning delay: 560 ms
 pipe opened
 

Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing

2008-02-14 Thread Hartmut Hackmann
Hi, Hermann

I am a bit confused

hermann pitton schrieb:
 Hi,
 
 Am Donnerstag, den 14.02.2008, 12:01 +0100 schrieb hermann pitton:
 Am Donnerstag, den 14.02.2008, 02:00 +0100 schrieb Hartmut Hackmann: 
 Hi, folks

 In my personal repository:
   http://linuxtv.org/hg/~hhackmann/v4l-dvb-experimental/
 you will find a driver that supports this card, DVB-T and DVB-S

 It might also work for
 - one section of the MD8800
 - similar boards based on saa713x, tda10086, tda826x, isl6405

 The board will show up as MD8800. According to Hermann, the configurations
 for analog TV and DVB-T are identical.
 If you want to use the board with DVB-S, you will need to load the
 saa7134-dvb module with the option use_frontend=1. The default 0 is
 DVB-T. For those who got the board from a second source: don't forget
 to connect the 12v (the floppy supply) connector.

 I don't have a dish, so i depend on your reports. To get the MD8800
 running, i need a volunteer who does the testing for me. He should be able
 to apply patches, compile the driver and read kernel logs.

 Good luck
   Hartmut

 Hartmut,

 great job, thank you very much!

 Can't wait, result of a first voltage measurement on the md8800 Quad.

 The upper LNB connector associated to the second saa7134 16be:0008
 device has correct voltage.

 Since my stuff is not in the original green PCI slot and I have only the
 first 16be:0007 device active, can't test much more for now here.
 
 back on the machine and thinking about it twice ...
 
 The Quad works for me as well on the upper LNB connector, despite of
 that I previously used the lower one successfully with RF loopthrough
 from an external receiver.
 
 So, in case of the Quad, just let it be autodetected and try on the
 first adapter and upper LNB connector.
 
So this one works as well, great! But which one is it?
Please tell me the minor device id. I need to use it to separate the 2 sections.
i will need to control the other one in a very different way.

 Even more fun :)
 
 Cheers,
 Hermann
 
 People with the card in the original Medion PC could set
 options saa7134-dvb use_frontend=1 debug=1
 in /etc/modprobe.conf and then do depmod -a.

 The Syntek v4l usb stkwebcam still produces a compilation error and
 needs to be disabled in make xconfig or something else.

Hm, i didn't have any compile problems ...

 After make it is best to do make rmmod on top of your
 v4l-dvb-experimental first. Those new to the v4l-dvb development stuff
 might do also make rminstall and then check that no *.ko is left
 in /lib/modules/kernel_in_use/kernel/drivers/media/*
 Especially the old video_buf.ko in the video dir needs to be removed.
 Check with ls -R |grep .ko and then make install.

 Now I suggest to modprobe saa7134 card=117,96
 In that case DVB-T is supported on the lower antenna connector and first
 adapter and DVB-S on the upper LNB connector and second adapter.

 Or to have it simple, it is safe to make rmmod and
 modprobe saa7134 card=5,96 tuner=54,54
 This way on the first device is only analog TV enabled, don't forget to
 use it first to have good DVB-T reception later anyway, and the only
 frontend is the DVB-S one in question for testing.

Why? the cards should be autodetected. Or is there a variant of the 948 with
a device id different from 16be:000d?
It should be possible to give a list to the use_frontend=xx option.
Something like use_frontend=0,1,0 which should select DVB-S only for the
2nd instance. Am i wrong?
Of corse you will need to select the right frontend which is not easy with
some applications.

snip

But thank you for your fast reporting!

Another issue: You have some patches waiting for integration. We can use
my other repository for this.

Best regards
   Hartmut

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


Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing

2008-02-14 Thread hermann pitton
Hi Hartmut,

Am Donnerstag, den 14.02.2008, 22:59 +0100 schrieb Hartmut Hackmann:
 Hi, Hermann
 
 I am a bit confused
 
 hermann pitton schrieb:
  Hi,
  
  Am Donnerstag, den 14.02.2008, 12:01 +0100 schrieb hermann pitton:
  Am Donnerstag, den 14.02.2008, 02:00 +0100 schrieb Hartmut Hackmann: 
  Hi, folks
 
  In my personal repository:
http://linuxtv.org/hg/~hhackmann/v4l-dvb-experimental/
  you will find a driver that supports this card, DVB-T and DVB-S
 
  It might also work for
  - one section of the MD8800
  - similar boards based on saa713x, tda10086, tda826x, isl6405
 
  The board will show up as MD8800. According to Hermann, the configurations
  for analog TV and DVB-T are identical.
  If you want to use the board with DVB-S, you will need to load the
  saa7134-dvb module with the option use_frontend=1. The default 0 is
  DVB-T. For those who got the board from a second source: don't forget
  to connect the 12v (the floppy supply) connector.
 
  I don't have a dish, so i depend on your reports. To get the MD8800
  running, i need a volunteer who does the testing for me. He should be able
  to apply patches, compile the driver and read kernel logs.
 
  Good luck
Hartmut
 
  Hartmut,
 
  great job, thank you very much!
 
  Can't wait, result of a first voltage measurement on the md8800 Quad.
 
  The upper LNB connector associated to the second saa7134 16be:0008
  device has correct voltage.
 
  Since my stuff is not in the original green PCI slot and I have only the
  first 16be:0007 device active, can't test much more for now here.
  
  back on the machine and thinking about it twice ...
  
  The Quad works for me as well on the upper LNB connector, despite of
  that I previously used the lower one successfully with RF loopthrough
  from an external receiver.
  
  So, in case of the Quad, just let it be autodetected and try on the
  first adapter and upper LNB connector.
  
 So this one works as well, great! But which one is it?
 Please tell me the minor device id. I need to use it to separate the 2 
 sections.
 i will need to control the other one in a very different way.

Seems default is some RF loopthrough.

I'll need to measure too against loopthrough conditions, but for sure
voltage is only on the upper connector and previously with the RF feed
from the external receiver the lower connector was fine enough.

No voltage in any previous testing and the 12Volts were always
connected.

Both slightly different Quads from different fabs work as well as the
CTX948. In my case it is the 16be:0007 and to the 16be:0008 I have no
access.

  Even more fun :)
  
  Cheers,
  Hermann
  
  People with the card in the original Medion PC could set
  options saa7134-dvb use_frontend=1 debug=1
  in /etc/modprobe.conf and then do depmod -a.
 
  The Syntek v4l usb stkwebcam still produces a compilation error and
  needs to be disabled in make xconfig or something else.
 
 Hm, i didn't have any compile problems ...

This happens on an almost given up FC5 with some 2.6.20 ...

  After make it is best to do make rmmod on top of your
  v4l-dvb-experimental first. Those new to the v4l-dvb development stuff
  might do also make rminstall and then check that no *.ko is left
  in /lib/modules/kernel_in_use/kernel/drivers/media/*
  Especially the old video_buf.ko in the video dir needs to be removed.
  Check with ls -R |grep .ko and then make install.
 
  Now I suggest to modprobe saa7134 card=117,96
  In that case DVB-T is supported on the lower antenna connector and first
  adapter and DVB-S on the upper LNB connector and second adapter.
 
  Or to have it simple, it is safe to make rmmod and
  modprobe saa7134 card=5,96 tuner=54,54
  This way on the first device is only analog TV enabled, don't forget to
  use it first to have good DVB-T reception later anyway, and the only
  frontend is the DVB-S one in question for testing.
 
 Why? the cards should be autodetected. Or is there a variant of the 948 with
 a device id different from 16be:000d?
 It should be possible to give a list to the use_frontend=xx option.
 Something like use_frontend=0,1,0 which should select DVB-S only for the
 2nd instance. Am i wrong?
 Of corse you will need to select the right frontend which is not easy with
 some applications.
 
 snip

This was all about first ideas on the Quads.
On the CTX948 there is no problem _at all_!

For the Quad I took my first idea back and said, just let it be auto
detected and take the first frontend then and the upper LNB connector.

Sorry for confusion, but it is still a little ...

 But thank you for your fast reporting!
 
 Another issue: You have some patches waiting for integration. We can use
 my other repository for this.

We might be already through here and you might like to commit first ;)

 Best regards
Hartmut

Cheers,
Hermann



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


Re: [linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing

2008-02-14 Thread Hartmut Hackmann
Hi, again

snip

 So this one works as well, great! But which one is it?
 Please tell me the minor device id. I need to use it to separate the 2 
 sections.
 i will need to control the other one in a very different way.
 
 Seems default is some RF loopthrough.
 
 I'll need to measure too against loopthrough conditions, but for sure
 voltage is only on the upper connector and previously with the RF feed
 from the external receiver the lower connector was fine enough.
 
 No voltage in any previous testing and the 12Volts were always
 connected.
 
 Both slightly different Quads from different fabs work as well as the
 CTX948. In my case it is the 16be:0007 and to the 16be:0008 I have no
 access.
 
Perfect, that's what i needed to know.

snip
 
 We might be already through here and you might like to commit first ;)
 
Indeed. I should also announce this status for the md8800...

What's your opinion on this:
According to the hints i got, the isl6405 is visible only on one section
of the md8800. The other section has control over the voltage through
a GPIO port. So unless i do something very dirty, there will either be the
restriction
- that the DVB-S decoder of the  16be:0007 section needs to be selected first.
  Otherwise the other DVB-S part will not work
- or i will need to always fire up the LNB supply of the 0008 section as soon
  as DVB is initialized.
The second approach has the advantage that it has little effect for the end
user while the first needs to be explained.
But i am not sure whether the isl6405 is fully short circuit proof. I will read
the datasheet again...

Best regards
  Hartmut




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


[linux-dvb] Mdeion / Creatix CTX948 DVB-S driver is ready for testing

2008-02-13 Thread Hartmut Hackmann
Hi, folks

In my personal repository:
  http://linuxtv.org/hg/~hhackmann/v4l-dvb-experimental/
you will find a driver that supports this card, DVB-T and DVB-S

It might also work for
- one section of the MD8800
- similar boards based on saa713x, tda10086, tda826x, isl6405

The board will show up as MD8800. According to Hermann, the configurations
for analog TV and DVB-T are identical.
If you want to use the board with DVB-S, you will need to load the
saa7134-dvb module with the option use_frontend=1. The default 0 is
DVB-T. For those who got the board from a second source: don't forget
to connect the 12v (the floppy supply) connector.

I don't have a dish, so i depend on your reports. To get the MD8800
running, i need a volunteer who does the testing for me. He should be able
to apply patches, compile the driver and read kernel logs.

Good luck
  Hartmut

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