From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] question about hci_usb endpoint selection...
Date: Thu, 14 Oct 2004 23:50:40 +0200 [thread overview]
Message-ID: <416EF4B0.6070802@dark-reality.de> (raw)
In-Reply-To: <1097752849.4640.37.camel@notepaq>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marcel Holtmann wrote:
| look at the hci_usb driver and add the notify() callback function for
| it. This function gets called when you change the voice setting or a new
| connection is added or removed. I changed the connection hash to count
| the ACL and SCO links separatly and disabled the tasklet when calling
| this function so that the core stops processing TX packets and enable it
| after the driver finished anything it has to do.
Hi there,
OK, I added hci_usb_notify(..) and it works as it should (get's the
notify when voice mode is changed).
Now for the "real stuff"... :)
I think to handle the voice mode change correctly, I have to duplicate
the code from about line 874..922 that locates the "proper" alternate
setting; before this can happen, the notify function must close
((husb *)hdev->driver_data)->isoc_iface with
usb_driver_release_interface(...)
is there anything else to do? Must some buffers be dropped or free'd or
something? is it possible to simply re-set
isoc_iface, isoc_in_ep and isoc_out_ep?
Or is it in fact not neccesary to disconnect isoc_iface and only change
the values of isoc_in_ep and isoc_out_ep?
I don't know much about the usb internals, so I ask the list again.
Thanks very much for bringing this topic forward :))
cu,
~ Lars
PS: one last question, I'm using kernel 2.6.8.1 now and hci_usb.c uses
CONFIG_BT_HCIUSB_DEBUG to enable/disable debugging; my kernel config
says this option does not exists, so, how to enable debugging properly?
Or is just the option accidently missing from kernel config in this release?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBbvSwQWC6DTWkDAoRArROAJ9ita8X+pxnxEDeH6f2iU4JUbMsDACfbao5
F0MQVzgEB8guoBDKw/McCbU=
=iJew
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-10-14 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 12:46 [Bluez-devel] question about hci_usb endpoint selection Lars Grunewaldt
2004-10-14 11:20 ` Marcel Holtmann
2004-10-14 21:50 ` Lars Grunewaldt [this message]
2004-10-16 12:06 ` Marcel Holtmann
2004-10-16 16:19 ` Lars Grunewaldt
2004-10-17 11:41 ` Marcel Holtmann
2004-10-17 14:15 ` Lars Grunewaldt
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=416EF4B0.6070802@dark-reality.de \
--to=lgw@dark-reality.de \
--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