Re: [Bluez-devel] BlueZ and the ALSA support

[Lars Grunewaldt <lgw@dark-reality.de>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcel Holtmann wrote:
| Hi Lars,
|
|
|>| Do anyone mind if we start using the kernel coding style? It will make
|>| later integration into the kernel or BlueZ so much easier.
|>
|>I definitly won't mind, we'll have to migrate anyway, and sooner is
|>better than later.
|
|
| this is correct, but I won't integrate the current idea of the btsco
| kernel module. In the end it must work without the SCO socket in between
| for sending and receiving the SCO data packets from the HCI. And I like
| to have the eSCO support also. However even I don't have the right test
| hardware for that.

Yes, you already mentioned that before. Depending on the time I'll have
to implement it, it won't be much of a problem to do a complete redesign
of the stuff. As soon as I understand what we'll need... ;)


|>My problem how to change the usb_hci endpoint without killing the n.y.t.
|>urbs is still pending, did you have any new ideas on this?
|
|
| My problem is that I haven't written all of the hci_usb driver code and
| some parts are still so messy that I think a complete rewrite is the
| best that we can do.

I see, did not know that.

| But what I will do is to add a module parameter for
| choosing the alternate setting that can be changed at runtime. To bring
| up a device with a new alternate setting you only have to unplug and
| then plug it in again. This is not the solution we should have, but it
| will help us with testing the SCO stuff without recompiling the kernel
| every time.

Yes, that would be a first step.

I hope I can have a look at the way how usb_hci works, so that I can
understand when an asynchronus/delayed change of the endpoint selection
could happen - or how we could get rid of not-send urbs. *sigh* just
need more time...

don't you think it should be possible to
a) block the submit of new urbs when a change notify has arrived
b) queue until the queue is empty
c) change the endpoint setting and release the block

I don't know to which bad runs or locks this could lead...

cu,
~  Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBoPbzQWC6DTWkDAoRAhDvAJ9OiAlvi1fjivMFchnmb4ehBe53hwCfey+1
UEARQw9ddXYRhewZvKFf014=
=kTD6
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel