On Sat, 2008-09-06 at 10:12 -0400, Andy Walls wrote: > On Thu, 2008-09-04 at 15:57 -0400, Andy Walls wrote: > > On Thu, 2008-09-04 at 11:00 -0700, Michael wrote: > > > > Hey Andy > > > > > > I hate to be the first to report this, but I'm still obtaining the > > > eeprom error. > >
> > > > And the dmesg output will help me see the current failure mode. > > > > > > > Anyways, you said if it doesn't work, run "/sbin/modprobe > > > cx18 mmio_ndelay=61". I've gotten up to 152, yet it still doesn't > > > work. Should I keep going, to see if it'll eventually catch it? How > > > high? > > > > 500 is half a microsecond and about 16.5 PCI bus cycles delay for each > > IO access. That should be ridiculously long in PCI bus terms as a one > > word transaction can take as little as 4 PCI bus cycles. > > Michael, One more idea. Quite a while ago (30 June) you had partial success setting the ".msecs_asserted" and " .msecs_recovery" delays in cx18-cards.c to 100 along with the two (now three) mdelay()'s near the bottom of cx18-i2c.c to 100. Could you try changing those again to 100, and recompiling the latest cx18 driver? When you modprobe the driver, make sure you set "mmio_ndelay" to a number higher than 0: 31, 61, 92, or higher. It's a shot in the dark. But, if it's not one thing, then maybe it's two. Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
