On Friday 09 April 2004 10:09, Bernhard C. Schrenk wrote:
Hi,
I am testing the new CI code in the budget-ci driver with a Hauppauge
Nova-CI and a cryptoworks CAM (with a legal ORF smartcard). This setup is
working perfectly under Windows. I have two problems under linux (2.6.1
with
2) If I unload the driver and load it again (tried budget-ci only and also
all modules down to dvb-core). Initialisation of the CAM does not work any
more. I can not retry the whole test cycle yet, because I can not reboot
the machine (due to another bug) remotely.
I can't replicate this on
On Friday 09 April 2004 12:19, you wrote:
2) If I unload the driver and load it again (tried budget-ci only and
also all modules down to dvb-core). Initialisation of the CAM does not
work any more. I can not retry the whole test cycle yet, because I can
not reboot the machine (due to
2) If I unload the driver and load it again (tried budget-ci only and
also
all modules down to dvb-core). Initialisation of the CAM does not work
any
more. I can not retry the whole test cycle yet, because I can not reboot
the machine (due to another bug) remotely.
I can't replicate this
I do not know the protocol well enough, to see the problem, but I think it
has something todo with a tcid comparison in cam_set which is not
fulfilled. The second possible problem I see is that the
dvb_ca_en50221_read_data function is called 1130 times in 12 seconds, but
no data is delivered
Andrew de Quincey wrote:
I do not know the protocol well enough, to see the problem, but I think it
has something todo with a tcid comparison in cam_set which is not
fulfilled. The second possible problem I see is that the
dvb_ca_en50221_read_data function is called 1130 times in 12
On Friday 09 April 2004 12:27, Klaus Schmidinger wrote:
Andrew de Quincey wrote:
I do not know the protocol well enough, to see the problem, but I think
it has something todo with a tcid comparison in cam_set which is not
fulfilled. The second possible problem I see is that the
Johannes Stezenbach said:
Found another typo in the same file (/dev/dvr instead of /dev/dvb), new
patch (cancelling the previous one).
Comitted.
And what about missing files (see my previous message :
http://linuxtv.org/mailinglists/linux-dvb/2004/04-2004/msg00101.html ) ?
I'm about to make a
On Friday 09 April 2004 12:09, Bernhard C. Schrenk wrote:
2) If I unload the driver and load it again (tried budget-ci only and
also
all modules down to dvb-core). Initialisation of the CAM does not work
any
more. I can not retry the whole test cycle yet, because I can not
reboot
There's a line
#define MAX_TPDU_SIZE 2048 /* Maximum size of TPDU */
in ci_link_layer.h of the firmware (hope I'm not violating the NDA
too much here... ;-).
Heh. So that is a limit imposed by the firmware/hardware in the av7110. It
won't accept a TPDU packet from the host 2048 bytes.
I've marked this down and I will put the TS through an ASI TS analyser for an
ETR 290 check when I get into the office on Monday evening. If I get a chance.
This test is rather the definative when it comes to checking the stability and
validity of a TS (although many commercial TS's fail on one
Andrew's frontend changes are all in CVS, and so far as I can tell
work fine. If you find that tuning for your frontend(s) is slower
or more unreliable than with any old drivers, please let us know.
Since I updated to latest CVS from about a month ago, my tuning times on
a DVB-T budget-ci
Hello Everyone,
I'm working on my next release of KnoppMyth and would like to include
support for DVB. I'd like to include the firmware for the various cards
so they can be supported out the box. Reading the docs, I see that I
have to download them from various locations. While I can do
13 matches
Mail list logo
