From: Jordan Crouse <jordanc@censoft.com>
To: "Herman Oosthuysen" <Herman@WirelessNetworksInc.com>,
"Galappatti, Kishantha" <Kishantha.Galappatti@gs.com>,
"'lkml'" <linux-kernel@vger.kernel.org>
Subject: Re: Bluetooth support on Linux
Date: Wed, 12 Dec 2001 15:28:37 -0700 [thread overview]
Message-ID: <E16EHvT-0004D1-00@ns.censoft.com> (raw)
In-Reply-To: <D28C5BE01ECBD41198ED00D0B7E4C9DA08E1AF3A@gsny31e.ny.fw.gs.com> <000701c1835b$5cca29e0$0100007f@localdomain.wni.com.wirelessnetworksinc.com>
In-Reply-To: <000701c1835b$5cca29e0$0100007f@localdomain.wni.com.wirelessnetworksinc.com>
ut a generic Bluetooth driver isn't something that can
> easily be included in the Kernel itself, since the modules are still
> evolving too rapidly.
I disagree. Between the Bluez and Affix projects, it is just as easy to
write a new bluetooth driver as it is to write an new ethernet or sound
driver. I worked on a Bluetooth project recently (using the Bluez stack),
and everything was very easy and it worked flawlessly (thanks to Maksim
Krasnyanskiy and his team).
What's missing right now are the user land applications to make the bluetooth
more useful. The Windows world is replete with cute little programs that
make sonar noises while they discover, and provide simple user interfaces for
printing and whatever little else the Windows box allows. While our
functionality is all there, we have no auto discovery, and no easy way for
users to get discovered and connected.
With a little effort in the user's direction, bluetooth could be a very
useful thing. And since Microsoft has chosen not to provide a bluetooth
stack of their own (at least not in XP), Linux has the potential to be *the*
OS when it comes to Bluetooth.
Jordan
next prev parent reply other threads:[~2001-12-12 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 21:43 Galappatti, Kishantha
2001-12-12 22:21 ` Herman Oosthuysen
2001-12-12 22:28 ` Jordan Crouse [this message]
2001-12-12 22:09 Peter Kjellerstedt
2001-12-13 0:08 Peter Kjellerstedt
2001-12-13 11:20 Dmitri.Kassatkine
2001-12-13 14:31 berthiaume_wayne
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=E16EHvT-0004D1-00@ns.censoft.com \
--to=jordanc@censoft.com \
--cc=Herman@WirelessNetworksInc.com \
--cc=Kishantha.Galappatti@gs.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®