| 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: <200905190827.52541.oliver@neukum.org> Date: Tue, 19 May 2009 08:27:52 +0200 From: Oliver Neukum <oliver@...kum.org> To: Marcel Holtmann <marcel@...tmann.org>, linux-usb@...r.kernel.org Cc: Matthew Garrett <mjg59@...f.ucam.org>, Mario Limonciello <mario_limonciello@...l.com>, linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend Am Dienstag, 19. Mai 2009 07:14:24 schrieb Marcel Holtmann: > > > When coming out of S3 if the killswitch isn't activated, the logical > > > USB mouse isn't coldplugged again preventing the udev rule from being > > > matched upon. You can manually run hid2hci and the device will switch > > > modes. > > > > Ok. I don't think the right way to implement this is forcing dell-laptop > > to simulate an unplug. The HCI driver should be responsible for saving > > and restoring state of the device in its suspend/resume method. > > what do you expect the generic USB driver to do? I don't see anything we > can do about it, if the device gets removed from underneath us. In order to do this we'd have to put hid2hci into usbcore and maintain a list of devices it should operate on. Regards Oliver -- 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