From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: ulfc@bun.falkenberg.se (Ulf Carlsson)
Cc: alambie@rock.csd.sgi.com, linux@cthulhu.engr.sgi.com
Subject: Re: weird HAL2
Date: Tue, 2 Feb 1999 21:11:04 +0000 (GMT) [thread overview]
Message-ID: <m107n69-0007U1C@the-village.bc.nu> (raw)
In-Reply-To: <19990202205328.A1996@bun.falkenberg.se> from "Ulf Carlsson" at Feb 2, 99 08:53:28 pm
> 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.
Stupid question but does
write 0x0010
wait 10uS
write 0x0018
work ?
(ie do you have to bring them out of reset card, then codec ?
WARNING: multiple messages have this Message-ID (diff)
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: Ulf Carlsson <ulfc@bun.falkenberg.se>
Cc: alambie@rock.csd.sgi.com, linux@cthulhu.engr.sgi.com
Subject: Re: weird HAL2
Date: Tue, 2 Feb 1999 21:11:04 +0000 (GMT) [thread overview]
Message-ID: <m107n69-0007U1C@the-village.bc.nu> (raw)
Message-ID: <19990202211104.RaQPfzDlBhQYH4gesvv_k-GL_9gargGAXiwx2DeKjsM@z> (raw)
In-Reply-To: <19990202205328.A1996@bun.falkenberg.se> from "Ulf Carlsson" at Feb 2, 99 08:53:28 pm
> 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.
Stupid question but does
write 0x0010
wait 10uS
write 0x0018
work ?
(ie do you have to bring them out of reset card, then codec ?
next prev parent reply other threads:[~1999-02-02 20:16 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
1999-02-02 20:25 ` Alistair Lambie
1999-02-02 21:11 ` Alan Cox [this message]
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=m107n69-0007U1C@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alambie@rock.csd.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ulfc@bun.falkenberg.se \
/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.