From owner-freebsd-mips@FreeBSD.ORG Sat Apr 2 00:20:45 2011 Return-Path: Delivered-To: mips@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7004106566B; Sat, 2 Apr 2011 00:20:44 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by mx1.freebsd.org (Postfix) with ESMTP id DAB208FC12; Sat, 2 Apr 2011 00:20:43 +0000 (UTC) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTZZr26XQNdO+8cfka9ykfkgU/yPoWzhj@postini.com; Fri, 01 Apr 2011 17:20:44 PDT Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 1 Apr 2011 17:16:34 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 1 Apr 2011 20:18:08 -0400 From: Andrew Duane To: Juli Mallett , bhanuprakash bodireddy Date: Fri, 1 Apr 2011 20:15:12 -0400 Thread-Topic: Blatant simple bug in Cavium SDK USB code? Thread-Index: AcvwutEqVYVCtpK8Q9C0opKHDjU+IAAEDdp/ Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "mips@freebsd.org" Subject: RE: Blatant simple bug in Cavium SDK USB code? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2011 00:20:45 -0000 I have USB hardware, and some familiarity with at least the bottom half of = the code. I know nothing of the scheduling, perdiodic stuff, the USB protoc= ol itself. But I can probably look at the hardware and driver aspects of it= . My hardware is very simple, a direct connect between the 5650 and a sing= le USB plug on the chassis. There's a similar platform I have someone else = working on that has a 4-port hub too, to look at "some day". We got a driver from a 3rd party company called Synopsis I think, I doubt t= here's any way we can use it, but I should be able to get the bottom half g= oing to at least recognize a stick. -- Andrew Duane Juniper Networks 978-589-0551 10 Technology Park Dr aduane@juniper.net Westford, MA 01886-3418 ________________________________________ From: juli@clockworksquid.com [juli@clockworksquid.com] On Behalf Of Juli M= allett [jmallett@FreeBSD.org] Sent: Friday, April 01, 2011 6:18 PM To: bhanuprakash bodireddy Cc: Andrew Duane; mips@freebsd.org Subject: Re: Blatant simple bug in Cavium SDK USB code? Following up to Andrew, On Fri, Apr 1, 2011 at 14:23, bhanuprakash bodireddy wrote: > On Fri, Apr 1, 2011 at 1:03 PM, Andrew Duane wrote: >> >> This isn't even close to the only problem I'm having. I don't make it ou= t >> of cvmx_usb_initialize at all. One of two things happens: > > We are yet to add the USB support to mainline. I have sent USB support > patches to Juli and she had reviewed them earlier. > But some of the routines are yet to be rewritten(due to other issues) and > hence the support is still missing. The outstanding patches are for Octeon 2 only, so if you're using CN5XXX you'll have to wait for someone to fix up the SDK-based USB driver. HPS did a great job on it initially, even working without hardware, and we managed to get it mostly working, but there were/are remaining issues that somebody with interest, time and hardware will need to solve. My USB need has disappeared and I've been short on time, so it hasn't been a priority for me. (I can't speak to CN3XXX as I don't have any usable CN3XXX hardware presently and it doesn't seem worth investing as much effort in.) Oleksandr has Octeon hardware with USB, and there's a system with USB in the Netperf cluster (although obviously that isn't really convenient for USB testing, but can be used for basic controller work) and Alexander Kabaev has expressed an interest in USB in the past. There's a D-Link Ukraine developer who has done some work with the DWC_OTG driver from Linux for Octeon and some other boards with similar hardware. Adrian Chadd should be getting Octeon hardware in the near future, including USB. So there's enough people with the right skills and hardware out there, it's just a matter of someone having enough time and interest to work on it. Juli.