I'm trying to put as many PVR350 cards into one machine as possible, but I am encountering some problems. The machine I'm using is a server system with a backplane which contains a PCI Bridge Backplane giving it 17 PCI slots (PX-20S3 from ICP Electronics Inc).
Problem 1: If I put one PVR350 card in the first slot of the first bus and one card in the first slot of the second bus, the first card (and probably the second as well) does not work. Does anybody have any experience doing similar things and issues I might want to look into in trying to solve this? Furthermore, I've looked at the driver and it seems to have a 9 cards limit hard coded, which assuming there aren't other issues limiting that number I can always try to increase. But to be useful, I need the system to accept cards on both PCI buses. Problem 2: If I fill the first bus with PVR350 cards (8 in total), the first four cards seem to work fine. The fifth card is somehow detected by the ivtv driver, but does not seem to work. The three remaining cards do not seem to be detected/initialized properly. The entries in /dev/ indicate that 5 cards should be working, but only the first four actually do. >From extensive googling and reading on this list, I read there might be some issues with sharing interrupts. If anybody have any pointers to more about this, please let me know. Anyway, I've disabled the serial and parallell ports on the machine, but the result is the same as previous. I've read about the interrupt lines on the backplane card, and it seems it has four interrupts which I would then assume would be shared between the various buses and slots. The OS/BIOS seems to assign those interrupts to the available numbered interrupts in the OS/BIOS. If the PVR350 cards can not share interrupts, the that explains the behaviour of a maximum of four. Can anybody confirm this? Problem 3: I've tried both the 0.3.6o and 0.2.0-rc3j drivers released on a linux 2.6.12 kernel. The 0.2.0-rc3j driver hard to be patched to compile, but the patch released here seems to work fine. The 0.3.6o driver compiled and installed on 2.6.12 without any trouble. Both drivers seem to be acting up in the same place indicated by the log. For a card that works, the log output is typically: Jun 20 14:18:02 snaptuner-slb01 ivtv: Configuring WinTV PVR 350 card with 9 streams Jun 20 14:18:02 snaptuner-slb01 ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total Jun 20 14:18:02 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 0 minor 4 Jun 20 14:18:02 snaptuner-slb01 ivtv: Create DMA stream 1 Jun 20 14:18:02 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 1 minor 36 Jun 20 14:18:02 snaptuner-slb01 ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total Jun 20 14:18:02 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 2 minor 236 Jun 20 14:18:02 snaptuner-slb01 ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total Jun 20 14:18:02 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 3 minor 28 Jun 20 14:18:02 snaptuner-slb01 ivtv: Create stream 4 Jun 20 14:18:02 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 4 minor 68 Jun 20 14:18:02 snaptuner-slb01 ivtv: Create DMA stream 5 using 16 65536 byte buffers 1048576 kbytes total Jun 20 14:18:02 snaptuner-slb01 wait_for_sysfs[9494]: either wait_for_sysfs (udev 045) needs an update to handle the device '/devices/platform/i2c-3/3-0021' properly (bus specific file unavailable) or the sysfs-support of your device's driver needs to be fixed, please report to <[EMAIL PROTECTED]> Jun 20 14:18:02 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 5 minor 20 Jun 20 14:18:02 snaptuner-slb01 ivtv: Create stream 6 using 1024 2048 byte buffers 262144 kbytes total Jun 20 14:18:02 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 6 minor 237 Jun 20 14:18:02 snaptuner-slb01 ivtv: Create stream 7 Jun 20 14:18:02 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 7 minor 238 Jun 20 14:18:02 snaptuner-slb01 ivtv: Create DMA stream 8 Jun 20 14:18:02 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 8 minor 52 Jun 20 14:18:02 snaptuner-slb01 ivtv: Setting Tuner 38 For the adapters where it does not work, the first differences show up like below: Jun 20 15:31:38 snaptuner-slb01 ivtv: Configuring WinTV PVR 350 card with 10 streams Jun 20 15:31:38 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 0 minor 5 Jun 20 15:31:38 snaptuner-slb01 ivtv: Create DMA stream 0 using 128 32768 byte buffers 0 kbytes total Jun 20 15:31:38 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 1 minor 37 Jun 20 15:31:38 snaptuner-slb01 ivtv: Create DMA stream 1 using 161 12960 byte buffers 0 kbytes total Jun 20 15:31:38 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 2 minor 239 Jun 20 15:31:38 snaptuner-slb01 ivtv: Create DMA stream 2 using 165 12635 byte buffers 0 kbytes total Jun 20 15:31:38 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 3 minor 29 Jun 20 15:31:38 snaptuner-slb01 ivtv: Create DMA stream 3 using 455 4608 byte buffers 0 kbytes total Jun 20 15:31:38 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 4 minor 69 Jun 20 15:31:38 snaptuner-slb01 ivtv: Create stream 4 Jun 20 15:31:38 snaptuner-slb01 ivtv: Registered v4l2 device, streamtype 5 minor 21 Jun 20 15:31:38 snaptuner-slb01 ivtv: Create DMA stream 5 using 16 65536 byte buffers 0 kbytes total Jun 20 15:31:38 snaptuner-slb01 ivtv: Couldn't register v4l2 device, streamtype 6, minor 9 Jun 20 15:31:38 snaptuner-slb01 ivtv: Error -12 setting up streams This looks more or less identical. The messages about 0 kbytes total buffers is of course very suspicious. Does anybody have any idea on what is going wrong? I have plenty of debug output and can provide more details if anybody is interested in helping out. Thanks in advance, Marius Kjeldahl ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
