From: Corey Minyard <minyard@acm.org>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: Gabriel Paubert <paubert@iram.es>,
Matt Porter <mmporter@home.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: arch/ppc/kernel restructure + MVME/MTX OpenPIC support
Date: 11 Jan 1999 13:01:49 -0600 [thread overview]
Message-ID: <m267advdk2.fsf@wf-rch.cirr.com> (raw)
In-Reply-To: Troy Benjegerdes's message of Sun, 10 Jan 1999 16:24:13 -0600 (CST)
Troy Benjegerdes <hozer@drgw.net> writes:
> I have just finished some early testing of this.
>
> The patch is available on
> ftp://ftp.microux.com/pub/linux/linuxppc-rework-troy.patch.gz
>
> Here's what I put in the REAME:
>
> This is my set of integrated patches to the Linux kernel, which are based on
> Corey Minyard's linuxppc-rework3.diff patches, along with Gabriel Paubert's
> Preploader (which I have integrated into arch/ppc/preploader) and Raven MPIC
> support for Motorola MTX/MVME boards.
>
> This works on my MTX board, but only with CONFIG_PREPLOADER (the preploader
> has a config option ;) ) because the raven needs to have it's PCI memory
> space remapped or it isn't accessible.
>
> Pmac should work, along with APUS. I think I may have broken MBX support..
> Can someone check this out and fix this?
>
> These patches were made from my local CVS archive agains 2.2.0-pre6.
> Please let me know if you have any additions, etc.
>
Is there anybody that could do the MBX work and test things out? That
is the biggest hole missing. I'd like to see all the 8xx and MBX stuff
be put into the new framework, but I don't have the experience to do
it. I'm also a little short of time right now since I'm remodelling
my house.
Also, a couple of small things that probably need to be fixed:
* The __initfunc() needs to be removed from all the xxx_setup_residual
function calls, since that is called all the time.
* The patch to idle.c needs to look something like:
--- linux-2.2p4.orig/arch/ppc/kernel/idle.c Mon Jan 4 16:59:13 1999
+++ linux-2.2p4/arch/ppc/kernel/idle.c Mon Jan 4 16:49:13 1999
@@ -301,7 +301,14 @@
hid0 &= ~(HID0_NAP | HID0_SLEEP | HID0_DOZE);
hid0 |= (powersave_nap? HID0_NAP: HID0_DOZE) | HID0_DPM;
asm("mtspr 1008,%0" : : "r" (hid0));
- msr |= MSR_POW;
+
+ /* set the POW bit in the MSR, and enable interrupts
+ so we'll wake up sometime! */
+ _nmask_and_or_msr(0, MSR_POW | MSR_EE);
+
+ /* Disable interrupts again so restore_flags will
+ work. */
+ _nmask_and_or_msr(MSR_EE, 0);
}
restore_flags(msr);
default:
--
Corey Minyard Internet: minyard@acm.org
Work: minyard@nortel.ca UUCP: minyard@wf-rch.cirr.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-11 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-10 22:24 arch/ppc/kernel restructure + MVME/MTX OpenPIC support Troy Benjegerdes
1999-01-11 19:01 ` Corey Minyard [this message]
1999-01-12 5:44 ` Troy Benjegerdes
1999-01-12 7:42 ` Dan Malek
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=m267advdk2.fsf@wf-rch.cirr.com \
--to=minyard@acm.org \
--cc=hozer@drgw.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mmporter@home.com \
--cc=paubert@iram.es \
/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).