On 18.09.2015 23:25, Oliver Neukum wrote:
On Fri, 2015-09-18 at 09:56 -0700, Laura Abbott wrote:
Would you rather see a revert of the patch you gave rather than a new
one re-introducing the flag?
We need a big fat comment here saying that different tests should
different results and the quirk
On 10.09.2015 20:27, Laura Abbott wrote:
We received several reports of systems rebooting and powering on
after an attempted shutdown. Testing showed that setting
XHCI_SPURIOUS_WAKEUP quirk in addition to the XHCI_SPURIOUS_REBOOT
quirk allowed the system to shutdown as expected for Lynxpoint
On Fri, 2015-09-18 at 09:56 -0700, Laura Abbott wrote:
> Would you rather see a revert of the patch you gave rather than a new
> one re-introducing the flag?
We need a big fat comment here saying that different tests should
different results and the quirk is needed for LynxPoint. That
suggests a
On Fri, 2015-09-18 at 13:18 +0300, Mathias Nyman wrote:
> Better ask Oliver,
> Do you still have access to the HP laptop?
No I am sorry, we no longer have those laptops.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body
On 09/18/2015 03:18 AM, Mathias Nyman wrote:
On 10.09.2015 20:27, Laura Abbott wrote:
We received several reports of systems rebooting and powering on
after an attempted shutdown. Testing showed that setting
XHCI_SPURIOUS_WAKEUP quirk in addition to the XHCI_SPURIOUS_REBOOT
quirk allowed the
We received several reports of systems rebooting and powering on
after an attempted shutdown. Testing showed that setting
XHCI_SPURIOUS_WAKEUP quirk in addition to the XHCI_SPURIOUS_REBOOT
quirk allowed the system to shutdown as expected for Lynxpoint
xHCI controllers. Set the qurik.
