From: benh@kernel.crashing.org
To: Paul White <pwhite@bivio.net>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: MPC7455
Date: Wed, 6 Mar 2002 22:48:49 +0100 [thread overview]
Message-ID: <20020306214849.11643@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0203062152510.30207-100000@stimpy.networkrobots.com>
>Great! It sounds like the firmware is doing everyhting. It might be
>nice to add an option to have linux configure the CPU registers or not,
>as for us embedded guys thats easier than implimenting it all in the
>firmware. We can do it either way now that we know what the registers
>should be, though.
Well, then the correct place for the patch is probably in the wrapper
or in a CONFIG_xxx option for your embedded box. At least for PReP/CHRP/Pmac,
I want to rely on the firmware for various reasons (one beeing that Apple's
firmware sets some bits in specific ways to avoid/workaround chip errata).
>I'll have a cleaned up patch file by tomorrow evening. What tree
>would you prefer the patch be against?
Whatever, I'll probably edit it anyway.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-06 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 7:02 MPC7455 Paul White
2002-03-06 19:46 ` MPC7455 Benjamin Herrenschmidt
2002-03-07 5:59 ` MPC7455 Paul White
2002-03-06 21:48 ` benh [this message]
2002-03-07 15:30 ` MPC7455 Tom Rini
2002-03-07 16:45 ` MPC7455 Dan Malek
2002-03-07 9:24 ` MPC7455 Gabriel Paubert
2002-03-06 22:18 ` MPC7455 Kevin B. Hendricks
2002-03-07 6:01 ` MPC7455 Paul White
2002-03-07 8:41 ` MPC7455 Giuliano Pochini
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=20020306214849.11643@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pwhite@bivio.net \
/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).