From: Fabien Chevalier <fabchevalier@free.fr>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Question for Marcel (& maybe others)
Date: Thu, 25 May 2006 22:15:29 +0200 [thread overview]
Message-ID: <44761061.1000804@free.fr> (raw)
Hi All, (and as stated, especially Marcel)
There is an item in the TODO list concerning SCO audio:
"Full support for SCO connections with the HCI USB driver"
Could you please provide me some details on the missing bits ?
Cheers,
Fabien
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-05-25 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 20:15 Fabien Chevalier [this message]
2006-05-29 13:10 ` [Bluez-devel] Question for Marcel (& maybe others) Marcel Holtmann
2006-05-29 17:41 ` Fabien Chevalier
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=44761061.1000804@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).