9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: dave.l@mac.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] bluetooth
Date: Thu, 24 Sep 2009 21:40:24 +0100	[thread overview]
Message-ID: <2F973DDF-361B-4043-B202-F8B27FC3C108@mac.com> (raw)
In-Reply-To: <dd4f9d03a058b551aced7fabeb635ad1@hamnavoe.com>

Thanks a million for all your work on this:
it means I'll probably be running plan9 seriously soon:-).

To be selfish for a moment ...
Presumably there's still a medium sized asteroid of pain to go through
to get something like,
say, my bluetooth stereo-phones+headset(A2DP/AVRCP/... ... ...)
working sensibly?

Oh, and we'll need more drivers which will need to be more complex and
more efficient and less buggy
while driving more, and more divergent hardware which is becoming ever
more complex and bigger and buggier,
of course.

OTOH, of course, we do at least have the wonderfully clean plan9 view
of all this contortionous mess,
so at least when I need to push an avrcp driver onto my stack,
I can manipulate and see the hideous vipers nest in userland and prod
it with rc.

Plus, of course, it'll be totally dandy for connecting my plan9
wristputer to my plan9 briefcase.

Well done again.


On 23 Sep 2009, at 15:48, Richard Miller wrote:

>> A very superficial glance a long time ago suggested that it was a
>> twisty little maze of de-facto and de-vulgus standards.
>> i.e. the death of a thousand committees.
> The core standard (defining the communication layers) is actually
> not too bad, compared to some I've had to look at.  It's huge, but
> a lot of it is describing low-level radio stuff (below the hci layer)
> which your bluetooth chip takes care of.
> All the "profiles" (application layers) have their own separate
> standards documents, and there indeed is a morass of (non)design
> by committee.
>> Then there's the hardware ...
> Maybe I was lucky, but my random choice of development hardware
> (a cheap generic usb dongle with a CSR chip) has seemed to behave
> just as the spec says.  Of course there have been surprises, but
> so far these have been where the spec was ambiguous and my guess
> didn't match the firmware designer's guess.

  reply	other threads:[~2009-09-24 20:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 19:34 Skip Tavakkolian
2009-09-22 22:33 ` Patrick Kelly
2009-09-23  0:53 ` dave.l
2009-09-23 14:48   ` Richard Miller
2009-09-24 20:40     ` dave.l [this message]
2009-09-25 10:48       ` Richard Miller
2009-09-23 14:37 ` Richard Miller
2009-09-23 16:10   ` Skip Tavakkolian
2009-09-23 17:54   ` Skip Tavakkolian
2009-09-23 17:57     ` Francisco J Ballesteros
2009-09-23 18:11     ` Richard Miller
2009-09-23 20:57       ` Skip Tavakkolian
2009-09-24  4:33         ` lucio
2009-09-24  8:22         ` Richard Miller
2009-09-24 11:03           ` Nathaniel W Filardo
2009-09-24 13:59             ` Richard Miller
2009-09-24 20:05               ` Steve Simon
2009-09-25 10:23                 ` Richard Miller
2009-09-24 15:30           ` rsc
2009-09-24 15:57             ` Richard Miller
2009-09-24 19:06           ` Skip Tavakkolian
2009-09-25 10:11             ` Richard Miller
2009-09-25 11:30               ` matt
2010-04-26 18:09           ` Skip Tavakkolian
2022-03-19 19:05 [9fans] Perhaps someone can give me an advice Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-03-19 19:52 ` [9fans] bluetooth Richard Miller

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2F973DDF-361B-4043-B202-F8B27FC3C108@mac.com \
    --to=dave.l@mac.com \
    --cc=9fans@9fans.net \
    --subject='Re: [9fans] bluetooth' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).