From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: confused about HID1 bits and G5
Date: Thu, 29 Apr 2004 08:29:31 +1000 [thread overview]
Message-ID: <1083191370.21436.81.camel@gaston> (raw)
In-Reply-To: <408FEBB6.105@nortelnetworks.com>
> It appears that we're relying on the firmware to set up a lot of the bits in this register--is there
> any reason we aren't forcing particular values?
Forcing values in HIDs is BAD. The firmware may set/clear bits to work
around specific CPU or north bridge bugs for example. That's why I need
to change the code that force-clear HID4/5 one of these days too and
instead just clear the bits I want to be cleared.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-28 22:29 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 [this message]
2004-04-29 13:54 ` Chris Friesen
2004-04-29 15:05 ` Greg Watson
2004-04-29 21:49 ` Benjamin Herrenschmidt
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=1083191370.21436.81.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cfriesen@nortelnetworks.com \
--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 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.