From: Cyber Dog <cyberdog3k@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Why is DVB stuff compiling?
Date: Mon, 17 Oct 2005 22:29:23 -0400 [thread overview]
Message-ID: <cbb8f04c0510171929j3378220cp48831caa1b8d478@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
I'm a bit confused here. I have a custom kernel configuration, and
I've trimmed out most of the multimedia aspects sound/video/etc
because this is for a server machine. I was just recompiling, and I
noticed there was still some media stuff compiling:
LD drivers/input/serio/built-in.o
LD drivers/media/common/built-in.o
LD drivers/media/dvb/b2c2/built-in.o
LD drivers/media/dvb/bt8xx/built-in.o
LD drivers/media/dvb/cinergyT2/built-in.o
LD drivers/media/dvb/dvb-core/built-in.o
LD drivers/media/dvb/dvb-usb/built-in.o
LD drivers/media/dvb/frontends/built-in.o
LD drivers/media/dvb/pluto2/built-in.o
LD drivers/media/dvb/ttpci/built-in.o
LD drivers/media/dvb/ttusb-budget/built-in.o
LD drivers/media/dvb/ttusb-dec/built-in.o
LD drivers/media/dvb/built-in.o
LD drivers/media/radio/built-in.o
LD drivers/media/video/built-in.o
LD drivers/media/built-in.o
LD drivers/misc/built-in.o
CC drivers/net/Space.o
This confuses me, because as I said, I'm not including multimedia in
the kernel. I checked the config and I see the following:
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
Which is what I would expect. So why are these things compiling into
the kernel even if they're not selected? Or am I missing something
about the process? Kernel 2.6.13.3 here. Thanks.
[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 22516 bytes --]
next reply other threads:[~2005-10-18 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 2:29 Cyber Dog [this message]
2005-10-18 3:02 ` Michael Krufky
2005-10-18 3:07 ` Michael Krufky
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=cbb8f04c0510171929j3378220cp48831caa1b8d478@mail.gmail.com \
--to=cyberdog3k@gmail.com \
--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®