From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
To: 7eggert@gmx.de
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 21:06:40 -0300 [thread overview]
Message-ID: <1123114000.8274.4.camel@localhost> (raw)
In-Reply-To: <E1E0SGH-0000Zk-7Y@be1.lrz>
Bodo,
Please, send me bttv init logs. I need to know if PCI quirks has
detected your PCI chipset as a problematic one.
Em Qui, 2005-08-04 às 01:02 +0200, Bodo Eggert escreveu:
> Mauro Carvalho Chehab <mchehab@brturbo.com.br> wrote:
>
> > 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.
>
> The CVS line will off cause not apply, and I needed to change
> s/static// int no_overlay in bttv-cards.c.
Strange. At CVS it worked even with static. But it should be ok.
>
> The picture is less distorted by pci activity with no_overlay=1, and it
> feels like the stable interface I used with my nvidia+2.4+XF86 before
> upgrading to 2.6+radeon+X.org. No OOPS within the first few minutes:).
That's good!
Mauro.
next prev parent reply other threads:[~2005-08-04 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4xiqy-2F3-5@gated-at.bofh.it>
2005-08-03 23:02 ` BTTV - experimental no_overlay patch Bodo Eggert
2005-08-04 0:06 ` Mauro Carvalho Chehab [this message]
2005-08-03 3:40 Mauro Carvalho Chehab
2005-08-03 6:06 ` Pavel Machek
2005-08-03 12:29 ` 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=1123114000.8274.4.camel@localhost \
--to=mchehab@brturbo.com.br \
--cc=7eggert@gmx.de \
--cc=aab@cichlid.com \
--cc=linux-kernel@vger.kernel.org \
--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