Re: [ivtv-devel] CX23418 support

2007-02-11 Thread Sander Sweers
Alex Izvorski wrote: I am wondering what it would take to get support for the CX23418 chip? Hans (The main developer atm), estimated it would take at least 6 months for it to be done. But this was by himself probably and any help you or other people can give will speed this up. Code wise I

Re: [ivtv-devel] CX23418 support

2007-02-11 Thread Hans Verkuil
On Sunday 11 February 2007 16:42, Sander Sweers wrote: Alex Izvorski wrote: I am wondering what it would take to get support for the CX23418 chip? Hans (The main developer atm), estimated it would take at least 6 months for it to be done. But this was by himself probably and any help you

Re: [ivtv-devel] the application is not reading fast enough

2007-02-11 Thread Linux TV homemaillist
On Thursday 18 January 2007 20:58, Martin Dauskardt wrote: ok, it seems as if it is not the pvrinput-plugin (which does only open vbi0 for ioctls, without reading from it) but the teletext-plugin. The log with ivtvctl -D3: Based on the log and a peek at the code I can confirm this is a

Re: [ivtv-devel] CX23418 support

2007-02-11 Thread Nicholas Fearnley
I wouldn't be holding my breath either - I was developing some hardware last year and Conexant were quite insistent I should spend €€ € with one of their development partners to get datasheets (I think it was about £12 GBP!!!). So I used someone else's IC's. Hope you get them though. Nick

[ivtv-devel] System (practically) non-responsive after several hours...no clues

2007-02-11 Thread Rich Kadel
Kernel: 2.6.18.6 IVTV: 0.8.2 CPU: AMD Opteron(tm) Processor 146 (Family: 15, Model: 39, Stepping: 1) I have a generic 4U AMD Opteron server that was running fine for long periods until I started using the IVTV driver. It's a CentOS 4.3 system. I was using the default 2.6.9 kernel, but ran into

Re: [ivtv-devel] System (practically) non-responsive after several hours...no clues

2007-02-11 Thread Brad Barnett
Rich, 4 PVR 500s is a heavy DMA load for any system. What motherboard does this system employ? What chipset does the motherboard have? VIA chipsets, for example, are particularly prone to DMA issues. A lockup due to a DMA issue can cause all sorts of issue, including your hard drive going

Re: [ivtv-devel] System (practically) non-responsive after several hours...no clues

2007-02-11 Thread Hans Verkuil
On Monday 12 February 2007 00:58, Rich Kadel wrote: Kernel: 2.6.18.6 IVTV: 0.8.2 CPU: AMD Opteron(tm) Processor 146 (Family: 15, Model: 39, Stepping: 1) I have a generic 4U AMD Opteron server that was running fine for long periods until I started using the IVTV driver. It's a CentOS 4.3