All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xuetao Guan" <gxt@mprc.pku.edu.cn>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Guan Xuetao <gxt@mprc.pku.edu.cn>,
	Riku Voipio <riku.voipio@iki.fi>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] proposal: drop linux-user unicore32 support from QEMU
Date: Mon, 12 Sep 2016 08:51:09 +0800 (CST)	[thread overview]
Message-ID: <64501.117.114.135.40.1473641469.squirrel@mprc.pku.edu.cn> (raw)
In-Reply-To: <CAFEAcA-dyahrrzwk_mc2ad6x-Su21RSua1UA+8LS=rfWA6126w@mail.gmail.com>

> On 14 June 2016 at 14:43, Xuetao Guan <gxt@mprc.pku.edu.cn> wrote:
>>> On 20 May 2016 at 13:48, Riku Voipio <riku.voipio@iki.fi> wrote:
>>>> On torstaina 12. toukokuuta 2016 17.34.42 EEST, Peter Maydell wrote:
>>>>> We should either fix our unicore32 support to use the real
>>>>> syscall numbers, or just drop it; since nobody has touched
>>>>> linux-user/unicore32 since 2012, and there have been no
>>>>> commits to target-unicore32 that aren't generic "clean up
>>>>> all targets" type patches since 2012 or 2013, and nobody
>>>>> has ever complained that the syscall numbers are all broken,
>>>>> my initial inclination is to say we should just drop this.
>>>>>
>>>>> Opinions?
>>>
>>>> I agree. I don't have a test setup for unicore, so unicore
>>>> has seen nothing but compile testing...
>>>
>>> I've put a note in the 2.7 Changelog saying we're going to
>>> remove unicore32-linux-user in 2.8.
>
>> I'm the maintainer of target-unicore32.
>> Though there's no commit since 2012, we're using qemu (but
>> old version) to test our new kernel and software-images.
>> I'll upgrade to new qemu and fix syscall problem.
>
> Hi -- just a reminder that I would like to see the unicore32
> support updated to use the correct syscall numbers if we
> are not to remove the code for 2.8. You have until about
> the middle of October before 2.8 softfreeze.
>
> thanks
> -- PMM
>
Sure, I'll fix it in this month.
Sorry for inconvenience.

Xuetao

  reply	other threads:[~2016-09-12  0:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 14:34 [Qemu-devel] proposal: drop linux-user unicore32 support from QEMU Peter Maydell
2016-05-12 17:19 ` Richard Henderson
2016-05-20 12:48 ` Riku Voipio
2016-06-14 12:14   ` Peter Maydell
2016-06-14 13:43     ` Xuetao Guan
2016-09-11 15:08       ` Peter Maydell
2016-09-12  0:51         ` Xuetao Guan [this message]
2016-09-22 15:09 MPRC
2016-09-23  7:46 ` Riku Voipio
2016-09-26  5:45   ` Xuetao Guan
2016-09-28 16:18     ` Riku Voipio
2016-09-29  8:04       ` 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=64501.117.114.135.40.1473641469.squirrel@mprc.pku.edu.cn \
    --to=gxt@mprc.pku.edu.cn \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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.