From: "Nicholas A. Preyss" <nalp@gmx.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] questions about BT audio headset support...
Date: Fri, 7 May 2004 16:19:28 +0200 [thread overview]
Message-ID: <20040507141928.GA4058@gmx.net> (raw)
In-Reply-To: <409B833B.8070203@superbug.demon.co.uk>
On 0, James Courtier-Dutton <James@superbug.demon.co.uk> wrote:
> Nicholas A. Preyss wrote:
> >In my opinion, the whole connection handling should be done in
> >user-space. In kernel-space only a generic "sco channel" - "alsa device"
> >binding interface should stay.
>
> I think it might be worth trying to find out if one can get alsa-lib to
> use a user-space device driver. Then everything will stay in user space
> until it reaches the bluez code.
This means alot of rather useless kernelspace-userspace-kernelspace
copying. Looking at Marcels hstest program, there is a quiet large lag,
i am not sure, how much you could reduce this with an optimized direct
alsa interface.
nicholas
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-05-07 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 0:12 [Bluez-devel] questions about BT audio headset support Lars Grunewaldt
2004-05-07 11:30 ` Nicholas A. Preyss
2004-05-07 12:38 ` James Courtier-Dutton
2004-05-07 14:19 ` Nicholas A. Preyss [this message]
2004-05-07 15:10 ` 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=20040507141928.GA4058@gmx.net \
--to=nalp@gmx.net \
--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