From: Johannes Berg <johannes@sipsolutions.net>
To: enh <enh@google.com>
Cc: Filipe Brandenburger <filbranden@google.com>,
Arik Nemtsov <arik@wizery.com>,
linux-wireless@vger.kernel.org,
Christopher Wiley <wiley@google.com>,
Ying Wang <wangying@google.com>
Subject: Re: [PATCH 0/2] iw: fixes to Android.mk to include "iw" in AOSP builds
Date: Thu, 13 Aug 2015 22:01:20 +0200 [thread overview]
Message-ID: <1439496080.2114.39.camel@sipsolutions.net> (raw)
In-Reply-To: <CAJgzZoo3ifnocO84uMLa1=LKQjGWm_J3WTsw0xO2skPG9gDtng@mail.gmail.com> (sfid-20150813_214845_594323_9D52C4AB)
On Thu, 2015-08-13 at 12:48 -0700, enh wrote:
>
> i think you misunderstand what AOSP is. this code is currently in
> AOSP master, and thus in internal master, and thus in a future
> release.
Great, but as I understand it, vendors are under no obligation to
actually ship that code on their devices.
If a vendor needs to have an iw that, for example, supports their own
vendor commands (which, as I understand from the wifihal etc., Google
is basically forcing vendors to have!), then the AOSP iw is useless and
an own version needs to be built.
johannes
next prev parent reply other threads:[~2015-08-13 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 21:35 [PATCH 0/2] iw: fixes to Android.mk to include "iw" in AOSP builds Filipe Brandenburger
2015-07-30 21:35 ` [PATCH 1/2] iw: fix references to libnl in Android.mk Filipe Brandenburger
2015-07-30 21:36 ` enh
2015-07-30 21:47 ` [PATCH v2 " Filipe Brandenburger
2015-07-31 6:55 ` Arik Nemtsov
2015-07-30 21:35 ` [PATCH 2/2] iw: remove android-nl.c with unneeded workaround Filipe Brandenburger
2015-07-31 6:56 ` Arik Nemtsov
2015-07-31 16:01 ` enh
2015-08-02 6:57 ` Arik Nemtsov
2015-08-02 16:11 ` enh
2015-08-13 9:01 ` [PATCH 0/2] iw: fixes to Android.mk to include "iw" in AOSP builds Johannes Berg
2015-08-13 16:55 ` Filipe Brandenburger
2015-08-13 18:33 ` Johannes Berg
2015-08-13 19:48 ` enh
2015-08-13 20:01 ` Johannes Berg [this message]
2015-08-13 20:44 ` enh
2015-08-13 20:47 ` 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=1439496080.2114.39.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arik@wizery.com \
--cc=enh@google.com \
--cc=filbranden@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wangying@google.com \
--cc=wiley@google.com \
/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).