Rene Bartsch wrote:
I'm having artefacts in the picture (VDR). The HDD (SATA) performs with
58 MB/s, so I assume it's related to the PCI-bus (on an i865PE board).
My setup has an i865G running with 4 x Nova-T PCI cards and I don't see
any problems so I suspect the PCI bus is not the cause.
Hi there!
I dont know if this is the place where I should ask for help regarding a hint for
using a B2C2
Skystar2 dvb board for data transfer/internet. I tried to use it with 2.6.5, 2.6.6,
2.6.7 and also
with the drivers from CVS; the pc is hanging when trying to spawn more than one
intreface
Andreas Share wrote:
Hmm, my skystar2 rev 2.6c/stv0299 dies within 2-3h, but my nova (like
budget-ci) and my ff rev 1.5 sometimes run for ~12h...
i have seen the skystar2 irq_handler calls dvb_dmx_swfilter_packets()
more
often than the other cards
if (adapter-capturing != 0) {
Andreas Share wrote:
Hi,
I have around 1600-1800 interrupts per second, with the ss2 as secondary
device during epgscan.
OK, That is not excessive - an idle 2.6 machine has 1000 from the timer
interrupt alone.
One other thing: The Dbox2 related Tuxbox Project share the Api3 and the
most of
- Original Message -
From: Jon Burgess [EMAIL PROTECTED]
To: Andreas Share [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, July 10, 2004 10:26 PM
Subject: [linux-dvb] Re: Vdr video data stream broken
Andreas Share wrote:
Hi,
I have around 1600-1800 interrupts per second,
On Saturday 10 July 2004 19:18, Ady Deac wrote:
Hi there!
I dont know if this is the place where I should ask for help regarding a
hint for using a B2C2 Skystar2 dvb board for data transfer/internet. I
tried to use it with 2.6.5, 2.6.6, 2.6.7 and also with the drivers from
CVS; the pc is
After updating the dvb-kernel from yesterday, I am unable to unload the
stv0299 module from my 2.6.7-bk20 kernel.
dvb_ttpci 312588 18
saa7146_vv 50432 1 dvb_ttpci
video_buf 22020 1 saa7146_vv
saa714619044 2 dvb_ttpci,saa7146_vv
On Sunday 11 July 2004 00:32, C.Y.M. wrote:
After updating the dvb-kernel from yesterday, I am unable to unload the
stv0299 module from my 2.6.7-bk20 kernel.
I added code that locks the frontend module when it attaches to a card driver
yesterday, offcourse this should be the other way around.
Hi,
I've attached a patch which fixes the problem where a program has the frontend
device open, and the frontend module is removed. I've only fixed the
frontends which already has been converted to the kernel i2c layer, as the
rest will be forced to provide the dvb-core with module info when
On Sunday 11 July 2004 04:58, C.Y.M. wrote:
I just checked in a fix for this, so that it ups the card
drivers module ref
count when a frontend attaches, and not the frontend module
ref count as this
was really the problem I was seeing.
Now I have the same problem unloading the modules,
Forgot the patch, here it is..
Regards
ChrisIndex: linux/drivers/media/dvb/dvb-core/dvb_frontend.c
===
RCS file: /cvs/linuxtv/dvb-kernel/linux/drivers/media/dvb/dvb-core/dvb_frontend.c,v
retrieving revision 1.80
diff -u -p -r1.80
Won't the dvb-ttpci module be released when you unload the
frontend module?
It does that here..
Yes, sorry. I was trying to remove the driver before the frontend. I just
changed the order of removal in my shutdown script and its working fine now.
Thank you for everything and such a fast
On Sunday 11 July 2004 05:36, C.Y.M. wrote:
Won't the dvb-ttpci module be released when you unload the
frontend module?
It does that here..
Yes, sorry. I was trying to remove the driver before the frontend. I just
changed the order of removal in my shutdown script and its working fine
I belive my first commit was correct, except for the fact
that I missed the
that I had placed the module_put call below a return
statement, doh. I don't
dare commit more errors, so I'm just going to wait untill
Michael or any of
the other gurus can confirm this. Also the patch I
14 matches
Mail list logo
