| 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: <20080901113425.GA15118@srcf.ucam.org> Date: Mon, 1 Sep 2008 12:34:25 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: Tomas Carnecky <tom@...ervice.com> Cc: Zhang Rui <rui.zhang@...el.com>, Steven King <sfking@...dc.com>, linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org, ibm-acpi-devel@...ts.sourceforge.net Subject: Re: 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after undocking On Mon, Sep 01, 2008 at 12:50:36PM +0200, Tomas Carnecky wrote: > There is one question though that was never answered: Is there any > interaction needed from the userspace when docking/undocking? Something > that the acpi daemon would have to do in response to a dock/undock > event? I'm thinking about > $ echo 1 > /sys/bus/scsi/devices/3\:0\:0\:0/rescan > or something like that. To tell the kernel that some devices may have > disappeared and that it shouldn't try to bring them up when resuming > from sleep. I would expect that ACPI would take care of that (it > certainly removes all USB devices and detaches ata4 (which is the bay in > the docking station). There's no interaction required, but userspace can optionally take responsibility for the docking control. Assuming lack of bugs, anyway. -- 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