public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Gill <gillb4@telusplanet.net>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	Linux kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: BTTV broken on recent kernels
Date: Sun, 22 Jan 2006 11:52:05 -0700	[thread overview]
Message-ID: <43D3D455.3000808@telusplanet.net> (raw)
In-Reply-To: <43D1DA98.1080704@linuxtv.org>

Michael Krufky wrote:

>
>> Alistair, Lee: thank you for your replies.  Sadly the bug is in the 
>> Nvidia binary.  Changing the driver to nv from nvidia did resolve the 
>> issue.  Now I have to decide whether I like accelerated 3d more, or 
>> using the tv tuner more (till Nvidia fixes the driver).  Thank you 
>> for your time.  I won't waste any more LKML bandwidth on this (Nvidia 
>> bug).  Thanks again.
>> Bob 
>
>
> Not that I would recommend the binary nvidia driver, but:
>
> You can probably get bttv to work despite this overlay bug by using 
> "grabdisplay" mode instead.  There is an option for it in xawtv.  The 
> difference is, in overlay mode, the capture card is writing directly 
> to videoram.  Using grabdisplay mode eliminates this optimization, and 
> would be a decent workaround for you.
>
> Hope this helps,
>
> Michael
>
I haven't tried using nv with grabdisplay instead of overlay, but I have 
recently run a large (nvidia...and no, I don't work for them) patch 
against the 81.78 driver (about 5 small patches all in one) and it works 
successfully on 2.6.16-rc1-git3 (in both grabdisplay and overlay 
modes).  The only thing I noted is that the old nvidia binaries wanted a 
channel frequency offset of 108, but with the (heavily patched) 81.78 
driver, you don't need an channel frequency offset (both xawtv and 
mplayer).  Your test is simple to try though, and if it doesn't work, 
I'll reply and mention it.   Thanks for your reply.
Bob

      reply	other threads:[~2006-01-22 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16  2:05 BTTV broken on recent kernels Bob Gill
2006-01-16  2:07 ` Lee Revell
2006-01-16  2:51   ` Bob Gill
2006-01-16  4:18 ` Alistair John Strachan
2006-01-17  2:10   ` Bob Gill
2006-01-21  6:54     ` Michael Krufky
2006-01-22 18:52       ` Bob Gill [this message]

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=43D3D455.3000808@telusplanet.net \
    --to=gillb4@telusplanet.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkrufky@linuxtv.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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