public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: archan <devrootp@bigfoot.com>
To: Prasanna P Subash <psubash@turbolinux.com>
Cc: John Jasen <jjasen1@umbc.edu>,
	Matthew Gabeler-Lee <msg2@po.cwru.edu>,
	linux-kernel@vger.kernel.org,
	AmNet Computers <amnet@amnet-comp.com>
Subject: Re: bttv problems in 2.4.0/2.4.1 PAL_BG
Date: Wed, 31 Jan 2001 14:29:29 +0530	[thread overview]
Message-ID: <3A77D3F1.4070206@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.32.0101301830330.1138-100000@cheetah.STUDENT.cwru.edu> <Pine.SGI.4.31L.02.0101301951040.887333-100000@irix2.gl.umbc.edu> <20010130171528.B25507@turbolinux.com>

I am using "Pixel View TV tuner card" based on "bttv". It works perfect 
in Windows with default TV application, and also responding well in 
Linux 2.2.17 and 2.4.0-test10 kernel. The device is getting detected 
perfectly by 2.4 kernel but I could not be able to check whether the 
card in 2.4 kernel is responding on PAL-BG signal (here, my frequency 
table is PAL-BG, country India) as none of the Linux apps (xawtv, 
cabletv) are responding positively.

archan
devrootp@bigfoot.com
archanp@bigfoot.com

Prasanna P Subash wrote:

> I have experienced similar issues with 2.4.0 and its test. I have a bttv848 chipset.
> I even tried compiling in kdb as a part of the kernel to see if it oopses, but no luck.
> 
> I will try trying 0.7.47 today.
> 
> this works on 2.2.16, last time i tried.
> 


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-31  8:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30 23:50 bttv problems in 2.4.0/2.4.1 Matthew Gabeler-Lee
2001-01-31  0:53 ` John Jasen
2001-01-31  1:06   ` Matthew Gabeler-Lee
2001-01-31  7:41     ` Gerd Knorr
2001-01-31 16:59       ` Prasanna P Subash
2001-01-31  1:15   ` Prasanna P Subash
2001-01-31  1:57     ` adrian
2001-01-31  2:05       ` Matthew Gabeler-Lee
2001-01-31 13:06         ` adrian
2001-01-31 21:39           ` Gerd Knorr
2001-02-01  3:23             ` adrian
2001-01-31  8:59     ` archan [this message]
2001-01-31 14:51       ` bttv problems in 2.4.0/2.4.1 PAL_BG John Jasen
2001-02-01  4:14         ` archan
2001-02-10  0:02 ` bttv problems in 2.4.0/2.4.1 Dr. Kelsey Hudson
2001-02-10  0:46   ` Matthew Gabeler-Lee
2001-02-10  3:37   ` Matthew Gabeler-Lee

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=3A77D3F1.4070206@bigfoot.com \
    --to=devrootp@bigfoot.com \
    --cc=amnet@amnet-comp.com \
    --cc=jjasen1@umbc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msg2@po.cwru.edu \
    --cc=psubash@turbolinux.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