Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@pacbell.net>
To: Kunihiko IMAI <kimai@laser5.co.jp>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: Re: usb-problems with Au1000
Date: 17 Jan 2002 11:02:03 -0800	[thread overview]
Message-ID: <1011294123.4550.58.camel@zeus> (raw)
In-Reply-To: <m3bsft6z87.wl@l5ac152.l5.laser5.co.jp>

On Thu, 2002-01-17 at 02:36, Kunihiko IMAI wrote:
> Hi,
> 
> I'm trying SGI version of kernel-2.2.17.
> And I get same message,
> 
> At Thu, 10 Jan 2002 18:40:24 +0100,
> Wolfgang Heidrich wrote:
> 
> > hub.c: USB new device connect on bus1/1, assigned device number 3
> > usb.c: USB device not accepting new address=3 (error=-145)

I'm surprised the sgi kernel works with usb at all.  We did a patch for
non-pci usb devices which was not accepted by the usb project at that
time because they were working on a different solution.
 
> when connect some device.
> 
> 
> I checked in some cases:
> 
> - Some devices are recognized, some are not.
> 	A joystick device (sanwa supply) works fine.
> 	A mouse device (century corp.) works too.
> 	But another mouse (Logitech Mini Wheel Mouse) doesn't work and
> 		I got message like above.
> 
> - When connected via USB hub device, Logitech mouse works fine.
> 
> I think USB root HUB doesn't work properly. 
 
> By the way:
> 
> today, I got a errata document from the chip dealer.  This document
> reports some USB errata.
> I read the report and source code, then  I found a bug in
> arch/mips/au1000/pb1000/setup.c.
> 
> 
> The errata report says workaround method:
> - set the CPU clock is 384MHz
> - set the source of USB host controller is CPU clcck.
> 
> And the code:
> 
>         /*
>          * Setup 48MHz FREQ2 from CPUPLL for USB Host
>          */
>         /* FRDIV2=3 -> div by 8 of 384MHz -> 48MHz */
>         sys_freqctrl |= ((3<<22) | (1<<21) | (0<<20));
>         outl(sys_freqctrl, FQ_CNTRL_1);
> 
> Comment says "Setup FREQ2" but the code set FREQ5.

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).

I do have a better USB workaround which checks the CPU silicon rev, but
I haven't had time to send Ralf an updated patch. The current setup.c
should work though.  Get the latest LSP from Alchemy, check the S4
jumpers (1-4 off, 5-6 on, 7-8 off), and let me know if it still doesn't
work for you.

Pete

  reply	other threads:[~2002-01-17 20:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 23:07 latest au1000 updates Pete Popov
2002-01-10 17:40 ` usb-problems with Au1000 Wolfgang Heidrich
2002-01-10 17:49   ` Pete Popov
2002-01-10 18:48     ` Wolfgang Heidrich
2002-01-10 19:00       ` Pete Popov
2002-01-17 10:36   ` Kunihiko IMAI
2002-01-17 19:02     ` Pete Popov [this message]
2002-01-18  5:26       ` Kunihiko IMAI
2002-01-18 17:59         ` Pete Popov
2002-01-18 19:49         ` Pete Popov
2002-01-22  9:56           ` Kunihiko IMAI
2002-01-22 10:51             ` Wolfgang Heidrich
2002-01-22 17:33             ` Pete Popov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1011294123.4550.58.camel@zeus \
    --to=ppopov@pacbell.net \
    --cc=kimai@laser5.co.jp \
    --cc=linux-mips@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox