All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Guenter Roeck <linux@roeck-us.net>, Arnd Bergmann <arnd@arndb.de>,
	linux-arch <linux-arch@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Richard Kuo <rkuo@codeaurora.org>,
	linux-hexagon@vger.kernel.org, Chen Liqin <liqin.linux@gmail.com>,
	Lennox Wu <lennox.wu@gmail.com>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	Al Viro <viro@zeniv.linux.org.uk>,
	James Hogan <jhogan@kernel.org>,
	linux-metag@vger.kernel.org, Jonas Bonn <jonas@southpole.se>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	Stafford Horne <shorne@gmail.com>,
	openrisc@lists.librecores.org,
	David Howells <dhowells@redhat.com>
Subject: Re: Removing architectures without upstream gcc support
Date: Sun, 25 Feb 2018 23:50:02 +0100	[thread overview]
Message-ID: <20180225225002.GA6078@amd> (raw)
In-Reply-To: <20180225202806.735a6870@alans-desktop>

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

Hi!

On Sun 2018-02-25 20:28:06, Alan Cox wrote:
> > FWIW, alpha and m68k are known boot with qemu (even though m68k
> > generates a warning traceback with the mainline kernel).
> 
> M68K works - people actively use it. Crazy people true 8). Alpha I
> believe one or two people boot. I just need to track down some discs for
> my Alpha 8)

I guess it would be useful to track who tested what kernel on what
hardware ... and I created a project for
that. Feel free to contribute: https://github.com/pavelmachek/missy --
I'd like to get some data from "big" iron...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Removing architectures without upstream gcc support
Date: Sun, 25 Feb 2018 23:50:02 +0100	[thread overview]
Message-ID: <20180225225002.GA6078@amd> (raw)
In-Reply-To: <20180225202806.735a6870@alans-desktop>

Hi!

On Sun 2018-02-25 20:28:06, Alan Cox wrote:
> > FWIW, alpha and m68k are known boot with qemu (even though m68k
> > generates a warning traceback with the mainline kernel).
> 
> M68K works - people actively use it. Crazy people true 8). Alpha I
> believe one or two people boot. I just need to track down some discs for
> my Alpha 8)

I guess it would be useful to track who tested what kernel on what
hardware ... and I created a project for
that. Feel free to contribute: https://github.com/pavelmachek/missy --
I'd like to get some data from "big" iron...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20180225/cd29939c/attachment.sig>

  reply	other threads:[~2018-02-25 22:50 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 15:45 Removing architectures without upstream gcc support Arnd Bergmann
2018-02-22 15:45 ` [OpenRISC] " Arnd Bergmann
2018-02-22 15:52 ` Lennox Wu
2018-02-22 16:02 ` Christoph Hellwig
2018-02-22 16:02   ` [OpenRISC] " Christoph Hellwig
2018-02-22 16:19   ` Arnd Bergmann
2018-02-22 16:19     ` [OpenRISC] " Arnd Bergmann
2018-02-22 17:14   ` Max Filippov
2018-02-22 17:14     ` [OpenRISC] " Max Filippov
2018-02-22 18:04     ` Christoph Hellwig
2018-02-22 18:04       ` [OpenRISC] " Christoph Hellwig
2018-02-23 11:37       ` Arnd Bergmann
2018-02-23 11:37         ` [OpenRISC] " Arnd Bergmann
2018-02-28  8:59         ` Florian Weimer
2018-02-28  8:59           ` [OpenRISC] " Florian Weimer
2018-02-22 16:07 ` Lennox Wu
2018-02-22 16:07   ` [OpenRISC] " Lennox Wu
2018-02-22 16:28 ` James Hogan
2018-02-22 16:28   ` [OpenRISC] " James Hogan
2018-02-22 16:34   ` Arnd Bergmann
2018-02-22 16:34     ` [OpenRISC] " Arnd Bergmann
2018-02-22 19:17 ` Richard Kuo
2018-02-22 19:17   ` [OpenRISC] " Richard Kuo
2018-02-22 22:43   ` Arnd Bergmann
2018-02-22 22:43     ` [OpenRISC] " Arnd Bergmann
2018-02-23 17:15     ` Richard Kuo
2018-02-23 17:15       ` [OpenRISC] " Richard Kuo
2018-02-28  2:06     ` Richard Kuo
2018-02-28  2:06       ` [OpenRISC] " Richard Kuo
2018-02-28  8:37       ` Arnd Bergmann
2018-02-28  8:37         ` [OpenRISC] " Arnd Bergmann
2018-03-03  1:43         ` Richard Kuo
2018-03-03  1:43           ` [OpenRISC] " Richard Kuo
2018-02-22 23:48 ` Guenter Roeck
2018-02-22 23:48   ` [OpenRISC] " Guenter Roeck
2018-02-23 10:32   ` Arnd Bergmann
2018-02-23 10:32     ` [OpenRISC] " Arnd Bergmann
2018-02-23 12:09     ` Andy Shevchenko
2018-02-23 12:09       ` [OpenRISC] " Andy Shevchenko
2018-02-23 12:20       ` Arnd Bergmann
2018-02-23 12:20         ` [OpenRISC] " Arnd Bergmann
2018-02-23 14:32     ` Guenter Roeck
2018-02-23 14:32       ` [OpenRISC] " Guenter Roeck
2018-02-23 15:43     ` Alan Cox
2018-02-23 15:43       ` [OpenRISC] " Alan Cox
2018-02-23 17:10       ` Guenter Roeck
2018-02-23 17:10         ` [OpenRISC] " Guenter Roeck
2018-02-23 18:19         ` Al Viro
2018-02-23 18:19           ` [OpenRISC] " Al Viro
2018-02-23 19:32           ` James Bottomley
2018-02-23 19:32             ` [OpenRISC] " James Bottomley
2018-02-23 21:34             ` Adam Borowski
2018-02-23 21:34               ` [OpenRISC] " Adam Borowski
2018-02-24  4:04               ` Guenter Roeck
2018-02-24  4:04                 ` [OpenRISC] " Guenter Roeck
2018-02-24 21:55             ` Guenter Roeck
2018-02-24 21:55               ` [OpenRISC] " Guenter Roeck
2018-02-25 19:39           ` Richard Henderson
2018-02-25 19:39             ` Richard Henderson
2018-02-23 23:49         ` Greg Ungerer
2018-02-23 23:49           ` [OpenRISC] " Greg Ungerer
2018-02-25 20:28         ` Alan Cox
2018-02-25 20:28           ` [OpenRISC] " Alan Cox
2018-02-25 22:50           ` Pavel Machek [this message]
2018-02-25 22:50             ` Pavel Machek
2018-02-24  0:15 ` Florian Fainelli
2018-02-24  0:15   ` [OpenRISC] " Florian Fainelli
2018-02-26  8:26   ` Arnd Bergmann
2018-02-26  8:26     ` [OpenRISC] " Arnd Bergmann
2018-02-26 22:11     ` Eric W. Biederman
2018-02-26 22:11       ` Eric W. Biederman
2018-02-26 22:11       ` [OpenRISC] " Eric W. Biederman
     [not found]     ` <5ef16c51-7cc5-9111-7e54-edfe77f39f4b@metafoo.de>
2018-03-05 10:57       ` Wu, Aaron
2018-03-05 10:57         ` [OpenRISC] " Wu, Aaron
2018-03-06  9:38         ` Arnd Bergmann
2018-03-06  9:38           ` [OpenRISC] " Arnd Bergmann
2018-03-06 10:35           ` Wu, Aaron
2018-03-06 10:35             ` [OpenRISC] " Wu, Aaron
2018-03-06 10:38             ` Arnd Bergmann
2018-03-06 10:38               ` [OpenRISC] " Arnd Bergmann
2018-02-25 15:43 ` Philipp Wagner
2018-02-25 15:43   ` Philipp Wagner
2018-02-26  8:00   ` Arnd Bergmann
2018-02-26  8:00     ` Arnd Bergmann
2018-02-26 12:10     ` Philipp Wagner
2018-02-26 12:10       ` Philipp Wagner
2018-02-26 15:24       ` whitequark
2018-02-26 15:24         ` whitequark
2018-03-09 14:00 ` Xuetao Guan
2018-03-09 14:00   ` [OpenRISC] " 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=20180225225002.GA6078@amd \
    --to=pavel@ucw.cz \
    --cc=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gxt@mprc.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 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.