From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SCO packet processing
Date: Tue, 03 Oct 2006 21:30:49 -0600 [thread overview]
Message-ID: <45232AE9.40605@xmission.com> (raw)
In-Reply-To: <4521D857.8000705@vasmac.com>
Jose
> I realize SCO handling has not been a priority and it sort of works.
> Is there much interest in getting it right?
I'm very interested in it but I've only been able to address the
application side of things. It looks like you've dug in and reached a
decent understanding of where problems are.
Developers of embedded systems are passing linux/bluez over because
voice is too important to just have it "mostly" work.
It's unfortunate that Fabien is not still working at it too. I was
hoping he would keep a dialog going long enough to find an approach that
Marcel likes but it seems like Fabien got tired of pushing it.
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-10-04 3:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 3:26 [Bluez-devel] SCO packet processing Jose Vasconcellos
2006-10-04 3:30 ` Brad Midgley [this message]
2006-10-04 8:27 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2006-10-03 1:05 Jose Vasconcellos
2006-10-04 8:33 ` Marcel Holtmann
2006-10-04 12:00 ` Jose Vasconcellos
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=45232AE9.40605@xmission.com \
--to=bmidgley@xmission.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