From: James Hogan <james.hogan@mips.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Huacai CHen <chenhc@lemote.com>, <linux-mips@linux-mips.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS: Loongson64: Drop 32-bit support for Loongson 2E/2F devices
Date: Tue, 2 Jan 2018 13:39:45 +0000 [thread overview]
Message-ID: <20180102133944.GO5027@jhogan-linux.mipstec.com> (raw)
In-Reply-To: <1514899786.1694.6.camel@flygoat.com>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Tue, Jan 02, 2018 at 09:29:46PM +0800, Jiaxun Yang wrote:
> On 2018-01-02 Tue 08:48 +0000，James Hogan Wrote：
> > On Tue, Dec 26, 2017 at 12:21:38PM +0800, Jiaxun Yang wrote:
> > > Make loongson64 a pure 64-bit mach.
> >
> > Please expand to provide some rationale behind the change. Was 32-bit
> > support broken at runtime, or broken at build time, or are we simply
> > no
>
> The 32-bit support was broken at runtime, it doesn't boot anymore,
> witch is hard to debug because even early printk isn't working, also
> there are some build warnings. Some newer bootloader may not support
> 32-bit ELF. So we decide to drop 32-bit support.
Okay, please put that in the commit message so that somebody digging
through the history later (perhaps summarising what is new in the next
release) can understand the *why* as well as the what.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@mips.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Huacai CHen <chenhc@lemote.com>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Loongson64: Drop 32-bit support for Loongson 2E/2F devices
Date: Tue, 2 Jan 2018 13:39:45 +0000 [thread overview]
Message-ID: <20180102133944.GO5027@jhogan-linux.mipstec.com> (raw)
Message-ID: <20180102133945.JQb5bfu8wsBqUZUTUN4atgXEfM4t3dAPh-Er2Nf9NcY@z> (raw)
In-Reply-To: <1514899786.1694.6.camel@flygoat.com>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Tue, Jan 02, 2018 at 09:29:46PM +0800, Jiaxun Yang wrote:
> On 2018-01-02 Tue 08:48 +0000，James Hogan Wrote：
> > On Tue, Dec 26, 2017 at 12:21:38PM +0800, Jiaxun Yang wrote:
> > > Make loongson64 a pure 64-bit mach.
> >
> > Please expand to provide some rationale behind the change. Was 32-bit
> > support broken at runtime, or broken at build time, or are we simply
> > no
>
> The 32-bit support was broken at runtime, it doesn't boot anymore,
> witch is hard to debug because even early printk isn't working, also
> there are some build warnings. Some newer bootloader may not support
> 32-bit ELF. So we decide to drop 32-bit support.
Okay, please put that in the commit message so that somebody digging
through the history later (perhaps summarising what is new in the next
release) can understand the *why* as well as the what.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-02 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 4:21 [PATCH] MIPS: Loongson64: Drop 32-bit support for Loongson 2E/2F devices Jiaxun Yang
2018-01-02 8:48 ` James Hogan
2018-01-02 8:48 ` James Hogan
2018-01-02 13:29 ` Jiaxun Yang
2018-01-02 13:39 ` James Hogan [this message]
2018-01-02 13:39 ` James Hogan
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=20180102133944.GO5027@jhogan-linux.mipstec.com \
--to=james.hogan@mips.com \
--cc=chenhc@lemote.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox