From: Mike Uhler <uhler@mips.com>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: C0 config reg for 5k core
Date: 11 Aug 2003 13:00:30 -0700 [thread overview]
Message-ID: <1060632030.1071.29.camel@uhler-linux.mips.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0308111556500.4643-100000@ares.mmc.atmel.com>
For MIPS32 and MIPS64 processors (the 5K is MIPS64), it is
architecturally defined and required, and the compatibility
verification testing verifies it (and, yes, we do run compatibility
verification testing on our own cores).
/gmu
On Mon, 2003-08-11 at 12:57, David Kesselring wrote:
> Is this reg, supposed to be the same among all processor or does it
> differ?
>
> On 11 Aug 2003, Mike Uhler wrote:
>
> > Bit 0 of Config1 is FPU-present. Bit 4 is "Performance counters
> > present". I guarantee you that the 5K family implements this
> > pattern.
> >
> > /gmu
> >
> >
> > On Mon, 2003-08-11 at 11:28, David Kesselring wrote:
> > > Has anyone else built linux 2.4 for a 5k or 5kf core? When comparing cpu.h
> > > and the MIPS64 5K Processor Core Family Software Users Manual it doesn't
> > > look to me that the c0-config1 reg is defined the same way. Am I reading
> > > something wrong? For example in the spec FPU flag is bit0 while in cpu.h
> > > it is bit4. Seems pretty basic.
> > >
> > > David Kesselring
> > > Atmel MMC
> > > dkesselr@mmc.atmel.com
> > > 919-462-6587
> > --
> >
> > Michael Uhler, Chief Technology Officer
> > MIPS Technologies, Inc. Email: uhler@mips.com Pager:uhler_p@mips.com
> > 1225 Charleston Road Voice: (650)567-5025 FAX: (650)567-5225
> > Mountain View, CA 94043 Mobile: (650)868-6870 Admin: (650)567-5085
> >
> >
> >
> >
>
> David Kesselring
> Atmel MMC
> dkesselr@mmc.atmel.com
> 919-462-6587
--
Michael Uhler, Chief Technology Officer
MIPS Technologies, Inc. Email: uhler@mips.com Pager:uhler_p@mips.com
1225 Charleston Road Voice: (650)567-5025 FAX: (650)567-5225
Mountain View, CA 94043 Mobile: (650)868-6870 Admin: (650)567-5085
next prev parent reply other threads:[~2003-08-11 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 18:28 C0 config reg for 5k core David Kesselring
2003-08-11 19:32 ` Mike Uhler
2003-08-11 19:57 ` David Kesselring
2003-08-11 20:00 ` Mike Uhler [this message]
2003-08-12 11:21 ` Chris Dearman
2003-08-12 12:39 ` David Kesselring
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=1060632030.1071.29.camel@uhler-linux.mips.com \
--to=uhler@mips.com \
--cc=dkesselr@mmc.atmel.com \
--cc=linux-mips@linux-mips.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