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]
Date:	Fri, 6 Oct 2006 14:20:42 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Duncan Sands <baldrick@...e.fr>
cc:	Pavel Machek <pavel@....cz>, <usbatm@...ts.infradead.org>,
	<linux-usb-devel@...ts.sourceforge.net>, <greg@...ah.com>,
	<linux-kernel@...r.kernel.org>, ueagle <ueagleatm-dev@....org>,
	matthieu castet <castet.matthieu@...e.fr>
Subject: Re: [linux-usb-devel] [PATCH 1/3] UEAGLE : be suspend friendly

On Fri, 6 Oct 2006, Duncan Sands wrote:

> > Maybe UEAGLE can do something a little more sensible...
> 
> What is the modem supposed to do if it receives a packet to
> transmit after it has been told to suspend?  This is a real
> question, I'm not pretending!  I've never thought about or
> read about suspend/resume and have no idea how it is supposed
> to work.  Should it just reject it, or should it wake the
> modem up?

It depends on the context in which the modem was suspended.  If this was a 
regular system sleep transition, or some other suspend request coming from 
outside the driver, then packets should be dropped.

But if the suspend originated within the driver itself, as a power-saving 
measure while the connection was idle, then new packets should cause the 
driver to wake the modem up.  That is, self-originated suspends should be 
transparent.  Outside-originated suspends are someone else's problem.

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