From: Andy Walls <awalls@md.metrocast.net>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org, vvvl@onet.pl
Subject: Re: cx23885: Unknown symbol __ir_input_register
Date: Sun, 25 Jul 2010 09:22:37 -0400 [thread overview]
Message-ID: <1280064157.2867.15.camel@localhost> (raw)
In-Reply-To: <1280061846.2867.5.camel@localhost>
On Sun, 2010-07-25 at 08:44 -0400, Andy Walls wrote:
> On Sat, 2010-07-24 at 18:45 +0200, vvvl@onet.pl wrote:
> > with linux-2.6.34-gentoo-r1 and V4L/DVB repository of July 24 I get these errors:
> > cx23885: Unknown symbol __ir_input_register
> > cx23885: Unknown symbol get_rc_map
>
> Those are IR related.
>
> I forgot to add "IR_CORE" to the Kconfig file for the cx23885 driver,
> but the the "VIDEO_IR" selection in that Kconfig depends on "IR_CORE",
> so I think that should be OK.
Hmmm...
"select VIDEO_IR" in the cx23885 Kconfig doesn't revisit the
dependencies on "IR_CORE" and "INPUT".
Mauro,
What's the correct thing to do here?
Change it to
"depends VIDEO_IR"
or add
"depends IR_CORE"
or add
"select INPUT"
"select IR_CORE"
The first is easiet to maintain, but might have something built
in-kernel vs. module in the wrong order.
The second repeats a known dependency, expressed elsewhere, which will
have to be kept in sync (and could still get the build wrong).
The third repeats more known dependencies, expressed elsewhere, which
will have to be kept in sync, but at least the build should always have
the right components built in-kernel.
Or do I misunderstand the select & depends keywords?
Regards,
Andy
next prev parent reply other threads:[~2010-07-25 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 16:45 cx23885: Unknown symbol __ir_input_register vvvl
2010-07-25 12:44 ` Andy Walls
2010-07-25 13:22 ` Andy Walls [this message]
2010-07-25 13:45 ` Andy Walls
2010-07-25 17:57 ` Mauro Carvalho Chehab
2010-07-25 17:55 ` Mauro Carvalho Chehab
2010-07-29 1:26 ` Andy Walls
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=1280064157.2867.15.camel@localhost \
--to=awalls@md.metrocast.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=vvvl@onet.pl \
/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