From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: Linux on sparc v7
Date: Tue, 22 May 2012 06:28:24 +0000 [thread overview]
Message-ID: <4FBB3208.3040509@gaisler.com> (raw)
In-Reply-To: <4FBA4DBC.9070609@gaisler.com>
On 05/21/2012 06:16 PM, Sam Ravnborg wrote:
> On Mon, May 21, 2012 at 04:14:20PM +0200, Daniel Hellstrom wrote:
>> Hello Dave,
>>
>> I am trying to catch up on what has been happening lately with the sparc
>> port. Have the latest patches removed support for SPARC V7 CPUs?
> Yes. The sun4c were the only users of v7 so today we tell gcc to generate v8
> code. This imply support for muldiv& friends.
>
> > From the sparc Makefile:
>
> KBUILD_CFLAGS += -mcpu=v8
Does this mean that if we change it to mcpu=v7 or mcpu=cypress (or removing mcpu=v8) the kernel can still be run on a V7 CPU? Or have software routines for making V8 mul/div operations on a V7 CPU
been removed so that V7 CPUs can't run Linux regardless of compiler option?
> As a side-note - we require support for the "flush" instruction now.
> I assume LEON support this.
Yes, flush invalidates all of the instruction cache.
>> The LEON VHDL model supports both V7 and V8 CPUs,
>> FPU and non-FPU in any combination.
> I do not have any overview on the FPU side of things.
Thanks,
Daniel
next prev parent reply other threads:[~2012-05-22 6:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 14:14 Linux on sparc v7 Daniel Hellstrom
2012-05-21 16:16 ` Sam Ravnborg
2012-05-22 6:28 ` Daniel Hellstrom [this message]
2012-05-22 6:31 ` Julian Calaby
2012-05-22 15:20 ` David Miller
2012-05-23 12:27 ` Daniel Hellstrom
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=4FBB3208.3040509@gaisler.com \
--to=daniel@gaisler.com \
--cc=sparclinux@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.