linux-kernel - 2.6.28: How come some kernel options cannot be disabled for non-existent hardware?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0812300641390.11356@p34.internal.lan>
Date:	Tue, 30 Dec 2008 07:25:42 -0500 (EST)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: 2.6.28: How come some kernel options cannot be disabled for non-existent
 hardware?

Example:

-> ACPI (Advanced Configuration and Power Interface) Support
-> -*-   Dock

>From dmesg:
[    0.247210] ACPI: EC: Look up EC in DSDT
[    0.249987] ACPI: Interpreter enabled
[    0.249990] ACPI: (supports S0 S5)
[    0.250005] ACPI: Using IOAPIC for interrupt routing
[    0.254621] ACPI: No dock devices found.
[    0.254631] ACPI: PCI Root Bridge [PCI0] (0000:00)

I have no Docking bay on my desktop machine, even when I change:
CONFIG_ACPI_DOCK=y
to
CONFIG_ACPI_DOCK=n

It still shows up as enabled and it is in dmesg shown above.  How come 
some kernel options are enabled and cannot (easily?) be disabled for 
hardware that does not exist in my machine?

http://home.comcast.net/~jpiszcz/20081230/config-2.6.28.txt

Justin.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/