linux-kernel - Re: [RFC] Include ACPI DSDT from INITRD patch into mainline

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-prev] [day] [month] [year] [list]

Message-ID: <20061204105846.GA17953@suse.de>
Date:	Mon, 4 Dec 2006 11:58:46 +0100
From:	Stefan Seyfried <seife@...e.de>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Alan <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	Ben Collins <ben.collins@...ntu.com>
Subject: Re: [RFC] Include ACPI DSDT from INITRD patch into mainline

On Sat, Dec 02, 2006 at 08:45:52AM +0100, Arjan van de Ven wrote:

> now here's another question...

And a good one, indeed.

> the ACPI layer got improved over the last
> 18 months bigtime to behave more like windows in many ways. How much of
> this is still really needed? 

I have not used a machine that really needed this for quite some time now.
Usually even DSDTs that do not pass the "disassemble, then recompile with
iasl"-test seem to work much better in practice than they did before.

And seeing what stupid ideas people come up with (sharing DSDTs on
acpi.sf.net _is_ stupid, since the DSDT usually depends on things you
configured in your BIOS settings, memory size, etc.pp) it is probably
a good idea to keep this patch out of mainline.

It is usefull for debugging, sure, but somebody who can debug on this
level should also be able to patch his kernel :-)
-- 
Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg  | "Well, surrounding them's out." 
-
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/