All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <sakoman@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] wpa-supplicant - enable CONFIG_CTRL_IFACE_DBUS_NEW in config
Date: Fri, 08 Nov 2013 17:02:31 +0000	[thread overview]
Message-ID: <1383930151.2345.15.camel@ted> (raw)
In-Reply-To: <CAGDS+nkupBrwgBBTbZzSnnB9pjaf2P6gMuQHn6QAZjfkFqi7ww@mail.gmail.com>

On Fri, 2013-11-08 at 07:33 -0800, Steve Sakoman wrote:
> I've begun using Yocto 1.5 (dora) for several client projects over the
> past few weeks.
> 
> I noticed that images that included connman and wpa-supplicant always
> failed to enable the wifi technology properly.  The visible error
> indication in the log:
> 
> src/technology.c:technology_get() No matching drivers found for wifi
> 
> After many hours of debugging I finally figured out that this was due
> to a missing option in wpa-supplicant (CONFIG_CTRL_IFACE_DBUS_NEW)
> 
> Adding a bbappend for wpa-supplicant with this option enabled fixed
> the issue and connman now handles wifi interfaces as expected.
> 
> Was there a particular reason CONFIG_CTRL_IFACE_DBUS_NEW wasn't enabled?

This sounds like a default that should be enabled. Please send a patch!

Cheers,

Richard



  reply	other threads:[~2013-11-08 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 15:33 [RFC] wpa-supplicant - enable CONFIG_CTRL_IFACE_DBUS_NEW in config Steve Sakoman
2013-11-08 17:02 ` Richard Purdie [this message]
2013-11-08 17:05   ` Burton, Ross
2013-11-08 17:54 ` Iorga, Cristian

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=1383930151.2345.15.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sakoman@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.