From: Ben Hutchings <ben@decadent.org.uk>
To: Guenter Roeck <linux@roeck-us.net>,
stable <stable@vger.kernel.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
Li Zefan <lizefan@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Building older mips kernels with different versions of binutils; possible patch for 3.2 and 3.4
Date: Sun, 08 Oct 2017 20:54:20 +0100 [thread overview]
Message-ID: <1507492460.2677.85.camel@decadent.org.uk> (raw)
In-Reply-To: <05e37183-f6a6-d141-5dad-9d4b161953b1@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Sun, 2017-10-08 at 12:01 -0700, Guenter Roeck wrote:
> On 10/08/2017 11:49 AM, Guenter Roeck wrote:
> > On 10/08/2017 11:12 AM, Ben Hutchings wrote:
> > > On Sun, 2016-05-15 at 19:56 -0700, Guenter Roeck wrote:
> > > [...]
> > > > For 3.4 and 3.2 kernels to build with binutils v2.24, it would be necessary to
> > > > apply patch c02263063362 ("MIPS: Refactor 'clear_page' and 'copy_page' functions").
> > > > It applies cleanly to 3.4, but has a Makefile conflict in 3.2. It might
> > > > make sense to apply this patch to both releases. Would this be possible ?
> > > > This way, we would have at least one toolchain which can build all 3.2+ kernels.
> > >
> > > I'm finally queueing this up for 3.2.
> > >
> > > Ben.
> > >
> >
> > mipsel images in 3.2.y-queue are now crashing for me. Should I have a look ?
> >
>
> Turns out the culprit is qemu. I had switched from qemu 2.9 to qemu 2.10.
> Something has changed in qemu that causes a qemu boot failure with 3.2 mipsel
> (but not in more recent kernels). I'll switch back to qemu 2.9 for the affected
> builds.
Thanks. I did notice these failures but didn't think they were related
to the few MIPS patches in the 3.2 queue.
Ben.
--
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-10-08 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 2:56 Building older mips kernels with different versions of binutils; possible patch for 3.2 and 3.4 Guenter Roeck
2016-05-20 13:21 ` Maciej W. Rozycki
2016-05-20 17:31 ` Guenter Roeck
2016-05-20 18:29 ` Maciej W. Rozycki
2016-05-20 23:18 ` James Hogan
2017-10-08 18:12 ` Ben Hutchings
2017-10-08 18:49 ` Guenter Roeck
2017-10-08 19:01 ` Guenter Roeck
2017-10-08 19:54 ` Ben Hutchings [this message]
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=1507492460.2677.85.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@roeck-us.net \
--cc=lizefan@huawei.com \
--cc=stable@vger.kernel.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.