From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [bluetooth-alsa] SCO-FLOWCONTROL patch in the newest kernels
Date: Mon, 10 Sep 2007 21:15:58 +0200 [thread overview]
Message-ID: <1189451758.687.70.camel@violet> (raw)
In-Reply-To: <46DEE2D5.3080804@free.fr>
Hi Fabien,
> > I've applied the
> > http://bluetooth-alsa.cvs.sourceforge.net/bluetooth-alsa/plugz/patches/sco-flowcontrol-v4.2.diff
> > <http://bluetooth-alsa.cvs.sourceforge.net/bluetooth-alsa/plugz/patches/sco-flowcontrol-v4.2.diff>
> > patch on my 2.6.22 kernel to let the SCO protocol works with my
> > bluetooth headset and it works well.
> >
> > Anyway I had some problem during the patching as the kernel wasn't the
> > correct one.
> >
> Indeed they should be updated to apply cleanly on latest 2.6.22 kernel.
> If you can provide an updated version of the patch i would happily push
> it in CVS.
the new audio service support for mono headset doesn't really need this
patch. Eventually we have to have it, but right now the Bluetooth Core
inside the kernel is in a major re-write to remove all the old cruft and
keeping this patch in sync is totally impossible. Once I have the eSCO
support merged upstream then we can talk about it again.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-09-10 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 16:43 [Bluez-devel] [bluetooth-alsa] SCO-FLOWCONTROL patch in the newest kernels Carlo Io
2007-09-05 17:09 ` Fabien Chevalier
2007-09-05 17:13 ` Carlo Io
2007-09-10 19:15 ` 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=1189451758.687.70.camel@violet \
--to=marcel@holtmann.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