All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikel Astiz <mikel.astiz@bmw-carit.de>
To: ofono@ofono.org
Subject: Re: Underlying Bluetooth device of a modem
Date: Wed, 10 Aug 2011 17:49:29 +0200	[thread overview]
Message-ID: <4E42A889.30802@bmw-carit.de> (raw)
In-Reply-To: <4E422907.1090304@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]

Hi Denis,

On 08/10/2011 08:45 AM, Denis Kenzior wrote:
> Hi Mikel,
>
> On 08/10/2011 03:46 AM, Mikel Astiz wrote:
>> Hi all,
>>
>> I am trying to set up a simple HFP demonstrator using
>> BlueZ+oFono+PulseAudio, with a dbus client that coordinates the three of
>> them. Being a simple prototype, the goal is to see how they behave and
>> analyze how well it would all scale.
>>
>> The first question that arises is quite simple. In a multi-phone
>> scenario (all of them connected to our PC using Bluetooth HFP), oFono
>> properly lists all the phones as available modems. I would like to know
>> whether these modems can be associated to their underlying bluetooth
>> device (mac address, bluez device dbus path, or whatever). I have been
>> looking on the available modem properties but this seems not to be
>> present. Could somebody confirm this or otherwise explain how it can be
>> done?
>>
> Have a look at the Modem.Name property, HFP_HF plugin sets this based on
> the BlueZ Device.Alias property of the remote device.  Which should be
> either the remote device name or the local alias.  This might actually
> be enough for your purposes.
>
>> The purpose of my interest is that, depending on the use-case, the final
>> user would have to choose the modem (or device) manually.
>>
> Depending on the usecase you might require more information, such as the
> bdaddr of the remote device.  In that case you will have to do a bit
> more work, such as defining a new atom that exports the information you
> require.
>
> Regards,
> -Denis

Thanks for your answer.

I replied to Marcel's message before reading yours so we could hopefully 
merge into one message thread.

One specific point to your answer: the device alias is certainly 
available (and in this case would satisfy the use case of 
manually-select-by-alias, so to speak) but that doesn't seem to scale 
well if you would also like to use other criteria (for example, to 
filter some devices depending on their icon, available services, etc.).

Regards,
Mikel


  reply	other threads:[~2011-08-10 15:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10  8:46 Underlying Bluetooth device of a modem Mikel Astiz
2011-08-10  6:45 ` Denis Kenzior
2011-08-10 15:49   ` Mikel Astiz [this message]
2011-08-10  8:28     ` Denis Kenzior
2011-08-10 13:39 ` Marcel Holtmann
2011-08-10 15:39   ` Mikel Astiz
2011-08-11 22:19   ` Gustavo Padovan
2011-08-11 22:39     ` Marcel Holtmann
2011-08-12  7:21       ` Mikel Astiz
2011-08-12 16:03         ` Marcel Holtmann
2011-08-12 14:16       ` Gustavo Padovan
2011-08-12 16:05         ` Marcel Holtmann

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=4E42A889.30802@bmw-carit.de \
    --to=mikel.astiz@bmw-carit.de \
    --cc=ofono@ofono.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 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.