From: Chafik Moalem <c.moalem@perdictum.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco/alsa-plugins Kernel 2.6.18-mh7 (and mh4-fch)
Date: Wed, 8 Nov 2006 17:44:56 +0000 (UTC) [thread overview]
Message-ID: <loom.20061108T184308-176@post.gmane.org> (raw)
In-Reply-To: 1111743.1162822095031.JavaMail.root@mail.prologistik.com
Chafik Moalem <Chafik.Moalem <at> perdictum.com> writes:
Dear All,
finally after digging around i found the solution to "alsa-plugin (sco) not
working with 2.6.18-mh>4 kernels ... ("Operation still in progress" ...
opening L2CAP/RFCOMM sockets)
after modifying freshly checkedout btsco sources NOW SCO-ALSASOUND
(plugin-method) WORKS (testet with 2.6.18-mh7-sco AND 2.6.18-mh4-fch ...
but still not chop free :( )
hint : fabien chevalier forgot to take care of EINPROGRESS
(in addition to EAGAIN) in his headsetd sources ...
still to check : his pcm_sco.c ...
and why the timeout parameter has NO effect ...
forget about my previous posting (as no one seems to be interested anyway)
regards,
Chafik
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-08 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 14:08 [Bluez-devel] btsco/alsa-plugins Kernel 2.6.18-mh7 (and mh4-fch) Chafik Moalem
2006-11-08 17:44 ` Chafik Moalem [this message]
2006-11-08 19:54 ` Brad Midgley
2006-11-08 22:19 ` Chafik Moalem
2006-11-09 8:53 ` Chafik Moalem
2006-11-13 15:29 ` Brad Midgley
2006-11-13 16:49 ` Chafik Moalem
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=loom.20061108T184308-176@post.gmane.org \
--to=c.moalem@perdictum.com \
--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