On Fri, 17 Nov 2006, Matthias Drochner wrote:

> With the appended patch the ubt initializes for me, even if usb2/ehci
> is used by the host controller.

yaay

> The "16" happens to be the "wMaxPacketSize" in the endpoint descriptor;
> I'm not sure yet whether it should be the driver's duty to check that
> or the framework should care.

That is a good question - currently ubt provides an event buffer with the
size that is the maximum Bluetooth event packet size and let the usb stack
fill it in.  The wMaxPacketSize will so far as I know be the maximum USB
packet size, so if we only allow for that then we need to cater for
partial Bluetooth packets as some are going to overflow (see hci.h) ..
what happens with this patch for instance when doing a 'btconfig -vvvv' ?
eg, the Read_Local_Name response packet in particular is I think 256 bytes..

I would say though, that since the uhci code does automatically catenate
USB packets into a single transfer (the bluetooth packet), the ehci code
should do that properly also..

> I'm also not sure whether the builtin Dell hub is somehow limited or
> the translation problems are to be expected under the timing/size conditions
> imposed by the ubt driver.

iain