From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>,
Takashi Oe <toe@unlserve.unl.edu>,
Kostas Gewrgiou <gewrgiou@imbc.gr>
Subject: Re: Sound stoppage
Date: Wed, 28 Mar 2001 15:17:34 +0200 [thread overview]
Message-ID: <20010328131734.25918@mailhost.mipsys.com> (raw)
In-Reply-To: <20010328091553.4B07DDB9FC@atlas.valhalla.net>
>
>The MacOS extension patch fixes a "PCI timing problem" - specifically
>claimed to stop PCI-based-IDE/Sound interaction (which is what we are
>seeing).
I quickly disassembled the extension, what it does is to write
0x00000858 (swapped) -> 0xf2800000
0x12 (byte) -> 0xf2c00000
Which is basically writing 0x12 to byte at address 0x58 of Bandit
PCI bridge config space.
Now we need to figure out how to identify this machine/bandit model to
make sure we don't scew up bandit on another box.
Can someone try to figure out in the device-tree if there's anything like
a machine ID ? (the "old" mac-os like box ID is 0x66 I think, but I don't
know if it can be found in the device tree. It may be available via mother
board straps around 0xf3000000 however).
I'd also like to know the bandit deviceID & revisionID in it's PCI config
space.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-28 13:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-28 9:15 Sound stoppage Iain Sandoe
2001-03-28 13:17 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 11:02 Iain Sandoe
2001-03-29 10:05 Iain Sandoe
2001-03-29 10:25 ` Takashi Oe
2001-03-29 13:47 ` Michael R. Zucca
2001-03-28 14:28 Iain Sandoe
2001-03-28 22:04 ` Takashi Oe
2001-03-28 9:23 Iain Sandoe
2001-03-28 7:06 Iain Sandoe
2001-03-28 9:09 ` Kostas Gewrgiou
2001-03-28 21:31 ` Takashi Oe
2001-04-01 4:01 ` Michael R. Zucca
2001-03-27 21:31 Iain Sandoe
2001-03-27 23:35 ` Takashi Oe
2001-03-27 17:54 Iain Sandoe
2001-03-27 20:41 ` Takashi Oe
2001-03-27 15:14 Iain Sandoe
2001-03-27 16:32 ` Takashi Oe
2001-03-26 4:26 Iain Sandoe
2001-03-26 3:09 Michael R. Zucca
2001-03-26 3:22 ` Hollis R Blanchard
2001-03-27 9:58 ` phandel
2001-03-27 13:20 ` Michael R. Zucca
2001-03-27 14:30 ` Takashi Oe
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=20010328131734.25918@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=gewrgiou@imbc.gr \
--cc=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toe@unlserve.unl.edu \
/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;
as well as URLs for NNTP newsgroup(s).