From: cort@fsmlabs.com
To: akuster <akuster@dslextreme.com>
Cc: Matthew Locke <mlocke@mvista.com>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC/Patch] 4xx idle loop
Date: Thu, 25 Jul 2002 00:54:26 -0600 [thread overview]
Message-ID: <20020725005426.H5740@cort.fsmlabs.com> (raw)
In-Reply-To: <20020724233921.G5740@cort.fsmlabs.com>; from cort@fsmlabs.com on Wed, Jul 24, 2002 at 11:39:21PM -0600
That should read "there's no need for the indirection..."
} There's need for the indirection for this sort of thing. The only reason
} I created ppc_md was to allow for different machines to run off a single
} binary but not different chip families.
}
} A big #ifdef for the chip-type would work fine since the chip family is
} known at compile time. The machine type isn't always know which is the
} reason for ppc_md.
}
} } This sounds like a good idea if we could use
} } if( ppc_md.powersave != NULL)
} } ppc_md.powersave();
} }
} } If it is determined that calling power_save() which is resides in an
} } arch/processor specific file then we are talking about many files being
} } hit. and the current power_save seems to common for many other ppc
} } platforms other than 4xx & 8xx
}
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-25 6:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 5:55 [RFC/Patch] 4xx idle loop akuster
2002-07-24 19:50 ` Matthew Locke
2002-07-25 5:38 ` akuster
2002-07-25 5:39 ` cort
2002-07-25 6:54 ` cort [this message]
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=20020725005426.H5740@cort.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=akuster@dslextreme.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlocke@mvista.com \
/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).