From: Todd Inglett <tinglett@vnet.ibm.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Yet another RS6k whipped!
Date: Thu, 02 Nov 2000 09:57:04 -0600 [thread overview]
Message-ID: <3A018ED0.AEAA1B40@vnet.ibm.com> (raw)
In-Reply-To: Pine.HPX.4.10.10011021136540.15431-100000@gra-ux1.iram.es
Gabriel Paubert wrote:
> Ok, there were a few bugs with Openpic on PreP: some functions were marked
> __chrp while openpic support is a completely orthogonal issue. Yours seems
> to work, however, which source tree are you using ? (I'm still basing
> everything on kernel.org).
I may still have trouble here. My code was based on a test8 kernel that
Tom snagged. I hope I can reproduce it in test10 :).
> Besides this, it's fairly close to what I do on my MVME boxes: the
> firmware puts them in PreP mode and I reorganize them as CHRP. This forces
> me to reorganize all the PCI space (but the code has not been with bridges
> and will probably fail). You have open firmware, which is hopefully more
> flexible than PPCBUG which I have to use.
This is exactly what I want to do. Any big pitfalls you can recall?
Guess I need to have a look at your patch. I'm assuming you have a
Grackle.
--
-todd
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-02 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 18:36 Yet another RS6k whipped! Todd Inglett
2000-11-02 9:01 ` Michael Schmitz
2000-11-02 10:46 ` Gabriel Paubert
2000-11-02 15:57 ` Todd Inglett [this message]
2000-11-02 16:16 ` Gabriel Paubert
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=3A018ED0.AEAA1B40@vnet.ibm.com \
--to=tinglett@vnet.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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).