public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Cc: Fred Schaettgen <kde-bluetooth@schaettgen.de>
Subject: Re: [Bluez-devel] Re: [kde-bluetooth] Re: Re: How can I add a new bluetooth service ?
Date: Mon, 17 Jan 2005 00:56:50 +0100	[thread overview]
Message-ID: <41EAFF42.20301@dark-reality.de> (raw)
In-Reply-To: <20050116230927.87008.qmail@web50202.mail.yahoo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just a few comments that where not even asked for :)

just to describe whats happening right now:

we have a small "daemon" that does the whole rfcomm and sco connection
handling (btsco). It listens on rfcomm for the connect/disconnect events
from the headset (button press) and opens/closes sco when needed.

the second part of the whole lot is snd-bt-sco, which handles the
sco-to-audio transmission. This thing will be reworked sooner or later,
we hope it can be a user-space driver AND we want to get rid of the data
transfer loop by connecting alsa and sco socket directly (or converting
the sco socket).

What I always thought about was some way of "communication" between our
btsco daemon that does the connection handling (also should manage
different headsets and stuff like auto-connection on audio-open later),
and I think you might have some suggestions here, Fred.

i.e. an application like gnomemeeting might like to open the headset, or
a tray app could display the status of the headset. For this, the daemon
must support some "connection" thingy. How should this be done? I never
did something like that before, so I don't know... :)

Maybe something simple in /proc or /dev? We won't need much mojo there,
just control for each headset (on/off)

best regards,
~  Lars


Paul Ionescu wrote:
| Hi Fred,
|
| I used the headset with a lot of alsa apps like
| gnomemeeting, mplayer, aso, and non alsa apps thru the
| oss emulation of alsa.
| For gnomemeeting this is just fine because is also
| intended for voice, but to listen to a movie on a 8KHz
| mono headset is not so HiQ.
| Anyway it realy works.
| What I am trying to do is to connect it when I press
| the button on headset and disconnect it when I press
| the button again. So no need for special applet.
| I think that will be nice to put some support for
| btsco in kdebluetooth, but the right person to ask is
| not me.
| Maybe Brad or Lars can give more details of what is in
| the future development for btsco.
| I just modified btsco a bit to be able to use the
| rfcomm connection accepted by kdebluetoothd and did
| some other small changes to better fit my Jabra BT110.
|
| Anyway, if I can help with something, just let me
| know.
|
| Thanks,
| Paul
|
|
| --- Fred Schaettgen <kde-bluetooth@schaettgen.de>
| wrote:
|
|
|>On Sunday 16 January 2005 10:27, you wrote:
|>
|>>--- Fred Schaettgen <kde-bluetooth@schaettgen.de>
|>>wrote:
|>>Hi Fred,
|>>
|>>Yes, I can press the headset button and
|>
|>kbluetoothd
|>
|>>will start a headset connection with btsco.
|>
|>And I can use it with any alsa-capable application?
|>
|>
|>>btsco is from
|>
|>http://bluetooth-alsa.sourceforge.net/
|>
|>>and is a small proof of concept AG profile using
|>>snd-bt-sco which is indeed an alsa bt driver.
|>>So you can connect btsco to a headset but not to a
|>>phone as it does not knows HS or HF profiles.
|>
|>Ah, got it.. I thought btsco handles only the SCO
|>connection, but this can
|>hardly work. Do you think it would make sense to
|>integrate headset support
|>into kdebluetooth at this point?
|>If it works already, the only thing that's missing
|>is a little tray icon,
|>where the user can terminate the headset connection.
|>Problem is snd-bt-sco
|>isn't shipped with the stock kernel. But on the
|>other hand it could help
|>making snd-bt-sco more popular if we support it in
|>kdebluetooth. What's you
|>opinion?
|


- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB6v9BQWC6DTWkDAoRAl6vAJ95UtPcSOr4sl0ap6YDqUU317iT5gCgsE4b
K+3bSnyFJB7d2niiLrrQoaI=
=/l1/
-----END PGP SIGNATURE-----


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-01-16 23:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200501162201.57611.kde-bluetooth@schaettgen.de>
2005-01-16 23:09 ` [Bluez-devel] Re: [kde-bluetooth] Re: Re: How can I add a new bluetooth service ? Paul Ionescu
2005-01-16 23:56   ` Lars Grunewaldt [this message]

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=41EAFF42.20301@dark-reality.de \
    --to=lgw@dark-reality.de \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=kde-bluetooth@schaettgen.de \
    /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