All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@mozilla.com>
To: linux-bluetooth@vger.kernel.org
Cc: Shawn Huang <shuang@mozilla.com>
Subject: Extending BlueZ's HAL protocol
Date: Fri, 30 Jan 2015 14:07:01 +0100	[thread overview]
Message-ID: <54CB81F5.3000401@mozilla.com> (raw)

Hello,

On Mozilla's Firefox OS, we use a daemon for running Bluedroid drivers
in their own address space, and communicate with the daemon via BlueZ's
HAL protocol. [1]

We'd like to use the HAL protocol as-is, but several commands are not
defined in the spec. We especially ran into this problem with
Bluedroid's |bt_interface_t::config_hci_snoop_log|. BlueZ has a
completely different mechanism for handling the command and probably
won't ever require an opcode for it. Just adding an opcode for
|config_hci_snoop_log| to our code base will probably collide with BlueZ
official spec in the long run.

Our proposal is to reserve two opcodes per service for extensions to
commands and notifications. This would allow us to add the missing
pieces without opcode collisions.

Best regards
Thomas

[1]
https://git.kernel.org/cgit/bluetooth/bluez.git/tree/android/hal-ipc-api.txt

             reply	other threads:[~2015-01-30 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 13:07 Thomas Zimmermann [this message]
2015-01-30 17:59 ` Extending BlueZ's HAL protocol Marcel Holtmann
2015-02-03  8:34   ` Thomas Zimmermann
2015-02-03 13:47     ` Marcel Holtmann
2015-02-06 12:04       ` Thomas Zimmermann
2015-02-06 14:56         ` Luiz Augusto von Dentz

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=54CB81F5.3000401@mozilla.com \
    --to=tzimmermann@mozilla.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=shuang@mozilla.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.