public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: tmm <tmm@fastmail.fm>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Passkey-Agent for bluez 4.xx
Date: Mon, 18 May 2009 18:20:25 -0400	[thread overview]
Message-ID: <4A11DF29.4070408@fastmail.fm> (raw)
In-Reply-To: <88BAD6A2A6AF68449DBBF80948806AC9014F56F0@bb-corp-ex1.corp.cubic.cub>

Wilson, Scott wrote:
> All,
>
> Regarding my earlier post and the reply by James Le Cuirot:
>
>   
>>> My question is, how hard would it be to fix the agent.c code myself?
>>>       
>
>   
>> Most of the work has been done, I believe. You should speak to Alan
>> Carvalho de Assis at acassis@gmail.com.
>>     
>
>   
>> James
>>     
>
> I have some additional questions:
>
> While on the "full" Linux operating system (on a PC), some type of agent
> is installed and executed for me in that environment.  Where is this
> agent coming from?  How is it being executed for me? To my knowledge, I
> have never installed an agent or configured one.
>   
I'm not an expert on this, but I'll try to answer.

Both Gnome and KDE have their own agents, as part of their bluetooth 
management software.

The dbus and bluez on your embedded platform are probably the same as on 
a desktop distro, but this depends on which embedded platform/distro you 
are using.  There is no agent included with dbus or with a standard 
installation of bluez.  Bluez does contain the sample agents that you 
have already found, but they are not installed as part of bluez - they 
are just samples.  So, it's not that the dbus agent gets installed on 
desktop PC and not on embedded - it's that the dbus based agents are not 
really part of dbus, they are part of Gnome or KDE and you are not 
installing those.

Earlier in this thread it was mentioned that someone is already working 
on upgrading the v3 'C' sample agent to v4.  If you don't want to use 
Python then I think that that is what you want.

Tom.

> I can't seem to find many agent interactions in the Bluez code -
> although I find references to it.  Not surprisingly, the main agent
> reference is in test/agent.c.
>
> When I go to execute my project on my embedded device, there is no
> agent.  From all other aspects that I am aware of, the other things
> (dbus, bluez, etc) seem to be similar (my team has already tackled those
> challenges - although some may still remain).
>
> Is it possible that this agent is not included with the dbus that runs
> on the embedded device, but is on the PC?  Does Gnome include this
> agent?  Does it come from the bluetooth-applet?
>
> Any and all comments welcome.  Thank you in advance.
>
> Regards,
>
> Scott Wilson
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   

  parent reply	other threads:[~2009-05-18 22:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 19:21 Passkey-Agent for bluez 4.xx Wilson, Scott
2009-05-18 19:52 ` James Le Cuirot
2009-05-18 21:53   ` Wilson, Scott
2009-05-18 22:16     ` Marcel Holtmann
2009-05-18 22:20     ` tmm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-13 15:55 Artem Makhutov
2009-05-13 15:48 Artem Makhutov
2009-05-14  4:46 ` Brad Midgley
2009-05-16 14:52   ` Artem Makhutov
2009-06-16 13:07   ` John Frankish
2009-06-16 14:30     ` Timothy Murphy
2009-06-17  7:38       ` Johan Hedberg
2009-06-17 12:17         ` Simon Kenyon
2009-06-16 19:21     ` Artem Makhutov
2009-06-17  4:14       ` John Frankish
2009-06-17  7:12         ` Johan Hedberg
2009-06-17 14:15           ` John Frankish
2009-06-17 15:35             ` Brad Midgley
2009-06-17  6:27     ` Brad Midgley
2009-06-17 14:15       ` John Frankish

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=4A11DF29.4070408@fastmail.fm \
    --to=tmm@fastmail.fm \
    --cc=linux-bluetooth@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