From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev Development <linuxppc-dev@ozlabs.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: 82xx CPU features
Date: Wed, 31 Jan 2007 07:55:13 +0300 [thread overview]
Message-ID: <20070131075513.55302696@localhost.localdomain> (raw)
In-Reply-To: <8E9D9D0A-80B5-4861-8612-7ABAF4815C4D@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Tue, 30 Jan 2007 16:35:03 -0600
Kumar Gala wrote:
>
> On Jan 30, 2007, at 4:31 PM, Guennadi Liakhovetski wrote:
>
> > On Fri, 26 Jan 2007, Kumar Gala wrote:
> >
> >> For _CAN_NAP, I'm guessing its historic, maybe Dan knows why it
> >> wasn't set.
> >> What happens if you try to set it? Are there implications at the
> >> system level
> >> with regards to _CAN_NAP?
> >
> > Just tested: set CPU_FTR_MAYBE_CAN_DOZE for 82xx,
> > CONFIG_BDI_SWITCH is not
> > defined, echoed 1 to /proc/sys/kernel/powersave-nap - and a 8241
> > still runs... I'll try to measure if there's any difference in power
> > consumption:-))
> >
> >> I'm looking at the CPU_FTR_PPC_LE it varies if we should use
> >> _PPC_LE vs
> >> _TRUE_LE (or whatever the other one is called).
>
> It would be good for someone to test an 8260 class (826x, 8272,
> etc..) to see if they have any issues.
I can see with 8272 if that makes any difference.
--
Thanks, Vitaly
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-01-31 4:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 22:39 82xx CPU features Guennadi Liakhovetski
2007-01-26 7:24 ` Kumar Gala
2007-01-30 22:31 ` Guennadi Liakhovetski
2007-01-30 22:35 ` Kumar Gala
2007-01-31 4:55 ` Vitaly Bordug [this message]
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=20070131075513.55302696@localhost.localdomain \
--to=vbordug@ru.mvista.com \
--cc=g.liakhovetski@gmx.de \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).