From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Joshua Kinard <kumba@gentoo.org>
Cc: Paul Burton <paul.burton@mips.com>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Paul Burton <pburton@wavecomp.com>
Subject: Re: [PATCH 4/4] MIPS: Remove unused R8000 CPU support
Date: Sat, 14 Sep 2019 18:01:02 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.1909141759380.7834@eddie.linux-mips.org> (raw)
In-Reply-To: <56180022-f5dc-d35d-8411-87f96412883d@gentoo.org>
On Sat, 27 Jul 2019, Joshua Kinard wrote:
> > Our R8000 CPU support can only be included if a system selects
> > CONFIG_SYS_HAS_CPU_R8000. No system does, making all R8000-related CPU
> > support dead code. Remove it.
> >
> > Signed-off-by: Paul Burton <paul.burton@mips.com>
>
> [snip]
>
> I actually have one of these CPUs, and the SGI IP26 system to go with it.
> Fascinating CPU design. More like a multi-chip set rather than just a
> single CPU die. That said, no tears are shed over this code getting
> excised, as it's half-complete, because only the R8K TLB code was written.
> The cache code (c-r8k.c?) was never completed. I don't even know if the R8K
> TLB code was ever tested on real hardware. A scanned copy of the CPU manual
> is on the linux-mips FTP server somewhere, and I think I have a copy
> somewhere as well, if anyone ever gets interested again.
With all the old-timers I believe gone from the MIPS world I doubt this
is ever going to happen.
Maciej
next prev parent reply other threads:[~2019-09-14 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 21:59 [PATCH 1/4] MIPS: Remove unused R4300 CPU support Paul Burton
2019-07-22 21:59 ` [PATCH 2/4] MIPS: Remove unused R5432 " Paul Burton
2019-07-22 22:00 ` [PATCH 3/4] MIPS: Remove unused R5432_CP0_INTERRUPT_WAR Paul Burton
2019-07-22 22:00 ` [PATCH 4/4] MIPS: Remove unused R8000 CPU support Paul Burton
2019-07-27 8:36 ` Joshua Kinard
2019-09-14 17:01 ` Maciej W. Rozycki [this message]
2019-07-24 20:22 ` [PATCH 1/4] MIPS: Remove unused R4300 " 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=alpine.LFD.2.21.1909141759380.7834@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=pburton@wavecomp.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;
as well as URLs for NNTP newsgroup(s).