Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Mar 2003 12:08:25 -0800
From:      Maksim Yevmenkin <myevmenk@exodus.net>
To:        ticso@cicely.de
Cc:        ticso@cicely9.cicely.de
Subject:   Re: Ax88172 vs FreeBSD USB stack
Message-ID:  <3E84ABB9.4090708@exodus.net>
References:  <20030328183858.7B2DB37B401@hub.freebsd.org> <20030328185650.GK23168@cicely9.cicely.de> <3E849FA7.1000400@exodus.net> <20030328193719.GN23168@cicely9.cicely.de>

next in thread | previous in thread | raw e-mail | index | archive | help
>>ng_ubt(4) (/sys/netgraph/bluetooth/drivers/ubt) driver
>>(Bluetooth USB devices) makes use of two interfaces.
> 
> From a look into the driver these interfaces serve different
> protocols.

not sure what do you mean by protocol here. interface 0 has
control, interrupt, bulk-in and bulk-out endpoints. interface
1 has isoc-in and isoc-out endpoints. also interface 1 has
5 different configurations (w/different packet sizes) allowing
isoc. bandwidth scaling.

> I asume they are unrelated from a logical standpoint, but I don't
> know bluetooth technology.

they are. interface 0 is used to control device (control/interrupt
transfers) and to transfer data (via bulk-in/out transfers). interface
1 is used to transfer voice (via isoc. transfers).

> We have a similar situation with ulpt, where we usually have up
> to three interfaces with different capabilities.
> ulpt currently pics one of them, but we could also have three different
> ulpt instances taking each one of them.

it is not exactly the same here. the device can only perform

1) data transfers
2) data transfers + voice transfers

> Well the AC88172 PDF is very clear about having 2 interfaces.
> The document also speaks about 4 endpoints, which I expect to be on
> interface 0 as they also have listed endpoint number 0 - they don't
> tell in the document.
> What I currently don't know is why there are 2 interfaces.
> The document also mentions some homenet capabilities on RJ11 - whatever
> it means.
> Maybe it's an hardware optional interface, which is disabled in this
> special device.

in Bluetooth case they decided to put isoc. endpoints on the another
interface so you can scale isoc. bandwidth (via max. packet size)
without affecting the other transfers.

thanks,
max



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E84ABB9.4090708>