From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Removing architectures without upstream gcc support
Date: Fri, 23 Feb 2018 14:32:08 -0500 [thread overview]
Message-ID: <1519414328.30443.29.camel@HansenPartnership.com> (raw)
In-Reply-To: <20180223181943.GF30522@ZenIV.linux.org.uk>
On Fri, 2018-02-23 at 18:19 +0000, Al Viro wrote:
[...]
> IIRC, parisc/qemu stuff had been announced a while ago;
I have, but it didn't work sufficiently for me to either boot a kernel
using system emulation or start an architecture container using user
emulation. I'll try again now that qemu has gone through several
revisions.
> I hadn't tried that yet (got an old parisc box, so 32bit testing can
> be done on that).
The mailing list (linux-parisc at vger.kernel.org) does regular build
testing on a variety of 32 and 64 bit hardware.
James
next prev parent reply other threads:[~2018-02-23 19:32 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 15:45 [OpenRISC] Removing architectures without upstream gcc support Arnd Bergmann
2018-02-22 15:52 ` Lennox Wu
2018-02-22 16:02 ` Christoph Hellwig
2018-02-22 16:19 ` Arnd Bergmann
2018-02-22 17:14 ` Max Filippov
2018-02-22 18:04 ` Christoph Hellwig
2018-02-23 11:37 ` Arnd Bergmann
2018-02-28 8:59 ` Florian Weimer
2018-02-22 16:07 ` Lennox Wu
2018-02-22 16:28 ` James Hogan
2018-02-22 16:34 ` Arnd Bergmann
2018-02-22 19:17 ` Richard Kuo
2018-02-22 22:43 ` Arnd Bergmann
2018-02-23 17:15 ` Richard Kuo
2018-02-28 2:06 ` Richard Kuo
2018-02-28 8:37 ` Arnd Bergmann
2018-03-03 1:43 ` Richard Kuo
2018-02-22 23:48 ` Guenter Roeck
2018-02-23 10:32 ` Arnd Bergmann
2018-02-23 12:09 ` Andy Shevchenko
2018-02-23 12:20 ` Arnd Bergmann
2018-02-23 14:32 ` Guenter Roeck
2018-02-23 15:43 ` Alan Cox
2018-02-23 17:10 ` Guenter Roeck
2018-02-23 18:19 ` Al Viro
2018-02-23 19:32 ` James Bottomley [this message]
2018-02-23 21:34 ` Adam Borowski
2018-02-24 4:04 ` Guenter Roeck
2018-02-24 21:55 ` Guenter Roeck
2018-02-25 19:39 ` Richard Henderson
2018-02-23 23:49 ` Greg Ungerer
2018-02-25 20:28 ` Alan Cox
2018-02-25 22:50 ` Pavel Machek
2018-02-24 0:15 ` Florian Fainelli
2018-02-26 8:26 ` Arnd Bergmann
2018-02-26 22:11 ` Eric W. Biederman
[not found] ` <5ef16c51-7cc5-9111-7e54-edfe77f39f4b@metafoo.de>
2018-03-05 10:57 ` Wu, Aaron
2018-03-06 9:38 ` Arnd Bergmann
2018-03-06 10:35 ` Wu, Aaron
2018-03-06 10:38 ` Arnd Bergmann
2018-02-25 15:43 ` Philipp Wagner
2018-02-26 8:00 ` Arnd Bergmann
2018-02-26 12:10 ` Philipp Wagner
2018-02-26 15:24 ` whitequark
2018-03-09 14:00 ` Xuetao Guan
-- strict thread matches above, loose matches on Subject: below --
2018-03-09 14:18 Guan Xuetao
2018-03-09 14:33 ` Arnd Bergmann
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=1519414328.30443.29.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=openrisc@lists.librecores.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox