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: <Pine.LNX.4.44L0.1109141056310.2066-100000@iolanthe.rowland.org>
Date:	Wed, 14 Sep 2011 11:02:25 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Sameer Nanda <snanda@...omium.org>
cc:	gregkh@...e.de, <linux-usb@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] USB: ehci-pci: Check and enable wakeup capability

On Tue, 13 Sep 2011, Sameer Nanda wrote:

> If the PORTWAK register is implemented and at least one of the physical
> ports is enabled for wakeup, enable wakeup for the ehci-pci device.

NAK.  Our current policy is that devices do not get enabled for wakeup 
by default unless users expect it (things like keyboards and power 
buttons, maybe LAN interfaces).

One certainly can question this policy.  It might make sense to enable 
wakeup for devices that don't generate wakeup events on their own but 
merely act as bridges for other devices.  By this reasoning, all USB 
host controllers should always be enabled for wakeup by default -- not 
just some of the PCI-based controllers.  But this is a separate matter 
and should be discussed on the mailing list.

Alan Stern

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ