Messages in this thread | | | Subject | Re: BTTV - experimental no_overlay patch | From | Mauro Carvalho Chehab <> | Date | Wed, 03 Aug 2005 09:29:05 -0300 |
| |
Pavel,
Em Qua, 2005-08-03 às 08:06 +0200, Pavel Machek escreveu: > Hi! > > > This small patch will allow no_overlay flag to disable BTTV driver to > > report OVERLAY capabilities. It should fix your troubles by enabling > > no_overlay=1 when inserting bttv module. > > > > This patch is against our CVS tree, but should apply with some hunk on > > 2.6.13-rc4 or 2.6.13-rc5. > > > > I'll generate a new one at morning, against 2.6.13-rc5 hopefully to > > have it applied at 2.6.13, since it fixes an OOPS. > > You have to pass option for it not to oops? That does not seem > right.... This OOPS is caused by bad implementation of PCI2PCI data transfers (hardware related). It is not related to V4L.
In fact, bttv code uses also a blacklist from PCI code, activating no_overlay option on bad chipsets:
void __devinit bttv_check_chipset(void) { int pcipci_fail = 0; struct pci_dev *dev = NULL;
if (pci_pci_problems & PCIPCI_FAIL) pcipci_fail = 1;
... if (pcipci_fail) { printk(KERN_WARNING "bttv: BT848 and your chipset may not work together.\n"); if (!no_overlay) { printk(KERN_WARNING "bttv: going to disable overlay.\n"); no_overlay = 1; } }
I don't know for sure if these new chipsets are at PCI fail blacklist. After Bodo and Andrew Burgess made these tests, we may submit some info to PCI guys for them to add the chipsets to PCI blacklist, by setting PCIPCI_FAIL flag at pcipci_fail global var.
Mauro.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |