From: Marcel Holtmann <marcel@holtmann.org>
To: Jonathan Paisley <jp-www@dcs.gla.ac.uk>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Bluetooth update for 2.4.23-pre2
Date: 13 Oct 2003 11:28:58 +0200 [thread overview]
Message-ID: <1066037344.8024.196.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.54.999.0310121324110.10464@sibu.dcs.gla.ac.uk>
Hi Jonathan,
> > the ALSA support is not the point, because you can use the SCO socket
> > for 2.4 for now and it is working fine for me. I think we should drop
> > this for 2.4.23 and wait until 2.4.24-pre.
>
> Have you had a chance to try or look at my snd-bluez-sco ALSA driver yet?
> I'm interested to hear your thoughts on its design.
>
> http://www.dcs.gla.ac.uk/~jp/snd-bluez-sco/
I have looked at your code, but never tested it. However it looks fine
and it seems that some people got success with it. What I don't like is
that it is build on top of the SCO sockets. I raised this a long time
ago and what I expect from a good Bluetooth audio integration is direct
interface to OSS and ALSA. I think of something we have done for RFCOMM,
which means that we integrate all stuff directly into the sco.o module.
Linux 2.4 SCO socket + OSS interface
Linux 2.6 SCO socket + OSS/ALSA interface
I am not an audio or ALSA expert, so don't expect to much from me in
this area. And the 2.6 looks like a good starting point to redesign our
SCO interface. I would say that you should go ahead and try to do it ;)
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2003-10-13 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1062432872.13729.185.camel@pegasus>
2003-09-12 17:44 ` Bluetooth update for 2.4.23-pre2 Max Krasnyansky
2003-09-12 22:48 ` [Bluez-devel] " Marcel Holtmann
2003-10-09 1:12 ` Max Krasnyansky
2003-10-09 16:13 ` [Bluez-devel] " Marcel Holtmann
2003-10-09 17:45 ` Max Krasnyansky
2003-10-09 18:24 ` Marcel Holtmann
2003-10-12 12:25 ` Jonathan Paisley
2003-10-13 9:28 ` Marcel Holtmann [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=1066037344.8024.196.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jp-www@dcs.gla.ac.uk \
--cc=maxk@qualcomm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.