From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, LKML <linux-kernel@vger.kernel.org>,
huhb@lemote.com, yanh@lemote.com, Zhang Le <r0bertz@gentoo.org>,
Thomas Gleixner <tglx@linutronix.de>,
Nicholas Mc Guire <der.herr@hofr.at>,
zhangfx@lemote.com, liujl@lemote.com
Subject: Re: [PATCH -queue v0 1/6] [loongson] add basic loongson-2f support
Date: Thu, 05 Nov 2009 19:00:16 +0800 [thread overview]
Message-ID: <1257418816.3067.8.camel@falcon.domain.org> (raw)
In-Reply-To: <20091105102838.GF12582@linux-mips.org>
Hi,
> > > You're ifdefing on Loongson 2F - doesn't that mean that you can't have a
> > > kernel that supports both Loongson 2E and 2F?
> > >
> >
> > Currently, not consider it yet;) It's a little hard to cope with, should
> > we consider it at this moment? if yes, I will try it with the help of
> > exisiting machtype asap. but I think it's better to let it be the future
> > job ;)
>
> Fair enough - though I'm sure Linux distributions would be happy to have
> one kernel variant less to ship.
>
Yup, linux distributions will like it.
but just remembered that: the instruciton set of loongson2e and
loongson2f is different, -march=loongson2e, -march=loongson2f. so it
will be not possible to merge them together, but I will try to merge the
2f support, so please wait for me merging fuloong2f & yeeloon2f, I will
do it tonight, it is really an interesting job to do ;)
Regards,
Wu Zhangjin
next prev parent reply other threads:[~2009-11-05 11:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1257325319.git.wuzhangjin@gmail.com>
2009-11-04 9:04 ` [PATCH -queue v0 1/6] [loongson] add basic loongson-2f support Wu Zhangjin
2009-11-04 10:28 ` Arnaud Patard
2009-11-04 11:04 ` Wu Zhangjin
2009-11-04 11:19 ` Ralf Baechle
2009-11-04 15:23 ` Wu Zhangjin
2009-11-04 20:15 ` Ralf Baechle
2009-11-05 1:39 ` Wu Zhangjin
2009-11-05 8:45 ` Ralf Baechle
2009-11-04 11:36 ` Arnaud Patard
2009-11-05 9:18 ` Ralf Baechle
2009-11-05 9:48 ` Wu Zhangjin
2009-11-05 10:28 ` Ralf Baechle
2009-11-05 11:00 ` Wu Zhangjin [this message]
2009-11-04 9:05 ` [PATCH -queue v0 2/6] [loongson] oprofile: avoid do_IRQ for perfcounter when the interrupt is from bonito Wu Zhangjin
2009-11-04 9:05 ` [PATCH -queue v0 3/6] [loongson] add basic cs5536 vsm support Wu Zhangjin
2009-11-04 9:05 ` [PATCH -queue v0 4/6] [loongson] add basic fuloong2f support Wu Zhangjin
2009-11-05 13:16 ` Ralf Baechle
2009-11-05 14:44 ` Wu Zhangjin
2009-11-06 5:39 ` Wu Zhangjin
2009-11-06 8:30 ` Ralf Baechle
2009-11-06 10:05 ` Wu Zhangjin
2009-11-06 8:34 ` Wu Zhangjin
2009-11-04 9:06 ` [PATCH -queue v0 5/6] [loongson] rtc: enable legacy RTC driver on fuloong2f Wu Zhangjin
2009-11-04 10:40 ` Arnaud Patard
2009-11-04 11:18 ` Wu Zhangjin
2009-11-04 11:34 ` Arnaud Patard
2009-11-04 14:15 ` Ralf Baechle
2009-11-04 15:12 ` Wu Zhangjin
2009-11-04 9:06 ` [PATCH -queue v0 6/6] [loongson] add default config file for fuloong2f Wu Zhangjin
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=1257418816.3067.8.camel@falcon.domain.org \
--to=wuzhangjin@gmail.com \
--cc=der.herr@hofr.at \
--cc=huhb@lemote.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=liujl@lemote.com \
--cc=r0bertz@gentoo.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=yanh@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