Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH] MIPS: Limit MIPS_MT_SMP support by ISA reversion
Date: Sat, 8 Apr 2023 14:17:28 +0200	[thread overview]
Message-ID: <20230408121728.GA5953@alpha.franken.de> (raw)
In-Reply-To: <CD810353-41E9-46ED-AEFB-902B6A4FFD6F@flygoat.com>

On Sat, Apr 08, 2023 at 11:10:32AM +0100, Jiaxun Yang wrote:
> 
> 
> > 2023年4月8日 01:30,Guenter Roeck <linux@roeck-us.net> 写道:
> > 
> > On 4/7/23 15:35, Jiaxun Yang wrote:
> >> MIPS MT ASE is only available on ISA between Release 1 and Release 5.
> >> Add ISA level dependency to Kconfig to fix build.
> >> Reported-by: Guenter Roeck <linux@roeck-us.net>
> >> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> > 
> > With this patch in place, I still get the second build failure.
> 
> + Thomas
> 
> Seems like PTE bits are overflowing again.

I'm going to revert de34007751aaba992373f2d659001a846aeb8811, which just
solves all new build problems in one go. Then we can try to come up with
a usable solution.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2023-04-08 12:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 22:35 [PATCH] MIPS: Limit MIPS_MT_SMP support by ISA reversion Jiaxun Yang
2023-04-08  0:30 ` Guenter Roeck
2023-04-08 10:10   ` Jiaxun Yang
2023-04-08 12:17     ` Thomas Bogendoerfer [this message]
2023-04-08 12:59       ` Jiaxun Yang
2023-05-16 15:05 ` Maciej W. Rozycki
2023-05-16 19:56   ` Jiaxun Yang
2023-05-16 20:47     ` Maciej W. Rozycki
2023-05-16 22:54       ` Jiaxun Yang

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=20230408121728.GA5953@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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