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

[Marcel Holtmann <marcel@holtmann.org>]

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.

> 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. 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.

Regards

Marcel




-------------------------------------------------------
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