From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: About the alx WoL feature Date: Tue, 22 May 2018 09:44:57 +0200 Message-ID: <1526975097.6787.4.camel@sipsolutions.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Emily Chien , Andrew Lunn , David Miller , Anthony Wong , netdev@vger.kernel.org, Johannes Stezenbach To: AceLan Kao Return-path: Received: from s3.sipsolutions.net ([144.76.63.242]:51038 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750709AbeEVHpG (ORCPT ); Tue, 22 May 2018 03:45:06 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: +netdev Hi, > Sorry to write to you directly, I'm not sure if I should CC some > public lists, please feel free to add them if that's the right way to > do. I think it is, adding netdev. > I would like to add back the alx WoL feature which is reverted by you > 5 years ago, and we have some discussions here[1] and here[2]. [...] > 1. https://patchwork.kernel.org/patch/10331135/ > 2. https://patchwork.kernel.org/patch/10396651/ > David Miller insists to fix the wake up issue before we can add this > feature back, Rightfully so! > so I'm wondering if you still have the machine which can > reproduce the wake up issue or know who might have the machine and > willing to help. I still have the machine that I initially did this development on, but it's been purposed as my NAS so testing on it is somewhat awkward. However, as far as I remember (why the hell are you doing this 5 years later?!) the problem never occurred on my machine. Perhaps on Johannes Stezenbach's machine? I don't recall, but see emails in my inbox from him related to alx WoL. > We can try contacting Qualcomm and/or Rivet Network to sort out the issue. Good luck with that, heh. johannes