From: "Rafał Miłecki" <zajec5@gmail.com>
To: Manuel Lauss <manuel.lauss@gmail.com>
Cc: "Paul Wassi" <p.wassi@gmx.at>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"Ralf Baechle" <ralf@linux-mips.org>,
"David Daney" <ddaney.cavm@gmail.com>,
"David Daney" <david.daney@cavium.com>,
"Michael Büsch" <m@bues.ch>, "Hauke Mehrtens" <hauke@hauke-m.de>,
"Larry Finger" <larry.finger@lwfinger.net>,
"Felix Fietkau" <nbd@nbd.name>, "John Crispin" <john@phrozen.org>
Subject: Re: BCM4704 stopped booting with 4.4 (due to vmlinux size?)
Date: Thu, 16 Jun 2016 14:24:37 +0200 [thread overview]
Message-ID: <CACna6rz0jm2BhCVwiwjXCTayjU5UacNh3Y=TuXp56OcfJ4huUg@mail.gmail.com> (raw)
In-Reply-To: <CAOLZvyFuP2TBFOkUZJPQ2HtaCb6pztMsxjiQVSDr8E5xxH3Ecw@mail.gmail.com>
On 16 June 2016 at 14:19, Manuel Lauss <manuel.lauss@gmail.com> wrote:
> On Thu, Jun 16, 2016 at 1:42 PM, <p.wassi@gmx.at> wrote:
>>> On the other hand Paul also experiences some problems with his Linksys
>>> WRT54GL (BCM5352E), the last stable kernel for him seems to be 3.18.
>>
>> I have to calrify that a bit:
>> if I use prebuilt images from OpenWrt 15.05.1, they work out of the box (as you say, it's 3.18)
>> If I take prebuilt images from (LEDE|OpenWrt) trunk (which was 4.1 then), they do not boot.
>> However, if I clone the repo (which was used to build said trunk) and build it myself,
>> the images work fine. (kernel 4.1) [1]
>
> Differences in toolchain perhaps? What versions of gcc, binutils do
> you and LEDE/OpenWrt use?
When building LEDE, it first compiles toolchain and compiler and then
it uses them to compile all the software. It doesn't use host-provided
toolchain/gcc. So it shouldn't matter on what machine you build your
image (buildbot or locally). Right now LEDE's master uses gcc 5.3.0
and musl 1.1.14.
--
Rafał
next prev parent reply other threads:[~2016-06-16 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 6:17 BCM4704 stopped booting with 4.4 (due to vmlinux size?) Rafał Miłecki
2016-06-16 6:17 ` Rafał Miłecki
2016-06-16 11:42 ` p.wassi
2016-06-16 12:19 ` Manuel Lauss
2016-06-16 12:24 ` Rafał Miłecki [this message]
2016-06-16 18:43 ` Aaro Koskinen
2016-06-20 8:39 ` p.wassi
2016-06-30 21:57 ` Hauke Mehrtens
2016-07-01 13:59 ` p.wassi
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='CACna6rz0jm2BhCVwiwjXCTayjU5UacNh3Y=TuXp56OcfJ4huUg@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.org \
--cc=larry.finger@lwfinger.net \
--cc=linux-mips@linux-mips.org \
--cc=m@bues.ch \
--cc=manuel.lauss@gmail.com \
--cc=nbd@nbd.name \
--cc=p.wassi@gmx.at \
--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.