public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@m1k.net>
To: Lukas Hejtmanek <xhejtman@mail.muni.cz>
Cc: linux-kernel@vger.kernel.org, kraxel@bytesex.org
Subject: Re: CX8800 driver and 2.6.15-RC2
Date: Sat, 03 Dec 2005 16:10:30 -0500	[thread overview]
Message-ID: <439209C6.9080004@m1k.net> (raw)
In-Reply-To: <20051203180740.GA11293@mail.muni.cz>

Lukas Hejtmanek wrote:

>On Fri, Dec 02, 2005 at 03:37:59PM -0500, Michael Krufky wrote:
>  
>
>>It was a memory management bug.... Already fixed in -rc3 (where new bugs 
>>were introduced) ...
>>
>>-rc4 isn't bad, but a whole slew of v4l / dvb bugfixes went in JUST 
>>after -rc4 release...
>>
>>Can you try 2.6.15-rc4-git1 and let us know how things are?
>>    
>>
>well, with 2.6.15-rc4-git video_buf related problems are gone, but it's still
>far from usable. xawtv is unable to use tunner.
>
Which card do you have?  What card # does it report in dmesg?  What 
tuner # is it using?  What is the PCI Subsystem id?

The following MIGHT fix it.... If so, I'll need the answers to the four 
questions above, in order to make this behavior occur by default:

modprobe  tda9887

This fixes the problem for analog video with pcHDTV 3000 and DViCO 
FusionHDTV3 Gold-T.  We've already fixed it in cvs so that this will be 
detected by default, if you have a different card, we might have to 
apply a similar fix.  If that doesn't help, then it's a different bug.

>Moreover, it seems that it cannot get another capture format than 320x240 RGB.
>
-- 
Michael Krufky



  reply	other threads:[~2005-12-03 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 20:14 CX8800 driver and 2.6.15-RC2 Lukas Hejtmanek
2005-12-02 20:37 ` Michael Krufky
2005-12-03 18:07   ` Lukas Hejtmanek
2005-12-03 21:10     ` Michael Krufky [this message]
2005-12-04 10:05       ` Lukas Hejtmanek
2005-12-11 15:04       ` Lukas Hejtmanek

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=439209C6.9080004@m1k.net \
    --to=mkrufky@m1k.net \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xhejtman@mail.muni.cz \
    /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