Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ulf Carlsson <ulfc@bun.falkenberg.se>
To: Alistair Lambie <alambie@rock.csd.sgi.com>
Cc: Linux SGI <linux@cthulhu.engr.sgi.com>
Subject: Re: weird HAL2
Date: Tue, 2 Feb 1999 20:53:28 +0100	[thread overview]
Message-ID: <19990202205328.A1996@bun.falkenberg.se> (raw)
In-Reply-To: <36B753D6.641616A4@csd.sgi.com>; from Alistair Lambie on Wed, Feb 03, 1999 at 08:36:54AM +1300

> I don't know anything about the HAL2, but looking in hal2.h it says
> 0=reset, so from what I can see you write 0x0018 to it and then it
> should read 0x0000 when it is reset.

The spec says:

Bit 3, Global reset R/W:
Assertion of hardware reset i.e. RESET_N, set this to zero. Software brings the
HAL2 out of reset by setting this bit and may reset the HAL2 by clearing it.
Please note: this bit must be set before any other internal register access
occurs.
RESET = 0;
ACTIVE = 1;

Bit 4, Codec reset R/W:
Value reflected to CODEC_RESET_N pin. To reset external codecs and other
external devices.
RESET = 0; ACTIVE = 1;

This is exactly what I'm trying to do by first writing 0x0000 to isr, waiting
some us, and then writing 0x0018. Then the card should be active and isr should
IMHO contain 0x0018.

> Maybe this part is working ok for you and the problem is further along?

Nope.

- Ulf

  reply	other threads:[~1999-02-02 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-02 16:17 weird HAL2 Ulf Carlsson
1999-02-02 19:36 ` Alistair Lambie
1999-02-02 19:53   ` Ulf Carlsson [this message]
1999-02-02 20:25     ` Alistair Lambie
1999-02-02 21:11     ` Alan Cox
1999-02-02 21:11       ` Alan Cox
1999-02-02 21:26       ` Thomas Bogendoerfer
  -- strict thread matches above, loose matches on Subject: below --
1999-02-01 22:10 Thomas Bogendoerfer
1999-02-01 23:09 ` Ulf Carlsson

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=19990202205328.A1996@bun.falkenberg.se \
    --to=ulfc@bun.falkenberg.se \
    --cc=alambie@rock.csd.sgi.com \
    --cc=linux@cthulhu.engr.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