From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-gw1-out.broadcom.com ([216.31.210.62]:35711 "EHLO mail-gw1-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754595AbaLVN0y (ORCPT ); Mon, 22 Dec 2014 08:26:54 -0500 Message-ID: <54981C1C.2020904@broadcom.com> (sfid-20141222_142657_368101_C732ED68) Date: Mon, 22 Dec 2014 14:26:52 +0100 From: Arend van Spriel MIME-Version: 1.0 To: Johannes Berg CC: Franky Lin , Subject: Re: [PATCH 1/2] brmc80211: dont use jiffies for BSS TSF References: <20120313125702.703540202@sipsolutions.net> <20120313125919.370791280@sipsolutions.net> (sfid-20120313_140421_642123_6BC8E250) <1419253089.1890.13.camel@sipsolutions.net> <549818FE.1090707@broadcom.com> <1419254074.1890.18.camel@sipsolutions.net> In-Reply-To: <1419254074.1890.18.camel@sipsolutions.net> Content-Type: text/plain; charset="UTF-8"; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 12/22/14 14:14, Johannes Berg wrote: > On Mon, 2014-12-22 at 14:13 +0100, Arend van Spriel wrote: >> On 12/22/14 13:58, Johannes Berg wrote: >>> By the way - I know now that the proprietary Broadcom driver has the >>> same bug, to the point where this is apparently getting encoded into the >>> Android framework. >>> >>> I urge you to fix this issue there as well. If an absolute "last >>> updated" timestamp is needed (and "last seen [ms] ago" isn't sufficient) >>> then new API will be needed. >> >> Sorry, seem to have missed the original patches somehow. Guess because >> it says *brmc*80211. > > No no - it's a looong time ago and was also applied a long time ago. It > just reared it's head again in another place. Found the commit in git log. So you mean the proprietary DHD driver or Android bcmdhd still uses host timestamp. I agree it should be fixed, but I may need some good arguments to convince my co-workers. So what kind of issues are rearing their (ugly) heads? supplicant issues? Regards, Arend