From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
To: Pavel Machek <pavel@suse.cz>
Cc: Andrew Burgess <aab@cichlid.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux and Kernel Video <video4linux-list@redhat.com>
Subject: Re: BTTV - experimental no_overlay patch
Date: Wed, 03 Aug 2005 09:29:05 -0300 [thread overview]
Message-ID: <1123072145.9082.16.camel@localhost> (raw)
In-Reply-To: <20050803060640.GC1399@elf.ucw.cz>
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.
next prev parent reply other threads:[~2005-08-03 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 3:40 BTTV - experimental no_overlay patch Mauro Carvalho Chehab
2005-08-03 6:06 ` Pavel Machek
2005-08-03 12:29 ` Mauro Carvalho Chehab [this message]
[not found] <4xiqy-2F3-5@gated-at.bofh.it>
2005-08-03 23:02 ` Bodo Eggert
2005-08-04 0:06 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1123072145.9082.16.camel@localhost \
--to=mchehab@brturbo.com.br \
--cc=aab@cichlid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox