All of lore.kernel.org
 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: 22 Jan 2002 09:33:29 -0800	[thread overview]
Message-ID: <1011720809.28944.149.camel@zeus> (raw)
In-Reply-To: <m37kqa7lpq.wl@l5ac152.l5.laser5.co.jp>

On Tue, 2002-01-22 at 01:56, Kunihiko IMAI wrote:
> Hi,
> 
> At 18 Jan 2002 11:49:09 -0800,
> Pete Popov wrote:
> > 
> > 
> > > > 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.
> 
> Oh, I see.  I'm sorry for my misunderstanding.

It's OK, one of these days I'll have time to rename all the registers to
match the last data book.

Pete
 
> Now the relations are like this:
> 
> Au1000 manual	Linux Header
> -----------------------------------
> sys_freqctl0	FQ_CNTRL_1
> sys_freqctl1	FQ_CNTRL_2
> -----------------------------------

      parent reply	other threads:[~2002-01-22 18:32 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
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 [this message]

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=1011720809.28944.149.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.