From: akuster <akuster@dslextreme.com>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: [RFC/Patch] 4xx idle loop
Date: Tue, 23 Jul 2002 22:55:17 -0700 [thread overview]
Message-ID: <3D3E4145.8030500@dslextreme.com> (raw)
I was going though some old 4xx kernels I have and found an
implimentation of idle.c that had support for 4xx. I believe the reason
it never made is out was the hacking we did to make it work. So I
propose that we modify the kernel/Makefile to use ppc4xx_idel.o instead
of idle.o when 4xx is configured. That way we have a clean
implimentation for 4xx idle functions and not touch the generic ppc idle
file. The function names would not change.
Armin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-07-24 5:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 5:55 akuster [this message]
2002-07-24 19:50 ` [RFC/Patch] 4xx idle loop Matthew Locke
2002-07-25 5:38 ` akuster
2002-07-25 5:39 ` cort
2002-07-25 6:54 ` cort
2002-07-25 16:51 ` Matthew Locke
2002-07-25 16:53 ` Cort Dougan
2002-07-25 16:20 ` Benjamin Herrenschmidt
2002-07-25 17:55 ` Cort Dougan
2002-07-25 18:04 ` Todd Poynor
2002-07-25 19:20 ` Dan Malek
2002-07-27 16:30 ` akuster
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=3D3E4145.8030500@dslextreme.com \
--to=akuster@dslextreme.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).