From: Bastien Nocera <hadess@hadess.net>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Add rfkill plugin
Date: Wed, 29 Jul 2009 22:45:36 +0100 [thread overview]
Message-ID: <1248903936.28327.1725.camel@localhost.localdomain> (raw)
In-Reply-To: <20090729214412.GA24031@jh-x301>
On Thu, 2009-07-30 at 00:44 +0300, Johan Hedberg wrote:
> Hi Marcel,
>
> On Wed, Jul 29, 2009, Marcel Holtmann wrote:
> > > > Hijacking the set_powered D-Bus command is the
> > > > wrong approach. We need a properly exported adapter_up() function for
> > > > this.
> > >
> > > I believe I tried exporting adapter_up() but it didn't work.
> >
> > Johan, Luiz, any reason why this would not work. What needs to be done
> > to bring up the adapter. Besides calling the ioctl() directly which we
> > don't wanna do anymore.
>
> adapter_up() is more of a callback that's responsible for doing the
> necessary initializations *after* adapter has just gone up, so it's not
> the right function to call when you want to bring it up (i.e. call the
> ioctl). I believe all code paths for bringing the adapter up call set_mode
> in src/adapter.c which in turn calls adapter_ops->set_powered (which calls
> the ioctl in the case of hciops).
>
> So having a btd_adapter_set_powered exported to plugins (which is what
> Bastien's patch seems to do) makes sense to me in this case. I might
> actually need something similar for maemo in order to handle our offline
> mode better (maemo specific plugin to catch the MCE offline mode signal
> and then call btd_adapter_set_powered).
Hence why it would probably be a good thing to have as a plugin :)
next prev parent reply other threads:[~2009-07-29 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 16:34 [PATCH] Add rfkill plugin Bastien Nocera
2009-07-28 20:06 ` Marcel Holtmann
2009-07-28 20:12 ` Bastien Nocera
2009-07-28 20:21 ` Marcel Holtmann
2009-07-29 15:13 ` Bastien Nocera
2009-07-29 19:49 ` Marcel Holtmann
2009-07-29 20:15 ` Bastien Nocera
2009-07-29 20:23 ` Marcel Holtmann
2009-07-29 20:40 ` Bastien Nocera
2009-07-29 21:44 ` Johan Hedberg
2009-07-29 21:45 ` Bastien Nocera [this message]
2009-07-30 2:10 ` Luiz Augusto von Dentz
2009-07-30 2:27 ` Marcel Holtmann
2009-07-30 2:30 ` Marcel Holtmann
2009-07-30 10:23 ` Johan Hedberg
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=1248903936.28327.1725.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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