public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Richi Plana <richip@richip.dhs.org>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Bluez / Bluetooth Docs
Date: Tue, 21 Oct 2008 16:03:11 -0600	[thread overview]
Message-ID: <48FE519F.9070409@richip.dhs.org> (raw)
In-Reply-To: <1224550188.21866.9.camel@richip.dhs.org>

Any pointers? Other mailing lists? IRC channels? There's nothing on the 
bluez website.

Richi Plana wrote:
> Hi,
>
> My apologies in advance for the slightly off-topic post.
>
> Working under the assumption that one can't bind two BT headsets to one
> BT adapter (device or whatever the correct term is), I've made available
> two BT adapters on my notebook (one USB dongle) and am now trying to
> pair one headset with one device. The problem is I've no idea how this
> works outside of the automagic that Fedora does (using hcid).
>
> My question is where can I find documentation that covers the concepts
> behind bluetooth on linux, specifically the bluez implementation. I've
> checked out www.bluez.org and downloaded the latest packages, but they
> don't contain documentation on how things are supposed to work (which
> daemons or utils do what).
>
> Are there official docs available that explains the infrastructure and
> tools to a newbie? If not official, could someone point me out to a good
> set of docs that might get me on my way?
>
> Thanks.
> --
>
> Richi
>
> --
> 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
>
>   


  reply	other threads:[~2008-10-21 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21  0:49 Bluez / Bluetooth Docs Richi Plana
2008-10-21 22:03 ` Richi Plana [this message]
2008-10-21 22:29   ` David Sainty

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=48FE519F.9070409@richip.dhs.org \
    --to=richip@richip.dhs.org \
    --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