| 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
| ||
|
Message-ID: <20070405092638.GA30208@srcf.ucam.org> Date: Thu, 5 Apr 2007 10:26:38 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: David Brownell <david-b@...bell.net> Cc: Linux Kernel list <linux-kernel@...r.kernel.org>, Linux ACPI list <linux-acpi@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [patch 2.6.21-rc5-git] make /proc/acpi/wakeup more useful On Tue, Apr 03, 2007 at 05:41:42PM -0700, David Brownell wrote: > This updates /proc/acpi/wakeup to be more informative, primarily by showing > the sysfs node associated with each wakeup-enabled device. Example: This looks good. > S139 S4 disabled Any idea what this one is? There's the potential for all sorts of weird platform devices to expose wakeup capabilities. > Eventually this file should be removed, but until then it's almost the only > way we have to tell how the relevant ACPI tables are broken (and cope). In > that example, two devices don't actually exist (USB3, S139), one can't issue > wakeup events (PCI0), and two seem harmlessly (?) confused (MDM and AUD are > the same PCI device, but it's the _modem_ that does wake-on-ring). Could the MDM entry be referring to the modem codec on the ac97 or hda bus? -- Matthew Garrett | mjg59@...f.ucam.org - 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/
Powered by blists - more mailing lists