From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 28 12:12:01 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0757537B401; Fri, 28 Mar 2003 12:12:01 -0800 (PST) Received: from scl8owa02.int.exodus.net (scl8out02.exodus.net [66.35.230.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A59343F85; Fri, 28 Mar 2003 12:11:56 -0800 (PST) (envelope-from Maksim.Yevmenkin@cw.com) Received: from scl8owa01.int.exodus.net ([66.35.230.241]) by scl8owa02.int.exodus.net with Microsoft SMTPSVC(5.0.2195.5329); Fri, 28 Mar 2003 12:11:56 -0800 Received: from exodus.net ([165.193.27.35]) by scl8owa01.int.exodus.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.5329); Fri, 28 Mar 2003 12:11:55 -0800 Message-ID: <3E84ABB9.4090708@exodus.net> Date: Fri, 28 Mar 2003 12:08:25 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021126 X-Accept-Language: en-us, ru, en MIME-Version: 1.0 To: ticso@cicely.de References: <20030328183858.7B2DB37B401@hub.freebsd.org> <20030328185650.GK23168@cicely9.cicely.de> <3E849FA7.1000400@exodus.net> <20030328193719.GN23168@cicely9.cicely.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Mar 2003 20:11:55.0898 (UTC) FILETIME=[47BF3DA0:01C2F566] X-Spam-Status: No, hits=-16.9 required=5.0 tests=AWL,QUOTED_EMAIL_TEXT,REFERENCES,USER_AGENT_MOZILLA_UA autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: Bill Paul cc: hackers@freebsd.org cc: ticso@cicely9.cicely.de Subject: Re: Ax88172 vs FreeBSD USB stack X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2003 20:12:02 -0000 >>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