From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH] DEC/SNI: O32 wrapper stack switching fixes
Date: Tue, 8 Apr 2014 00:19:20 +0200 [thread overview]
Message-ID: <20140407221920.GA9418@alpha.franken.de> (raw)
In-Reply-To: <alpine.LFD.2.11.1403312351450.27402@eddie.linux-mips.org>
On Tue, Apr 01, 2014 at 12:14:41AM +0100, Maciej W. Rozycki wrote:
> Please verify this works for your system.
works on a RM200 system (after removing stupid EARLY_CRAP_8250 select).
Only strange thing I see is
WARNING: CPU: 0 PID: 0 at /home/tsbogend/mips/work/linux/arch/mips/mm/uasm.c:97 build_insn+0x4c4/0x570()
Micro-assembler field overflow
Happens twice one for build_clear_cache() and build_copy_cache().
CPU is is R4600PC 2.0.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2014-04-07 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 23:14 [PATCH] DEC/SNI: O32 wrapper stack switching fixes Maciej W. Rozycki
2014-04-07 22:19 ` Thomas Bogendoerfer [this message]
2014-04-07 23:05 ` Maciej W. Rozycki
2014-04-08 6:53 ` Thomas Bogendoerfer
2014-04-08 11:25 ` Maciej W. Rozycki
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=20140407221920.GA9418@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
/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.