From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: wei.tee.ng@intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] recipes-connectivity: Add hostapd configuration for enabling Marvell 8897 WiFi feature
Date: Mon, 27 Jul 2015 15:03:39 +0100 [thread overview]
Message-ID: <1438005819.821.255.camel@linuxfoundation.org> (raw)
In-Reply-To: <1436418620-16592-2-git-send-email-wei.tee.ng@intel.com>
On Thu, 2015-07-09 at 13:10 +0800, wei.tee.ng@intel.com wrote:
> From: Ng Shui Lei <shui.lei.ng@intel.com>
>
> Hostapd features was created in the recipes-connectivity
> layer to enable Marvell 8897 module in AP mode and STA mode.
>
> Signed-off-by: Ng Shui Lei <shui.lei.ng@intel.com>
> Signed-off-by: Ng Wei Tee <wei.tee.ng@intel.com>
> ---
> .../hostapd/hostapd-2.2/defconfig | 145 ++++++++++++++++++++
> .../hostapd/hostapd-2.2/hostapd.service | 11 ++
> meta/recipes-connectivity/hostapd/hostapd-2.2/init | 58 ++++++++
> meta/recipes-connectivity/hostapd/hostapd_2.2.bb | 48 +++++++
> 4 files changed, 262 insertions(+)
> create mode 100644 meta/recipes-connectivity/hostapd/hostapd-2.2/defconfig
> create mode 100644 meta/recipes-connectivity/hostapd/hostapd-2.2/hostapd.service
> create mode 100644 meta/recipes-connectivity/hostapd/hostapd-2.2/init
> create mode 100644 meta/recipes-connectivity/hostapd/hostapd_2.2.bb
I'm by no means a comms expert which is one of the reasons I've not
replied to this, I'd hoped someone with more knowledge would. Part of
the issue here is that hostapd and connmand have overlapping
functionality, conflicting in some cases.
So the question is why do we need hostapd if we have connman (which is
already in OE-Core)?
Cheers,
Richard
next prev parent reply other threads:[~2015-07-27 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 5:10 [PATCH 0/2] [master][dizzy] Enable Marvel 8897 Wifi feature wei.tee.ng
2015-07-09 5:10 ` [PATCH 1/2] recipes-connectivity: Add hostapd configuration for enabling Marvell 8897 WiFi feature wei.tee.ng
2015-07-27 14:03 ` Richard Purdie [this message]
2015-07-09 5:10 ` [PATCH 2/2] recipes-connectivity: Add iw " wei.tee.ng
2015-07-27 14:07 ` Richard Purdie
2015-07-21 1:32 ` [PATCH 0/2] [master][dizzy] Enable Marvel 8897 Wifi feature Ng, Wei Tee
2015-07-27 5:21 ` Ng, Wei Tee
2015-07-27 16:41 ` Otavio Salvador
2015-07-27 18:15 ` Hugo Vasconcelos Saldanha
2015-07-27 18:28 ` Otavio Salvador
2015-07-27 18:45 ` Burton, Ross
2015-07-28 9:24 ` Ng, Wei Tee
2015-07-27 18:47 ` Hugo Vasconcelos Saldanha
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=1438005819.821.255.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=wei.tee.ng@intel.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