From: LAUTERWASSER Stefan <stefan.lauterwasser@thalesgroup.com>
To: "'linux-config@vger.kernel.org'" <linux-config@vger.kernel.org>
Subject: Can't remove CONFIG_GENERIC_CMOS_UPDATE, CONFIG_X86_TSC from kernel configuration
Date: Tue, 14 Oct 2014 11:34:43 +0200 [thread overview]
Message-ID: <29345_1413279277_543CEE2C_29345_1230_1_FDF2BCC5A347C04C96E55A31D54D9D510899DC6808@THSNCOA06MXS02P.ONE-06.GRP> (raw)
I want to rebuild linux-3.16.3-200.fc20.x86_64 with options:
CONFIG_GENERIC_CMOS_UPDATE=n
CONFIG_X86_TSC=n
But it seams that "make olddefconfig" enables these options again because of dependencies.
I found the "select GENERIC_CMOS_UPDATE" entries in arch/*/Kconfig files - if I remove them, I am able to build a kernel with CONFIG_GENERIC_CMOS_UPDATE=n.
It's selected by default but does not seam to be necessary isn't it?
I am not able to disable CONFIG_X86_TSC.
It seams that Xen (arch/x86/xen/Kconfig) depends on X86_TSC - so I disabled all the XEN stuff.
May arch/x86/Kconfig.cpu (config X86_TSC - def_bool y) is the reason that CONFIG_X86_TSC is enabled again?
I thought it's just on of multiple clock sources isn't it?
It's my first email to a kernel mailing list so please be clement - feetback welcome. :-)
Mit freundlichen Grüßen/Best regards
Stefan Lauterwasser
Software Engineer
Transportation Systems
Thales Deutschland
Email: Stefan.Lauterwasser@thalesgroup.com
Web: www.thalesgroup.com
--------------------------------------------------------------
Thales Transportation Systems GmbH
Thalesplatz 1 - 71254 Ditzingen - Germany
--
To unsubscribe from this list: send the line "unsubscribe linux-config" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-10-14 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 9:34 LAUTERWASSER Stefan [this message]
[not found] <2xgu1p0011TeosZ01xgvhH>
2014-10-18 19:35 ` Can't remove CONFIG_GENERIC_CMOS_UPDATE, CONFIG_X86_TSC from kernel configuration John D. Hendrickson and Sara Darnell
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=29345_1413279277_543CEE2C_29345_1230_1_FDF2BCC5A347C04C96E55A31D54D9D510899DC6808@THSNCOA06MXS02P.ONE-06.GRP \
--to=stefan.lauterwasser@thalesgroup.com \
--cc=linux-config@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).