From: Bongani <bhlope@mweb.co.za>
To: kraxel@bytesex.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.5.44 bttv-driver.c
Date: Mon, 21 Oct 2002 00:23:10 +0200 [thread overview]
Message-ID: <200210210023.10640.bhlope@mweb.co.za> (raw)
Hi Gerd
You are listing as the maintainer of the bttv driver, so I hope I'm sending
this to the correct person. The bttv drivers are printing the following
following "debug" information, which is filling up my messages file the patch
bellow seems to fix it.
Oct 20 04:03:01 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=no
mux=4/1 irq=yes
Oct 20 04:03:01 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=yes
mux=1/1 irq=yes
Oct 20 04:03:08 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=no
mux=4/1 irq=yes
Oct 20 04:03:08 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=yes
mux=1/1 irq=yes
Oct 20 04:03:09 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=no
mux=4/1 irq=yes
Oct 20 04:03:09 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=yes
mux=1/1 irq=yes
Oct 20 04:03:10 localhost kernel: bttv0: amux: mode=-1 audio=1 signal=no
mux=4/1 irq=yes
Could you please foward the patch to Linus.(If you think its correct that is
;)
Thanx
--- linux-2.5/drivers/media/video/bttv-driver.c.old 2002-10-21
00:08:50.000000000 +0200
+++ linux-2.5/drivers/media/video/bttv-driver.c 2002-10-21 00:09:17.000000000
+0200
@@ -813,7 +813,7 @@
i2c_mux = mux = (btv->audio & AUDIO_MUTE) ? AUDIO_OFF : btv->audio;
if (btv->opt_automute && !signal && !btv->radio_user)
mux = AUDIO_OFF;
- printk("bttv%d: amux: mode=%d audio=%d signal=%s mux=%d/%d irq=%s\n",
+ dprintk(KERN_DEBUG "bttv%d: amux: mode=%d audio=%d signal=%s mux=%d/%d
irq=%s\n",
btv->nr, mode, btv->audio, signal ? "yes" : "no",
mux, i2c_mux, in_interrupt() ? "yes" : "no");
reply other threads:[~2002-10-20 22:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200210210023.10640.bhlope@mweb.co.za \
--to=bhlope@mweb.co.za \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®