From: Chen Gang <chengang@emindsoft.com.cn>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Thomas Huth <thuth@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Guan Xuetao <gxt@mprc.pku.edu.cn>,
Chen Gang <gang.chen.5i5j@gmail.com>,
Chen Gang <xili_gchen_5257@hotmail.com>,
Richard Henderson <rth@twiddle.net>,
Chris Metcalf <cmetcalf@ezchip.com>,
"walt@tilera.com" <walt@tilera.com>
Subject: Re: [Qemu-devel] Deprecate tilegx ?
Date: Wed, 14 Mar 2018 00:37:45 +0800 [thread overview]
Message-ID: <5AA7FE59.9020206@emindsoft.com.cn> (raw)
In-Reply-To: <c7b075f5-8084-99c0-02e0-3da555bea4df@mail.uni-paderborn.de>
On 2/28/18 20:41, Bastian Koppelmann wrote:
> On 02/28/2018 07:11 AM, Thomas Huth wrote:
>> On 27.02.2018 12:51, Peter Maydell wrote:
>>
>>> Possibly there are other target architectures we could reasonably
>>> deprecate-and-remove (though none of the other ones Linux is dropping
>>> in this round are ones we support)...
>>
>> I'd vote for marking tilegx as deprecated, too, since we even do not
>> have an active maintainer for that CPU core (at least I did not spot one
>> in our MAINTAINERS file). Opinions?
>
> I always saw it as a big plus that QEMU supports nearly any
> architecture, no matter how obscure it is. So I'm a bit more hesitant on
> dropping architectures quickly.
>
Firstly, sorry for too long time to no response about tilegx.
During latest 2 years, I turned to android development (custom aosp with
java/c++/c, merge android and linux together), and revert engineering
about android (java/c).
At present, sorry, I really have no time for tilegx any more. :(
For me, tilegx is still a good platform, and we have done much things,
now, so if we can find another maintainers/volunteers for it, I hope
qemu can still support tilegx.
By the way, for floating point instructions patches, I have sent before
(2 years ago), it seems I did not get any reply. I hope they are useful
for tilegx.
Thanks.
--
Chen Gang (陈刚)
next prev parent reply other threads:[~2018-03-13 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 11:51 [Qemu-devel] Proposal: deprecate and remove QEMU's unicore32 target code Peter Maydell
2018-02-27 11:56 ` Daniel P. Berrangé
2018-02-28 6:11 ` [Qemu-devel] Deprecate tilegx ? (was: Proposal: deprecate and remove QEMU's unicore32 target code) Thomas Huth
2018-02-28 7:17 ` [Qemu-devel] Deprecate tilegx ? Paolo Bonzini
2018-02-28 10:38 ` Thomas Huth
2018-02-28 12:41 ` Bastian Koppelmann
2018-03-09 15:13 ` Alex Bennée
2018-03-13 17:18 ` Bastian Koppelmann
2018-03-13 17:39 ` Peter Maydell
2018-03-14 9:09 ` Xuetao Guan
2018-03-14 10:11 ` Laurent Vivier
2018-03-14 12:01 ` Xuetao Guan
2018-03-17 8:06 ` Waldemar Brodkorb
2018-03-13 16:37 ` Chen Gang [this message]
2018-03-09 14:08 ` [Qemu-devel] Proposal: deprecate and remove QEMU's unicore32 target code Xuetao Guan
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=5AA7FE59.9020206@emindsoft.com.cn \
--to=chengang@emindsoft.com.cn \
--cc=cmetcalf@ezchip.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=kbastian@mail.uni-paderborn.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
--cc=walt@tilera.com \
--cc=xili_gchen_5257@hotmail.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 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.