From: Knut Omang <knut.omang@oracle.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures
Date: Sun, 26 Mar 2017 11:16:38 +0200 [thread overview]
Message-ID: <1490519798.11328.113.camel@oracle.com> (raw)
In-Reply-To: <CAFEAcA-BaDtJyNk0pB7AwyJNXtZ8V9LgJzcuAfPbN65b7OFsSw@mail.gmail.com>
On Sat, 2017-03-25 at 21:15 +0000, Peter Maydell wrote:
> On 25 March 2017 at 20:49, Knut Omang <knut.omang@oracle.com> wrote:
> >
> > Can we please keep the Sparc support in for a while still?
>
> Yes, John Paul Adrian Glaubitz and the Debian Project have
> kindly provided me with access to a Sparc box. I'm planning
> to send a patch that puts sparc into the 'supported'
> category before 2.9 release.
good to hear!
> I would note that so far I've found a couple of TCG
> bugs of the "this just doesn't work at all" level, so
> it doesn't look like anybody using sparc has been
> doing any testing against git master...
No, I tried a while ago myself without much success so there's awareness
about this sad state. Hopefully we can get some momentum on it soon.
> >
> > When it comes to build platforms, a legitimate need to be able to keep
> > anything
> > running, I don't have any authority to promise away hardware or other forms
> > of
> > Sparc access, but I have been told that that part can be worked out in some
> > way
> > if we get enough support for this internally.
>
> I'd recommend trying to get a machine into the gcc compile
> farm (assuming they'd be willing to take it) -- that way
> it's accessible to developers for a range of open
> source projects.
I'll bring that suggestion forward,
Thanks,
Knut
>
> thanks
> -- PMM
next prev parent reply other threads:[~2017-03-26 9:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 15:23 [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures Peter Maydell
2017-03-16 15:46 ` Daniel P. Berrange
2017-03-16 15:55 ` Peter Maydell
2017-03-16 16:00 ` Daniel P. Berrange
2017-03-16 16:06 ` Peter Maydell
2017-03-16 16:12 ` Daniel P. Berrange
2017-03-17 9:09 ` Markus Armbruster
2017-03-16 16:52 ` Paolo Bonzini
2017-03-17 9:09 ` Thomas Huth
2017-03-17 10:12 ` Daniel P. Berrange
2017-03-17 10:15 ` Peter Maydell
2017-03-17 10:30 ` Thomas Huth
2017-03-17 10:48 ` Peter Maydell
2017-03-16 18:59 ` Dr. David Alan Gilbert
2017-03-17 9:58 ` Peter Maydell
2017-03-21 17:59 ` Eric Blake
2017-03-16 15:57 ` Gerd Hoffmann
2017-03-16 16:16 ` Daniel P. Berrange
2017-03-16 16:27 ` Peter Maydell
2017-03-16 18:01 ` Peter Maydell
2017-03-16 18:08 ` Daniel P. Berrange
2017-03-22 12:51 ` Alex Bennée
2017-03-22 13:09 ` Peter Maydell
2017-03-22 13:24 ` Thomas Huth
2017-03-23 10:33 ` Paolo Bonzini
2017-03-23 11:02 ` Peter Maydell
2017-03-24 1:28 ` Richard Henderson
2017-03-24 17:24 ` Peter Maydell
2017-03-22 19:07 ` [Qemu-devel] rawhide gcc failures [was: Proposal for deprecating unsupported host OSes & architecutures] Eric Blake
2017-03-22 19:39 ` Philippe Mathieu-Daudé
2017-03-27 6:36 ` Fam Zheng
2017-03-22 22:33 ` Peter Maydell
2017-03-23 9:25 ` Alex Bennée
2017-03-25 20:49 ` [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures Knut Omang
2017-03-25 21:15 ` Peter Maydell
2017-03-26 9:16 ` Knut Omang [this message]
2017-03-27 16:32 ` Peter Maydell
2017-03-28 18:34 ` Knut Omang
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=1490519798.11328.113.camel@oracle.com \
--to=knut.omang@oracle.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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.