From: Tom Rini <trini@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Big powermac update
Date: Mon, 26 Jan 2004 08:29:22 -0700 [thread overview]
Message-ID: <20040126152921.GF15271@stop.crashing.org> (raw)
In-Reply-To: <1075075758.848.34.camel@gaston>
On Mon, Jan 26, 2004 at 11:09:18AM +1100, Benjamin Herrenschmidt wrote:
> On Mon, 2004-01-26 at 05:55, Tom Rini wrote:
> > On Sat, Jan 24, 2004 at 11:58:33AM +1100, Benjamin Herrenschmidt wrote:
> >
> > >
> > > >
> > > > Can you please put the 970 register definitions into
> > > > include/asm-ppc/reg_970.h or something along those lines?
> > >
> > > I won't create a file for 3 registers :) Also, HID2/3 are defined
> > > on other CPUs, as HIOR, none of these are strictly 970 specific
> > > in fact though we only use them on it (coment may need fixing, bu
> > > that's ok at this point).
> >
> > Are they found on regular, classic PPCs or just on others in the
> > 64bit family? The problem is we don't want to let <asm/reg.h> get to be
> > as bad as it used to be.
>
> HID2 exist on some 750FX afaik, HID3 and upper probably only on
> POWER4/GPUL at this point and HIOR is specific to HV capable CPUs,
> but then, afgain, it's only 3 registers :)
But that's how it starts out... :) If it turns out that you need to add
more regs in later, can you please move all of the POWER4/GPUL
definitions into their own file? Thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-01-26 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 2:38 [PATCH] Big powermac update Benjamin Herrenschmidt
2004-01-23 17:54 ` Tom Rini
2004-01-24 0:58 ` Benjamin Herrenschmidt
2004-01-25 18:55 ` Tom Rini
2004-01-26 0:09 ` Benjamin Herrenschmidt
2004-01-26 15:29 ` Tom Rini [this message]
2004-01-26 22:01 ` 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=20040126152921.GF15271@stop.crashing.org \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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.