linux-kernel - Re: [PATCH 3/3] ACPI: thinkpad-acpi: change thinkpad-acpi input default and kconfig help

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: <20070811180602.GA17843@mellanox.co.il>
Date:	Sat, 11 Aug 2007 21:06:02 +0300
From:	"Michael S. Tsirkin" <mst@....mellanox.co.il>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	lenb@...nel.org, "Michael S. Tsirkin" <mst@....mellanox.co.il>,
	Hugh Dickins <hugh@...itas.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] ACPI: thinkpad-acpi: change thinkpad-acpi input
	default and kconfig help

> Quoting Henrique de Moraes Holschuh <hmh@....eng.br>:
> Subject: [PATCH 3/3] ACPI: thinkpad-acpi: change thinkpad-acpi input default and kconfig help
> 
> The current kconfig help text was misleading users.  Also, the default for
> an input-layer-optimized support caused way too many problems without
> up-to-date userspace in place.
> 
> So, rework the help text, and change the default to N.  Note that
> distributions are supposed to enable this option as soon as they update HAL
> to a version that handles the thinkpad-acpi new input layer interface.

I don't really know the details here, so I could be completely wrong.

However, generally, forcing HAL and kernel to be in sync really
looks to me like a non-ideal way to handle interface change.
For example, this would mean that one can't use the same kernel
for multiple distributions, and for a person like me
that needs to switch distros all the time, it seems like a pain.

Could not the kernel expose both new and old interfaces
somehow, so that HAL can be updated without recompiling the kernel?
For example, there could be a sysfs interface which let the HAL set
the desired interface version.

Couldn't that work?
This seems easy to code up.
Want a patch like that?

-- 
MST
-
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/