From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Esco implementation patch
Date: Thu, 03 May 2007 07:25:28 +0200 [thread overview]
Message-ID: <1178169928.6891.39.camel@violet> (raw)
In-Reply-To: <200705031357.04459.denis.kenzior@trolltech.com>
Hi Denis,
> Here's a modified patch that implements eSCO sockets, including incoming SCO
> connections. This was a merge of my previous work for the 2.4 series of
> kernels, so some variables might be named differently than in your patch.
please make sure you use my naming of variables. Otherwise it is too
much confusion. And please create a patch relative to this one so I can
actually review it. And please keep hci_setup_sync(). Doing the
separation this way it more logical than hacking up hci_add_sco(). The
function that decides which command to use should be hci_connect().
> > this patch is incomplete. It doesn't handle incoming eSCO connections
> > and it can't handle SCO audio packets over HCI when a real eSCO
> > connection has been established.
>
> Why do you say this? What is required in order to get eSCO packets flowing?
If you have type == ESCO_LINK then the kernel doesn't send these packets
over the transport layer.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-05-03 5:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 6:58 [Bluez-devel] Esco implementation patch Sumeet VERMA
2007-04-25 7:44 ` Marcel Holtmann
2007-04-26 4:56 ` Sumeet VERMA
2007-04-26 5:19 ` Denis KENZIOR
2007-04-26 6:24 ` Mayank BATRA
2007-04-26 6:29 ` Sumeet VERMA
2007-04-26 10:19 ` dkenzior
2007-04-26 10:36 ` Sumeet VERMA
2007-04-26 14:18 ` Marcel Holtmann
2007-04-26 19:40 ` Marcel Holtmann
2007-04-27 7:50 ` Sumeet VERMA
2007-05-01 11:24 ` Marcel Holtmann
2007-05-03 3:57 ` Denis KENZIOR
2007-05-03 4:38 ` Mayank BATRA
2007-05-03 5:00 ` Denis KENZIOR
2007-05-03 5:16 ` Marcel Holtmann
2007-05-03 5:23 ` Mayank BATRA
2007-05-03 5:29 ` Marcel Holtmann
2007-05-03 5:24 ` Denis KENZIOR
2007-05-03 5:28 ` Marcel Holtmann
2007-05-03 5:25 ` Marcel Holtmann [this message]
2007-05-04 7:36 ` Denis KENZIOR
2007-05-04 8:53 ` [Bluez-devel] sdpd and multiple bluetooth devices Olivier Le Pogam
2007-05-04 9:18 ` 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=1178169928.6891.39.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.