From: Pantelis Antoniou <panto@intracom•gr>
To: Tom Rini <trini@kernel•crashing.org>,
linux-ppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: The case of the disappearing CPU_FTR_xxx
Date: Tue, 09 Nov 2004 10:47:09 +0200 [thread overview]
Message-ID: <4190840D.6000403@intracom.gr> (raw)
Hi all
I'm currently trying to implement proper idling for 8xx in 2.4 (please
don't bitch yet
since things are pretty similar for 2.6 too).
It appears that the flags set in cputable.c, i.e. CPU_FTR_NAP get cleared
at some point in the init sequence.
Looking at the 6xx idle code, there is some extra handling for that case but
I'm unable to locate what is going on.
Can anyone shed some light on the issue?
Regards
Pantelis
reply other threads:[~2004-11-09 8:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4190840D.6000403@intracom.gr \
--to=panto@intracom$(echo .)gr \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=trini@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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