From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Trent Piepho <xyzzy@speakeasy.org>,
v4l-dvb-maintainer@linuxtv.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [v4l-dvb-maintainer] bttv build error (CONFIG_NET=n)
Date: Thu, 01 Nov 2007 06:28:29 -0200 [thread overview]
Message-ID: <1193905709.8587.24.camel@gaivota> (raw)
In-Reply-To: <20071031092350.91eae067.randy.dunlap@oracle.com>
Randy,
> > The only reason the net stuff works, is because CONFIG_NET includes igmp.c,
> > which can't be compiled as a module. That means ip_compute_csum() will get
> > pulled out of the lib.a file for igmp, and thus be present for the net modules
> > that use it too. If igmp could be turned off, made a module, or stopped using
> > ip_compute_csum(), then the users of ip_compute_csum() that do depend on
> > CONFIG_NET would have the same problem as bttv does.
>
> Thanks for the analysis and summary.
> (I'm still waiting for those lkml.org links to load... timed out)
>
> > It seems a shame to create a new ip checksum function in the bttv driver when
> > a perfectly good one already exists and will already be present in just about
> > every kernel out there. Honestly, how common is NET=n and VIDEO_BT848=m
> > outside of randconfig?
This might happen on embedded devices, like a set top box or a PVR,
using a bttv hardware.
> so just adding "depends on NET" should be OK then?
Seems very weird to have bttv module dependent on NET, just because a
checksum calculus function is defined there.
One possible solution would be to move this function to another place
and having both NET, BTTV and other places selecting it.
--
Cheers,
Mauro
next prev parent reply other threads:[~2007-11-01 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 5:15 bttv build error (CONFIG_NET=n) Randy Dunlap
2007-10-31 11:51 ` [v4l-dvb-maintainer] " Trent Piepho
2007-10-31 16:23 ` Randy Dunlap
2007-11-01 8:28 ` Mauro Carvalho Chehab [this message]
2007-11-01 14:53 ` Randy Dunlap
2007-11-02 0:39 ` Trent Piepho
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=1193905709.8587.24.camel@gaivota \
--to=mchehab@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=xyzzy@speakeasy.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