From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <768ca0186288f2fe3f6694478893d5bb@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Wed, 23 Sep 2009 15:37:31 +0100
In-Reply-To: <2b105286d2f8b70838f318889c1bd87b@9netics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] bluetooth
Topicbox-Message-UUID: 76214e82-ead5-11e9-9d60-3106f5b1d025

> anyone looked at this or given it any thought?

I've been working on a bluetooth implementation which should be
ready for initial release soon.  Just the core communication layers
(usb-hci transport, hci, l2cap, rfcomm), and fairly rudimentary:
I've tried to pick a minimal useful subset rather than support
the whole 1420-page Core V2.1+EDR standard.

The interface follows the normal Plan 9 /net model, so the usual
dial/announce/listen operations work pretty much as expected,
and you can do things like:

  aux/listen1 bt!*!77 /bin/exportfs
  import -A bt!00123456789A!77 / /n/blue

A bit of tweaking to cs(8) would allow the use of "friendly"
device names in place of 12-hexdigit bluetooth device addresses.