From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg Watson <gwatson@lanl.gov>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: confused about HID1 bits and G5
Date: Fri, 30 Apr 2004 07:49:48 +1000 [thread overview]
Message-ID: <1083275387.29594.146.camel@gaston> (raw)
In-Reply-To: <B77CD81E-99EE-11D8-B5B8-000393A47A5C@lanl.gov>
On Fri, 2004-04-30 at 01:05, Greg Watson wrote:
> As a firmware designed (LinuxBIOS), I would support this. Obviously
> there are some things that the firmware has to do, like enable memory,
> but the less reliance the o/s has on magic behavior the better. It
> makes firmware design simpler and more reliable.
There is nothing like "magic behaviour" here. There is a set of
features that should normally be enabled on the CPU, this set is
clearly defined in the spec, the firmware should enabled them.
As I wrote, I prefer not touching most of this from the kernel since
some specific CPU rev. errata may involve disabling some of those,
and that is typically done by the firmware, at least on pmacs. Now,
it's possible that I decide to force more of these bits myself based
on experience with broken firmwares, but so far, this has not been
necessary :)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-29 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 17:36 confused about HID1 bits and G5 Chris Friesen
2004-04-28 22:29 ` Benjamin Herrenschmidt
2004-04-29 13:54 ` Chris Friesen
2004-04-29 15:05 ` Greg Watson
2004-04-29 21:49 ` Benjamin Herrenschmidt [this message]
2004-04-29 23:16 ` Greg Watson
2004-04-29 21:46 ` Benjamin Herrenschmidt
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=1083275387.29594.146.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cfriesen@nortelnetworks.com \
--cc=gwatson@lanl.gov \
--cc=linuxppc-dev@lists.linuxppc.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).