From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Franky Lin <frankyl@broadcom.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] brmc80211: dont use jiffies for BSS TSF
Date: Mon, 22 Dec 2014 14:26:52 +0100 [thread overview]
Message-ID: <54981C1C.2020904@broadcom.com> (raw)
In-Reply-To: <1419254074.1890.18.camel@sipsolutions.net>
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
next prev parent reply other threads:[~2014-12-22 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 12:57 [PATCH 0/2] BSS timestamp fix/cleanup Johannes Berg
2012-03-13 12:57 ` [PATCH 1/2] brmc80211: dont use jiffies for BSS TSF Johannes Berg
2012-03-13 18:32 ` Franky Lin
2014-12-22 12:58 ` Johannes Berg
2014-12-22 13:13 ` Arend van Spriel
2014-12-22 13:14 ` Johannes Berg
2014-12-22 13:26 ` Arend van Spriel [this message]
2014-12-24 7:49 ` Arik Nemtsov
2012-03-13 12:57 ` [PATCH 2/2] cfg80211: clarify timestamp in cfg80211_inform_bss Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54981C1C.2020904@broadcom.com \
--to=arend@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).