From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] SCO flow control
Date: Sat, 10 Jun 2006 11:24:23 +0200 [thread overview]
Message-ID: <448A8FC7.5010401@free.fr> (raw)
In-Reply-To: <1149884263.3985.10.camel@aeonflux.holtmann.net>
Hi Marcel,
>> I'm not against this, even if it means more work...
>
> I think it will be worth it.
>
>> However i don't have any precise idea on which communication mechanism
>> to use between userspace/kernelspace. Any ideas ??
>
> We might leave the socket for now. The alternative is a character device
> or directly an ALSA sound card. Haven't fully thought about it either.
For the ALSA sound card, this is basically what snd-bt-sco does. The
issue with this alternative, is that the headset&handsfree profile
mandates the use of an RFCOMM channel before to use SCO. Doing this at
kernel level will mean that SCO layer will be dependant on RFCOMM
sockets, or that user space will have to handle RFCOMM channel before to
open ALSA device. This is roughly the way btsco works today. The result
is not very pretty :-(
>
>>> Let's have another patch on top of 2.6.16-mh1 and maybe you also wanna
>>> adapt scotest for testing it.
>>>
>> Ok, i'm gonna work on that then...
>
> The 2.6.16-mh2 is missing the automatic sniff mode patch, but only for
> testing. It is coming back for sure.
Ok, i will stick with mh1 then....
Cheers,
Fabien
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-10 9:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 19:46 [Bluez-devel] [PATCH] SCO flow control Fabien Chevalier
2006-05-29 20:33 ` Marcel Holtmann
2006-05-29 21:39 ` Pieter Poorthuis
2006-05-29 22:21 ` Marcel Holtmann
2006-05-30 13:28 ` Fabien Chevalier
2006-06-01 19:15 ` Marcel Holtmann
2006-06-07 20:15 ` Fabien Chevalier
2006-06-07 20:30 ` Marcel Holtmann
2006-06-09 17:05 ` Fabien Chevalier
2006-06-09 20:17 ` Marcel Holtmann
2006-06-10 9:24 ` Fabien Chevalier [this message]
2006-06-10 22:22 ` Marcel Holtmann
2006-06-10 9:59 ` Fabien Chevalier
2006-06-10 23:14 ` Marcel Holtmann
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=448A8FC7.5010401@free.fr \
--to=fabchevalier@free.fr \
--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;
as well as URLs for NNTP newsgroup(s).