public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Domain Admin <hostmaster@suche.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco2
Date: Wed, 01 Dec 2004 21:22:54 +0100	[thread overview]
Message-ID: <41AE281E.3050908@suche.org> (raw)
In-Reply-To: <41AE065F.9040601@xmission.com>

Brad Midgley wrote:

> Thomas
>
>> a) How should btsco2 Handle Multiple Headset in the Parameter ?
>> - ./btsco2 <mac1> <mac2> <mac3>
>> - ./btsco2 <mac1> -1 <mac2> 1 <mac3> 2
>> Where -1 in the Channel Parameter stand for Autodetec
>
>
> the argument list is fine, but this is showing how we need to improve 
> things. btsco needs to be split into three parts:
>
> * connection processor: keep saved state about what headsets are 
> paired, available, connected, alsa device mappings, etc. We should get 
> it to add a new headset while it's running via dbus events. (We will 
> have to get it to talk to dbus for connect/disconnect events and 
> control anyway)

Currently there is no support for multiple headset because of missing 
arguments. It was an open question how it should be done.
I do not realy like the idee of d-bus for this task. From my point of 
view btsco should be an smal daemon that run with low resources.
This special mean that he should not require an extream set of librarys 
for tasks that can be done faster simpler and easer to read without the 
libs.
1. ALSA till i used btsco i never needed to install libasound to get the 
sound running under linux.
2. The configure script link without check against libptread wich is 
aktuall not used on asound on my system
3. The btsco can be writen with less lines and less memory usage without 
asound/pthread
4. Even the bluetooth stuff is not realy needed but leas overloaded in 
my eyes.

This would make it to what it is an small deamon with no dependecies out 
of the kernel. This is ideal for embeded system.

> * audio processor: the audio processing part of btsco will need to be 
> separated out and put into alsa-lib.

There is no audio processor in the btsco daemon.

>
> * gui for telling the connection processor to 
> discover/add/delete/connect/disconnect to a service on a headset
>
>> c) Is there any Plan to allow th BT-SCO Sound driver in kernel Space 
>> to handle mor than one bluetooth as sound device.
>> Nice would be an option to tell the driver how many sound device he 
>> sould allocate.
>
>
> it's been talked about. I don't exactly understand the problem so I 
> pasted the discussion into the sourceforge bug item.

If  there is an support i will build it in.

Cu Thomas



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-12-01 20:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01  7:39 [Bluez-devel] A2DP working :-) , voice not :-( Sebastian Eichner
2004-12-01  7:54 ` Marcel Holtmann
2004-12-01  8:07   ` Sebastian Eichner
2004-12-01  8:31     ` Marcel Holtmann
2004-12-01  8:43       ` Sebastian Eichner
2004-12-01  9:43         ` Marcel Holtmann
2004-12-01 11:24           ` Sebastian Eichner
2004-12-01 11:31             ` Marcel Holtmann
2004-12-01 16:33               ` Sebastian Eichner
2004-12-01 11:35             ` [Bluez-devel] BTsco suche.org
2004-12-01 11:41               ` Marcel Holtmann
2004-12-01 11:57                 ` suche.org
2004-12-01 12:08                   ` Marcel Holtmann
2004-12-01 14:20                     ` [Bluez-devel] btsco2 Thomas Lußnig
2004-12-01 17:58                       ` Brad Midgley
2004-12-01 20:22                         ` Domain Admin [this message]
2004-12-01 21:32                           ` Brad Midgley
2004-12-01 21:51                             ` Bluetooth
2004-12-01 23:54                               ` Lars Grunewaldt

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=41AE281E.3050908@suche.org \
    --to=hostmaster@suche.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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