From: Sergey Vlasov <vsu@altlinux.ru>
To: David Liontooth <liontooth@cogweb.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.16] saa7134 disable_ir oops
Date: Fri, 7 Apr 2006 21:19:10 +0400 [thread overview]
Message-ID: <20060407171910.GB8376@procyon.home> (raw)
In-Reply-To: <4435BA58.4080709@cogweb.net>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Thu, Apr 06, 2006 at 06:03:20PM -0700, David Liontooth wrote:
> >Does the following patch fix things?
> >
> The patch fixes the oops -- thank you! Yet the ir modules get loaded in
> spite of the "disable_ir=1" parameter:
>
> # sudo modprobe -vvv saa7134 card=2 tuner=43 disable_ir=1
> insmod /lib/modules/2.6.16/kernel/drivers/media/common/ir-common.ko
> insmod /lib/modules/2.6.16/kernel/drivers/media/video/ir-kbd-i2c.ko
> insmod /lib/modules/2.6.16/kernel/drivers/media/video/video-buf.ko
> insmod /lib/modules/2.6.16/kernel/drivers/media/video/saa7134/saa7134.ko
> card=2 tuner=43 disable_ir=1
This is normal - saa7134 uses some symbols from these modules, and
such dependencies cannot be dynamic. The disable_ir=1 option just
prevents saa7134 from enabling the IR input and registering the
corresponding input device with the kernel, therefore the IR code will
stay unused.
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-07 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 22:00 David Liontooth
2006-04-06 16:20 ` Sergey Vlasov
2006-04-07 1:03 ` David Liontooth
2006-04-07 17:19 ` Sergey Vlasov [this message]
2006-04-07 13:16 ` Mauro Carvalho Chehab
2006-04-07 13:36 ` Sergey Vlasov
2006-04-07 21:40 ` Hartmut Hackmann
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=20060407171910.GB8376@procyon.home \
--to=vsu@altlinux.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=liontooth@cogweb.net \
/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®