From: Christoph Hellwig <hch@infradead.org>
To: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 00/3] MIPS: SGI-IP27 rework part2
Date: Tue, 7 May 2019 23:24:20 -0700 [thread overview]
Message-ID: <20190508062420.GD19227@infradead.org> (raw)
In-Reply-To: <20190507174820.381fd56f678609416fd8b617@suse.de>
On Tue, May 07, 2019 at 05:48:20PM +0200, Thomas Bogendoerfer wrote:
> > I had a look and the code is really, really MIPS specific, actually
> > I would be interested in understanding how many platforms it supports,
> > it is not even FW configurable.
>
> it's MIPS only and used in basically 3 different SGI platforms.
Actually this isn't quite true, this whole infraѕtructure was also
shared by the SGI IA64 systems.
The early SN1 prototypes were basically just IP35 systems with IA64
CPUs glued in, and even the later SN2 that were released as Altix
shared the same xtalk + bridge infrastructure, just with some hardware
updates. It just turned out SGI at some point decided to hide all that
in firmware. Linux 2.4 was still accessing this natively, but the code
was a mess. I tried to consolidate it with the mips version at that
point, but SGI decided that hiding it under firmware calls was easier
as they could just move the messy code there.
So, not it isn't really MIPS only in theory, although in practice it
very much is..
prev parent reply other threads:[~2019-05-08 6:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 15:47 [PATCH v3 00/3] MIPS: SGI-IP27 rework part2 Thomas Bogendoerfer
2019-03-19 15:47 ` [PATCH v3 1/3] MIPS: SGI-IP27: move IP27 specific code out of pci-ip27.c into new file Thomas Bogendoerfer
2019-03-19 15:47 ` [PATCH v3 2/3] MIPS: SGI-IP27: use generic PCI driver Thomas Bogendoerfer
2019-03-19 15:47 ` [PATCH v3 3/3] MIPS: SGI-IP27: abstract chipset irq from bridge Thomas Bogendoerfer
2019-03-19 15:47 ` [PATCH v3 00/3] MIPS: SGI-IP27 rework part2 Thomas Bogendoerfer
2019-04-18 20:57 ` Bjorn Helgaas
2019-05-06 10:37 ` Thomas Bogendoerfer
2019-05-07 9:42 ` Lorenzo Pieralisi
2019-05-07 15:31 ` Lorenzo Pieralisi
2019-05-07 15:48 ` Thomas Bogendoerfer
2019-05-07 16:30 ` Lorenzo Pieralisi
2019-05-08 6:24 ` Christoph Hellwig [this message]
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=20190508062420.GD19227@infradead.org \
--to=hch@infradead.org \
--cc=helgaas@kernel.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=tbogendoerfer@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).