Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tbogendoerfer@suse.de>
To: Paul Burton <paul.burton@mips.com>
Cc: Carlo Pisani <carlojpisani@gmail.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	Joshua Kinard <kumba@gentoo.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: SGI-IP30
Date: Tue, 25 Jun 2019 10:59:58 +0200	[thread overview]
Message-ID: <20190625105958.a7764976a3687cbb8d960a50@suse.de> (raw)
In-Reply-To: <20190624175553.2tpepq5zsamovrra@pburton-laptop>

On Mon, 24 Jun 2019 17:55:55 +0000
Paul Burton <paul.burton@mips.com> wrote:

> On Sat, Jun 22, 2019 at 02:42:05PM +0200, Carlo Pisani wrote:
> > hi guys
> > I am new on this mailing list, is there anyone on SGI-IP30?
> > I am with kernel 4.18, there are a few quirks ... with the SMP
> > 
> > =)
> 
> Since we don't have IP30 support upstream I presume you must be getting
> your kernel source from somewhere else?
> 
> I'm afraid I don't have access to any of these old SGI systems myself,
> but your best chances are probably:
> 
> - Thomas Bodendoerfer who's recently done some work refactoring IP27
>   code in an effort to also support IP30 & other systems.

I have a patchset ready for IP30 support, but I'm waiting for two other patchsets,
which need to get merged first :-( This is

https://marc.info/?l=linux-kernel&m=155929848918599&w=2
https://marc.info/?l=linux-kernel&m=155929849418602&w=2

and

https://marc.info/?l=linux-kernel&m=156044570923085&w=2

If wanted I can post the IP30 patchset for review and testing.

Thomas.

-- 
SUSE Linux GmbH
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)

  parent reply	other threads:[~2019-06-25  9:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-22 12:40 Call trace stops at static callback functions Hauke Mehrtens
2019-06-22 12:42 ` SGI-IP30 Carlo Pisani
2019-06-24 17:55   ` SGI-IP30 Paul Burton
2019-06-24 19:16     ` SGI-IP30 Maciej W. Rozycki
2019-06-25  8:59     ` Thomas Bogendoerfer [this message]
2019-06-26  4:23     ` SGI-IP30 Joshua Kinard
2019-06-26  5:49       ` SGI-IP30 Carlo Pisani
2019-07-01 19:27         ` SGI-IP30 Joshua Kinard
2019-06-27 20:38       ` SGI-IP30 Matt Turner
2019-06-27 22:29         ` SGI-IP30 Carlo Pisani
2019-06-28  8:27           ` SGI-IP30 Carlo Pisani
2019-07-01 18:31             ` SGI-IP30 Joshua Kinard
2019-07-01 18:36               ` SGI-IP30 Carlo Pisani
2019-07-01 20:29                 ` SGI-IP30 Joshua Kinard
2019-07-01 20:41                   ` SGI-IP30 Carlo Pisani
2019-06-28  9:46         ` SGI-IP30 Carlo Pisani
2019-06-24 18:10 ` Call trace stops at static callback functions Paul Burton

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=20190625105958.a7764976a3687cbb8d960a50@suse.de \
    --to=tbogendoerfer@suse.de \
    --cc=carlojpisani@gmail.com \
    --cc=kumba@gentoo.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=paul.burton@mips.com \
    /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