From: Sylvain Munaut <tnt@246tNt•com>
To: roger blofeld <blofeldus@yahoo•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: MPC5200 Cache coherency with BestComm issue
Date: Mon, 29 Nov 2004 19:29:22 +0100 [thread overview]
Message-ID: <41AB6A82.8070201@246tNt.com> (raw)
In-Reply-To: <20041129174842.14784.qmail@web53506.mail.yahoo.com>
Hi Roger
>
>Sylvain,
> You are correct. The CPU_FTR_NEED_COHERENT is not required. Perhaps
>the solution is to only turn on powersave_nap if CONFIG_PPC_BESTCOMM is
>not selected.
>
>
Pull the latest tree. I've just commented it out with a note.
I didn't rip it off so that people copying lite5200.c for their own
board know how to activate
it if they need to ...
It can also be controlled from userspace /proc/sys/kernel/powersave-nap
You just need to be aware of the consequences ( like USB not working
either ! ) if you want
to save power.
Sylvain
next prev parent reply other threads:[~2004-11-29 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 17:48 MPC5200 Cache coherency with BestComm issue roger blofeld
2004-11-29 18:29 ` Sylvain Munaut [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 20:16 Lite5200 FEC Driver on linux 2.6 broken? (again) Dale Farnsworth
2004-11-27 21:39 ` MPC5200 Cache coherency with BestComm issue roger blofeld
2004-11-28 23:22 ` Sylvain Munaut
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=41AB6A82.8070201@246tNt.com \
--to=tnt@246tnt$(echo .)com \
--cc=blofeldus@yahoo$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)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