From: benh@kernel.crashing.org
To: <hobold@Informatik.Uni-Bremen.DE>,
Edward Swarthout <Ed.Swarthout@Motorola.com>
Cc: <christopher.murtagh@mcgill.ca>,
<linuxppc-dev@lists.linuxppc.org>,
<yellowdog-devel@lists.yellowdoglinux.com>
Subject: Re: Support for new Dual G4 1 Gig machines?
Date: Tue, 29 Jan 2002 20:09:40 +0100 [thread overview]
Message-ID: <20020129190941.5062@mailhost.mipsys.com> (raw)
In-Reply-To: <200201291701.g0TH1a318829@pacific.somerset.sps.mot.com>
>The 7455 uses bit 8 for HIGH_BAT_EN. On the 7400/7410, bit 8 is DOZE
>Enable and on the 7450 it is ignored. So, code ported from the 7400
>which happens to set bit 8 will work fine on the 7450 but cause great
>grief on the 7455. Random translations whose side effects don't get
>detected until much later tend to make system debug difficult...
If I didn't fuck it up too much, the latest kernels will not set
the DOZE bit on those CPUs if they have a proper cputable entry
(basically copy the 7450 one).
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-29 19:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C55A9A8.9B3EB57E@wvi.com>
2002-01-28 20:34 ` Support for new Dual G4 1 Gig machines? Christopher Murtagh
2002-01-29 12:39 ` benh
2002-01-29 14:52 ` Christopher Murtagh
2002-01-29 15:01 ` Holger Bettag
2002-01-29 17:01 ` Edward Swarthout
2002-01-29 19:09 ` benh [this message]
2002-01-29 19:08 ` benh
2002-01-30 9:44 ` Alain RICHARD
2002-01-30 14:55 ` benh
2002-01-29 17:25 ` Derrik Pates
2002-01-29 22:06 ` Tom Rini
2002-01-30 7:00 ` Eric Leblond
2002-01-28 19:40 Kevin B. Hendricks
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=20020129190941.5062@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=Ed.Swarthout@Motorola.com \
--cc=christopher.murtagh@mcgill.ca \
--cc=hobold@Informatik.Uni-Bremen.DE \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=yellowdog-devel@lists.yellowdoglinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.