From: Mike Frysinger <vapier@gentoo.org>
To: Huacai Chen <chenhuacai@gmail.com>
Cc: Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: custom kernel on lemote-3a-itx (Loongson-3A) crashes in userspace
Date: Fri, 27 Feb 2015 15:31:59 -0500 [thread overview]
Message-ID: <20150227203159.GS29461@vapier> (raw)
In-Reply-To: <CAAhV-H7vm61G1TP53GpskhLxC6LFEUkhiVzTFDRTiXSt9-zuvg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
On 27 Feb 2015 21:37, Huacai Chen wrote:
> We have also built good kernels with native GCC-4.6.4/4.7.2/4.8.3 (o32
> binaries).
do you have the source for those versions available ? that way i can see if
there's any patches we should pick up in Gentoo for mips.
> So maybe this is an N32-related problems.
that would not surprise me :). we like to push the envelope in Gentoo.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-27 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 19:46 custom kernel on lemote-3a-itx (Loongson-3A) crashes in userspace Mike Frysinger
2015-02-26 7:47 ` Huacai Chen
2015-02-26 8:14 ` Mike Frysinger
2015-02-27 13:37 ` Huacai Chen
2015-02-27 20:31 ` Mike Frysinger [this message]
2015-02-28 1:29 ` Huacai Chen
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=20150227203159.GS29461@vapier \
--to=vapier@gentoo.org \
--cc=chenhuacai@gmail.com \
--cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox