From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] HCI USB driver and SCO support
Date: 06 Aug 2003 00:17:14 +0200 [thread overview]
Message-ID: <1060121840.935.25.camel@pegasus> (raw)
In-Reply-To: <5.1.0.14.2.20030805101803.0c38f768@unixmail.qualcomm.com>
Hi Max,
> >the patch from Jonathan Paisley is working fine. I have tested it on
> >2.4.18 to 2.4.21 and we can safely use two ISOC TX and RX URB's by
> >default.
> Yep, I was going to apply his patch.
but without choosing the correct ISOC alternate setting it is useless :(
> >But the configuration of the ISOC endpoint must be adjusted on
> >demand. It depends on the voice setting and number of SCO connections,
> >otherwise you won't hear any sound. At the moment we don't have access
> >to these information from within the driver, so I started to extend the
> >HCI core.
> >
> >The first patch introduces hdev->notify and reads the voice setting on
> >device init and stores them in hdev->voice_setting for later use. With
> >these modification a driver can be notified about added or deleted
> >connections (ACL + SCO) and if the voice setting was changed.
> I like the idea in general.
>
> HCI_CONN_ADD should be something like HCI_NOTIFY_CONN_ADD.
I will change this and push it to my Bitkeeper repository.
> >The second patch is for the HCI USB driver and it shows how to use
> >hdev->notify. It also contains Jonathans modifications to use two ISOC
> >TX and RX URB's and it keeps track of the number of ACL and SCO
> >connections.
> There is no need to count number of connections in the drivert. Core already
> has that counter (conn_hash.num). We just need to extend it to count ACL and
> SCO separately.
Is it worth to change this? The only driver who needs it at the moment
will be hci_usb.o and it can count the stuff by itself.
> >In the next step, we must choose the correct ISOC configuration. The
> >default one should be 0, because we don't use any SCO channel. It is
> >also a good idea to start the ISOC and BULK transfers only if they are
> >needed.
> I think that's the way to go. Driver shouldn't start any BULK or ISOC transfers
> until core tells it so.
I have some successful results with starting and stopping ISOC URB's,
but this code was not based on the hdev->notify architecture.
> btw This stuff should go into 2.6 and not 2.4.
At the moment I switched my development machine back to 2.4, because the
2.6 was out of date (hint) and I have to do the next round of my -mh
patches.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-08-05 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 1:20 [Bluez-devel] HCI USB driver and SCO support Marcel Holtmann
2003-08-02 9:19 ` James Courtier-Dutton
2003-08-04 9:35 ` Marcel Holtmann
2003-08-05 17:48 ` Max Krasnyansky
2003-08-05 22:56 ` James Courtier-Dutton
2003-08-05 17:44 ` Max Krasnyansky
2003-08-05 22:17 ` Marcel Holtmann [this message]
2003-08-05 23:02 ` James Courtier-Dutton
2003-08-06 8:41 ` Marcel Holtmann
2003-08-06 10:23 ` James Courtier-Dutton
2003-08-06 11:07 ` 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=1060121840.935.25.camel@pegasus \
--to=marcel@rvs.uni-bielefeld.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=maxk@qualcomm.com \
/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.