public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Chazarain <guichaz@yahoo.fr>
To: Mickael Marchand <marchand@kde.org>
Cc: Gerd Knorr <kraxel@bytesex.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.11-rc3 - BT848 no signal
Date: Fri, 04 Feb 2005 11:44:33 +0100	[thread overview]
Message-ID: <42035211.9030603@yahoo.fr> (raw)
In-Reply-To: <4202798B.7000802@kde.org>

[-- Attachment #1: Type: text/plain, Size: 299 bytes --]

Mickael Marchand wrote:

> Hello,
>
> I am having the same kind of troubles (can't tune and mt_set_frequency 
> -121 errors) since 2.6.10 (it was working in 2.6.9) on amd64.
> this patch did not help sadely.

I have the same problem, but on x86, the attached patch fixed it for me.

-- 
Guillaume



[-- Attachment #2: tda9887.diff --]
[-- Type: text/x-patch, Size: 654 bytes --]

--- linux-2.6.11-rc3/drivers/media/video/tda9887.c
+++ linux-2.6.11-rc3/drivers/media/video/tda9887.c
@@ -545,19 +553,21 @@
 	int rc;
 
 	memset(buf,0,sizeof(buf));
+	tda9887_set_tvnorm(t,buf);
 	buf[1] |= cOutputPort1Inactive;
 	buf[1] |= cOutputPort2Inactive;
-	tda9887_set_tvnorm(t,buf);
 	if (UNSET != t->pinnacle_id) {
 		tda9887_set_pinnacle(t,buf);
 	}
 	tda9887_set_config(t,buf);
 	tda9887_set_insmod(t,buf);
 
+#if 0
 	if (t->std & V4L2_STD_SECAM_L) {
 		/* secam fixup (FIXME: move this to tvnorms array?) */
 		buf[1] &= ~cOutputPort2Inactive;
 	}
+#endif
 
 	dprintk(PREFIX "writing: b=0x%02x c=0x%02x e=0x%02x\n",
 		buf[1],buf[2],buf[3]);

  reply	other threads:[~2005-02-04 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  2:35 Linux 2.6.11-rc3 Linus Torvalds
2005-02-03  5:19 ` Linux 2.6.11-rc3 - BT848 no signal Markus Trippelsdorf
2005-02-03 10:17   ` Gerd Knorr
2005-02-03 11:02     ` Markus Trippelsdorf
2005-02-03 11:30       ` Gerd Knorr
2005-02-03 12:02         ` Markus Trippelsdorf
2005-02-03 19:20         ` Mickael Marchand
2005-02-04 10:44           ` Guillaume Chazarain [this message]
2005-02-04 17:37             ` Mickael Marchand

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=42035211.9030603@yahoo.fr \
    --to=guichaz@yahoo.fr \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marchand@kde.org \
    /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