linux-kernel - Re: dsdt buggy acpi

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

Message-ID: <20080702082555.0959ef2b@linux360.ro>
Date:	Wed, 2 Jul 2008 08:25:55 +0300
From:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
To:	"Justin Mattock" <justinmattock@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"ACPI Devel Maling List" <linux-acpi@...r.kernel.org>
Subject: Re: dsdt buggy acpi

On Tue, 1 Jul 2008 16:18:45 +0000
"Justin Mattock" <justinmattock@...il.com> wrote:

> Cool; thanks.
> I'll check that out and see where and how I can locate the dsdt
> manufacture number,  then see if I can fix the broken dsdt error and
> apply this to the kernel and see what happens.
> regards;

Just one note here: DSDTs have nothing to do with the kernel. This is
just broken firmware. The most one can do _in-kernel_ is blacklist some
functionality or create a workaround, but this only happens for widely
used stuff. Broken DSDTs aren't widely used stuff, they are written by
the machine's vendor (the laptop's manufacturer for example, but this
could be different for desktops) and differ a lot from one machine to
another.

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