From: Arnd Bergmann <arnd@arndb.de>
To: Guan Xuetao <gxt@pku.edu.cn>
Cc: linux-arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Richard Kuo <rkuo@codeaurora.org>,
linux-hexagon <linux-hexagon@vger.kernel.org>,
Chen Liqin <liqin.linux@gmail.com>,
Lennox Wu <lennox.wu@gmail.com>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Guenter Roeck <linux@roeck-us.net>,
Al Viro <viro@zeniv.linux.org.uk>,
James Hogan <jhogan@kernel.org>,
linux-metag <linux-metag@vger.kernel.org>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Stafford Horne <shorne@gmail.com>,
David Howells <dhowells@redhat.com>,
openrisc@lists.librecores.org
Subject: Re: Removing architectures without upstream gcc support
Date: Fri, 9 Mar 2018 15:33:47 +0100 [thread overview]
Message-ID: <CAK8P3a1v3XuwhRacboXK7AZQD32JMsc3bY74KdchEWSYVd0y7g@mail.gmail.com> (raw)
In-Reply-To: <23bf54ca.a08c.1620b20bd53.Coremail.gxt@pku.edu.cn>
On Fri, Mar 9, 2018 at 3:18 PM, Guan Xuetao <gxt@pku.edu.cn> wrote:
> Since mprc.pku.edu.cn is blocked, I use this email account to send the email again.
>
>> * unicore32 was a research project at Peking University with a SoC
>> based on the Intel PXA design. No gcc source code has ever been
>> published, the only toolchain available is a set of binaries that
>> include
>> a gcc-4.4 compiler. The project page at
>> http://mprc.pku.edu.cn/~guanxuetao/linux/ has a TODO list that has
>> not been modified since 2011. The maintainer still Acks patches
>> and has last sent a pull request in 2014 and last sent a patch of
>> his own in 2012 when the project appears to have stalled.
>> I would suggest removing this one.
>>
> Hi, Arnd.
> I am really sorry to reply so late, since I seldom use this email account
> in recent years. I will add my new email account to related bits.
>
> Let me clarify the status of UniCore. It's a real cpu-core product,
> integrated into PKUnity SoC, and sold in a large amount of embedded boxes,
> such as cloud terminals and set top boxes. Surely, we still use the port
> internally and keep doing developments in other projects. So, I really
> appreciate having unicore32 port in the tree.
Ok, thanks for your reply, I'm dropping my removal patch then and will
try to document the current status better.
Can you send me a patch to the MAINTAINERS file update to the email
address? If you have no other patches at this point, I'll add that to my
patch series so at least you can be reached more easily.
> As to gnu toolchain of UniCore, I have already discussed it in my group,
> and I'll do my best to propel it forward.
Thanks, that would be very helpful!
Arnd
next prev parent reply other threads:[~2018-03-09 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 14:18 Removing architectures without upstream gcc support Guan Xuetao
2018-03-09 14:33 ` Arnd Bergmann [this message]
[not found] <CAK8P3a2-6YwRR3j7J78fVHSvDpq8Kf4wRj6d9mnGgAxgkYypxg@mail.gmail.com>
[not found] ` <20180222234833.GA3047@roeck-us.net>
[not found] ` <CAK8P3a3Y2b-DivYz1ZqhFGUqQaiF=5SDB6RFLtCknwY2--09OQ@mail.gmail.com>
[not found] ` <20180223154316.35b26857@alans-desktop>
[not found] ` <20180223171019.GA1125@roeck-us.net>
[not found] ` <20180225202806.735a6870@alans-desktop>
2018-02-25 22:50 ` Pavel Machek
[not found] ` <2d12dc77-16b9-417d-72e3-2b1ffa38803d@gmail.com>
2018-02-26 8:26 ` Arnd Bergmann
2018-02-26 22:11 ` Eric W. Biederman
[not found] ` <20180222191758.GB5180@codeaurora.org>
[not found] ` <CAK8P3a3r=3wDtqV5feLUT-hOkE+9yWOLjLVm+nejqdaN7MtMFw@mail.gmail.com>
2018-02-28 2:06 ` Richard Kuo
2018-02-28 8:37 ` Arnd Bergmann
2018-03-03 1:43 ` Richard Kuo
[not found] ` <20180222160217.GA18243@infradead.org>
[not found] ` <CAMo8BfLoqat+6CyOM2VV5Wz13NFMj54YisCogiVm95oDwdnTFQ@mail.gmail.com>
[not found] ` <20180222180420.GA17956@infradead.org>
[not found] ` <CAK8P3a2VMbAARCFuBjY7TMuAfGM_h4BU3PfQA2C_pUFT34UHAA@mail.gmail.com>
2018-02-28 8:59 ` Florian Weimer
2018-03-09 14:00 ` 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=CAK8P3a1v3XuwhRacboXK7AZQD32JMsc3bY74KdchEWSYVd0y7g@mail.gmail.com \
--to=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=gxt@pku.edu.cn \
--cc=jhogan@kernel.org \
--cc=jonas@southpole.se \
--cc=lennox.wu@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=liqin.linux@gmail.com \
--cc=openrisc@lists.librecores.org \
--cc=rkuo@codeaurora.org \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).