From: Fuxin Zhang <fxzhang@ict.ac.cn>
To: Thiemo Seufer <ths@networkno.de>
Cc: tiansm@lemote.com, linux-mips@linux-mips.org,
Fuxin Zhang <zhangfx@lemote.com>
Subject: Re: [PATCH 2/16] arch related Makefile update for lemote fulong mini-PC
Date: Mon, 16 Apr 2007 16:48:50 +0800 [thread overview]
Message-ID: <46233872.7010206@ict.ac.cn> (raw)
In-Reply-To: <20070415222847.GA1402@networkno.de>
>> +cflags-$(CONFIG_CPU_LOONGSON2) += -march=r4600 -Wa,--trap
>
> I wonder why this is r4600. I heard the Loongson2 is MIPS IV compatible,
> so r5000 / r8000 / r10000 would be better choices.
Presently Loongson-2E is nearly MIPS III compatible(with some
self-defined extensions), next version will be mips64 release2 compatible.
-march=r4600 is inherited from loongson-1, -march=mips3 might be a
better choice.
>
>
> Thiemo
>
>
>
>
next prev parent reply other threads:[~2007-04-16 8:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 15:25 lemote-fulong patch update tiansm
2007-04-15 15:25 ` [PATCH 1/16] new files for lemote fulong mini-PC support tiansm
2007-04-15 15:25 ` [PATCH 2/16] arch related Makefile update for lemote fulong mini-PC tiansm
2007-04-15 15:25 ` [PATCH 3/16] Kconfig " tiansm
2007-04-15 15:25 ` [PATCH 4/16] TO_PHYS_MASK for loongson2 tiansm
2007-04-15 15:25 ` [PATCH 5/16] add MACH_GROUP_LEMOTE & MACH_LEMOTE_FULONG tiansm
2007-04-15 15:25 ` [PATCH 6/16] define Hit_Invalidate_I to Index_Invalidate_I for loongson2 tiansm
2007-04-15 15:25 ` [PATCH 7/16] add Loongson processor definitions tiansm
2007-04-15 15:25 ` [PATCH 8/16] define MODULE_PROC_FAMILY for Loongson2 tiansm
2007-04-15 15:25 ` [PATCH 9/16] add serial port definition for lemote fulong tiansm
2007-04-15 15:25 ` [PATCH 10/16] make cpu_probe recognize Loongson2 tiansm
2007-04-15 15:26 ` [PATCH 11/16] add Loongson support to /proc/cpuinfo tiansm
2007-04-15 15:26 ` [PATCH 12/16] cheat for support of more than 256MB memory tiansm
2007-04-15 15:26 ` [PATCH 13/16] define MODULE_PROC_FAMILY for Loongson2 tiansm
2007-04-15 15:26 ` [PATCH 14/16] tlb handling support for Loongson2 processor tiansm
2007-04-15 15:26 ` [PATCH 15/16] work around for more than 256MB memory support tiansm
2007-04-15 15:26 ` [PATCH 16/16] alsa sound support for mips tiansm
2007-04-18 13:54 ` Ralf Baechle
2007-04-18 14:13 ` Fuxin Zhang
2007-04-20 9:39 ` Atsushi Nemoto
2007-04-18 12:11 ` [PATCH 6/16] define Hit_Invalidate_I to Index_Invalidate_I for loongson2 Ralf Baechle
2007-04-18 13:51 ` Fuxin Zhang
2007-04-18 13:56 ` Fuxin Zhang
2007-04-18 12:02 ` [PATCH 4/16] TO_PHYS_MASK " Ralf Baechle
2007-04-18 12:06 ` [PATCH 3/16] Kconfig update for lemote fulong mini-PC Ralf Baechle
2007-04-18 13:32 ` Fuxin Zhang
2007-04-18 15:28 ` Uhler, Mike
2007-04-18 15:28 ` Uhler, Mike
2007-04-18 15:43 ` Fuxin Zhang
2007-04-18 16:38 ` Ralf Baechle
2007-04-18 22:27 ` Uhler, Mike
2007-04-18 22:27 ` Uhler, Mike
2007-04-19 0:34 ` Ralf Baechle
2007-04-15 22:28 ` [PATCH 2/16] arch related Makefile " Thiemo Seufer
2007-04-16 7:37 ` Tian
2007-04-16 8:48 ` Fuxin Zhang [this message]
2007-04-16 8:49 ` Zhang Fuxin
2007-04-16 12:44 ` Thiemo Seufer
2007-04-16 14:01 ` Ralf Baechle
2007-04-16 15:10 ` Zhang Fuxin
-- strict thread matches above, loose matches on Subject: below --
2007-04-04 14:38 zhangfx
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=46233872.7010206@ict.ac.cn \
--to=fxzhang@ict.ac.cn \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
--cc=tiansm@lemote.com \
--cc=zhangfx@lemote.com \
/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