From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g0IKmpa08801 for linux-mips-outgoing; Fri, 18 Jan 2002 12:48:51 -0800 Received: from hermes.mvista.com ([12.44.186.158]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g0IKmkP08797 for ; Fri, 18 Jan 2002 12:48:47 -0800 Received: from zeus.mvista.com (zeus.mvista.com [10.0.0.112]) by hermes.mvista.com (8.11.0/8.11.0) with ESMTP id g0IJklB14075; Fri, 18 Jan 2002 11:46:47 -0800 Subject: Re: usb-problems with Au1000 From: Pete Popov To: Kunihiko IMAI Cc: linux-mips In-Reply-To: References: <3B7DA3A3.8010000@pacbell.net> <3C3DD208.45B5BC29@esk.fhg.de> <1011294123.4550.58.camel@zeus> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0 (Preview Release) Date: 18 Jan 2002 11:49:09 -0800 Message-Id: <1011383349.18177.6.camel@zeus> Mime-Version: 1.0 Sender: owner-linux-mips@oss.sgi.com Precedence: bulk > > It's the comment that's wrong, not the code. The code works and has been > > tested. Alchemy makes available the Linux Support Package (LSP) which > > we did. That kernel has been tested with all peripherals so I would > > recommend that you get that from them. Also,make sure your jumpers are > > setup correctly (S4). > > In the source code: > > sys_clksrc |= ((4<<12) | (0<<11) | (0<<10)); > > (snip...) > > outl(sys_clksrc, CLOCK_SOURCE_CNTRL); > > This code sets the clock source of USB host controller is FREQ2. So > FREQ5 clock source doesn't affect to USB host controller. After looking into it, both the comment and code are correct. From include/asm-mips/au1000.h: #define FQ_CNTRL_1 0xB1900020 #define FQ_CNTRL_2 0xB1900024 So FQ_CNTRL_1 corresponds to what is now sys_freqctrl0. In other words, the update to the databook has not been incorporated into the Au1000 files. The names of the registers were updated after I had done all the core work. I need to update the code so the names of the registers correspond to the latest Au1000 manual. Since the boards we have do work with USB and there were some usb hardware glitches, please check with Alchemy on what the problem might be with your board. Pete