From: benh@kernel.crashing.org
To: Michael Zucca <mzucca@ne.mediaone.net>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4.18 and dmasound and rebooting
Date: Mon, 4 Mar 2002 00:34:13 +0100 [thread overview]
Message-ID: <20020303233413.32449@mailhost.mipsys.com> (raw)
In-Reply-To: <3C827800.67CC4435@ne.mediaone.net>
>
>Ok, I tried 2.4.18 from kernel.org on my PowerCenter 132 and the DMA
>dead patch works. However, as a side note, it only seems to work if the
>sound code is compiled into the kernel. The same code in a module does
>not work and still causes the sound hang. As I recall, the way the
>emergency buffer was allocated was critical to it functioning properly.
>I usually compile in the sound driver so it's not a big deal for me but
>it might be for other folks.
Well, I see no problem with the way the buffer is allocated. However,
the emergency buffer code looks wrong: It should really contain a
branch command to branch back the DBDMA controller to the normal buffer.
>On another note, I've noticed that if I reboot my machine using shutdown
>-r the machine will reboot to a gray screen and then just hang there. It
>won't boot into MacOS. I've noticed that on 68k Macs, it is important to
>map the ROMs back into memory before rebooting or the machine just hangs
>around forever. Is it possible that we're not remapping stuff back to
>its usual place before rebooting on OldWorld machines? This has been a
>persistant problem for a long time on 2.4.
That is weird, I don't think we have to take care of any sort of MMU
mapping, looks more like some driver would need to be restored in some
"pristine" state (sound ?)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-03 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 18:07 2.4.17 and dmasound Michael Zucca
2002-02-22 18:31 ` benh
2002-03-03 19:22 ` 2.4.18 and dmasound and rebooting Michael Zucca
2002-03-03 23:34 ` benh [this message]
2002-03-04 0:03 ` benh
-- strict thread matches above, loose matches on Subject: below --
2002-03-18 14:15 Michael R. Zucca
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=20020303233413.32449@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mzucca@ne.mediaone.net \
/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.