Oops, didn't realize before that my configuration was broken; but then again, I'm just a poor guy with only 1 350 ;-)
Any idea where these are coming from? Don't tknow if they are related to the X-driver as well. They don't seem to cause any problems but fill up my message-buffers: ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d3c81c of 196608 bytes failed with (-512) offset = 0x00102814, total 1255444 ivtv: OSD: DMA xfer from 0xb7d13824 of 458752 bytes failed with (-512) offset = 0x000d981c, total 1349660 ivtv: OSD: DMA xfer from 0xb7cf5a60 of 786432 bytes failed with (-512) offset = 0x000bba58, total 1555032 ivtv: OSD: DMA xfer from 0xb7d05a60 of 720896 bytes failed with (-512) offset = 0x000cba58, total 1555032 ivtv: OSD: DMA xfer from 0xb7ccfddc of 327680 bytes failed with (-512) offset = 0x00095dd4, total 941524 ivtv: OSD: DMA xfer from 0xb7d13824 of 458752 bytes failed with (-512) offset = 0x000d981c, total 1349660 Otherwise the driver (0.3.2a) is running fine. On Mon, 20 Dec 2004 20:17:41 -0000, John Harvey <[EMAIL PROTECTED]> wrote: > No that's the way it works. > This is X server code doing the work not our driver. > > It did actually list it correctly for you in the line :- > (WW) ivtvdev: No matching Device section for instance (BusID PCI:2:10:0) > found > > What was happening before is that it was ignoring your busid because it was > invalid. > This is ok in single card mode but causes a problem in multi card mode. So > people would get the 350 working with a broken configuration and the same > for their normal driver but when they tried to merge them it would break > horribly and then be really hard to debug. > > If it continues to be a problem I could add some code to generate a new > "correct" decimal version of the busid before passing it the the Xserver > code. > > John > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > > [EMAIL PROTECTED] On Behalf Of Nick Rosier > > Sent: 20 December 2004 19:46 > > To: [EMAIL PROTECTED] > > Subject: Re: [ivtv-devel] [X-Drviver] V0.7 xdriver source > > > > Sorry, fixed it. Started throwing different ID's at it. On a wild > > guess I tried 2:10:0 and that worked. Is this a small bug? PCI probing > > shows the busid in hex, putting it in hex in xorg.conf doesn't work > > but gives an error in decimal for the correct busid. > > > > On Mon, 20 Dec 2004 20:42:15 +0100, Nick Rosier <[EMAIL PROTECTED]> > > wrote: > > > This is a snippit from my Xorg.0.log file: > > > > > > (II) PCI: Probing config type using method 1 > > > (II) PCI: Config type is 1 > > > (II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000 > > > (II) PCI: PCI scan (all values are in hex) > > > (II) PCI: 00:00:0: chip 10de,00e1 card 1695,100c rev a1 class 06,00,00 > > hdr 00 > > > (II) PCI: 00:01:0: chip 10de,00e0 card 1695,100c rev a2 class 06,01,00 > > hdr 80 > > > (II) PCI: 00:01:1: chip 10de,00e4 card 1695,100c rev a1 class 0c,05,00 > > hdr 80 > > > (II) PCI: 00:02:0: chip 10de,00e7 card 1695,100c rev a1 class 0c,03,10 > > hdr 80 > > > (II) PCI: 00:02:1: chip 10de,00e7 card 1695,100c rev a1 class 0c,03,10 > > hdr 80 > > > (II) PCI: 00:02:2: chip 10de,00e8 card 1695,100c rev a2 class 0c,03,20 > > hdr 80 > > > (II) PCI: 00:05:0: chip 10de,00df card 1695,100c rev a2 class 06,80,00 > > hdr 00 > > > (II) PCI: 00:06:0: chip 10de,00ea card 1695,100b rev a1 class 04,01,00 > > hdr 00 > > > (II) PCI: 00:08:0: chip 10de,00e5 card 1695,100c rev a2 class 01,01,8a > > hdr 00 > > > (II) PCI: 00:0a:0: chip 10de,00e3 card 1695,100c rev a2 class 01,01,85 > > hdr 00 > > > (II) PCI: 00:0b:0: chip 10de,00e2 card 0000,0000 rev a2 class 06,04,00 > > hdr 01 > > > (II) PCI: 00:0e:0: chip 10de,00ed card 0000,0000 rev a2 class 06,04,00 > > hdr 01 > > > (II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 > > hdr 80 > > > (II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 > > hdr 80 > > > (II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 > > hdr 80 > > > (II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 > > hdr 80 > > > (II) PCI: 01:00:0: chip 10de,0171 card 0000,0000 rev a3 class 03,00,00 > > hdr 00 > > > (II) PCI: 02:06:0: chip 1106,3043 card 1186,1400 rev 06 class 02,00,00 > > hdr 00 > > > (II) PCI: 02:0a:0: chip 4444,0803 card 0070,4000 rev 01 class 04,00,00 > > hdr 00 > > > (II) PCI: End of PCI scan > > > > > > lspci gives: > > > > > > 0000:02:0a.0 Multimedia video controller: Internext Compression Inc > > > iTVC15 MPEG-2 Encoder (rev 01) > > > > > > So the BusID for my card should be 02:0a:0 > > > > > > Before, my BusID was "0x02:0x0a:0x00" and that worked fine. Now I set > > > it to 2:0a:0 but I get this error: > > > > > > (WW) ivtvdev: No matching Device section for instance (BusID PCI:2:10:0) > > found > > > (EE) No devices detected. > > > > > > Any idea? > > > > > > N. > > > > > > On Sun, 19 Dec 2004 16:28:33 -0000, John Harvey > > > <[EMAIL PROTECTED]> wrote: > > > > Change > > > > BusID "0:0x08:0" > > > > > > > > To > > > > BusID "0:08:0" > > > > > > > > It has > > > > Bus id's are decimal and should only contain digits and colons in the > > id > > > > part. > > > > The x in the Busid causes the parser to error. > > > > > > > > John > > > > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://productguide.itmanagersjournal.com/ > > _______________________________________________ > > ivtv-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > ivtv-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ ivtv-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
