From: "list subscribe" <develnewbie@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH]Dynamic Alternate Setting patch (hci_usb.c)
Date: Tue, 24 Apr 2007 20:38:40 +0530 [thread overview]
Message-ID: <fc27e74b0704240808j3ca3df0cr5c415d39acf29ac4@mail.gmail.com> (raw)
In-Reply-To: <462E02FB.8000600@vasmac.com>
[-- Attachment #1.1: Type: text/plain, Size: 691 bytes --]
Jose,
Hi Alok,
>
> This is a good start. There are a few other things to consider:
>
> * Are there error conditions in hci_usb_tx_complete that need to be
> handled?
I am not sure what you mean. Since we don't flush submitted URBs, these
URBs are handled like normal ones. If their status indicates error the
error_tx count will be incremented. What error conditions are u pointing at?
* How do you make sure data for different channels is interleaved?
Well , since we know that there can be max 3 SCO channels , we can have 3
separate queues, and use a round robin method to send out the packets from
the queues. i am not sure about this idea though. What do u think?
Jose
>
>
[-- Attachment #1.2: Type: text/html, Size: 1250 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-04-24 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 11:13 [Bluez-devel] [PATCH]Dynamic Alternate Setting patch (hci_usb.c) list subscribe
2007-04-24 13:15 ` Jose Vasconcellos
2007-04-24 15:08 ` list subscribe [this message]
2007-04-24 15:27 ` Jose Vasconcellos
2007-04-24 16:06 ` Marcel Holtmann
2007-04-24 16:13 ` alok
2007-04-24 17:08 ` Jose Vasconcellos
2007-04-24 18:38 ` 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=fc27e74b0704240808j3ca3df0cr5c415d39acf29ac4@mail.gmail.com \
--to=develnewbie@gmail.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