From: Pavel Machek <pavel@ucw.cz>
To: Nishanth Menon <nm@ti.com>
Cc: "Tony Lindgren" <tony@atomide.com>,
linux-omap@vger.kernel.org, "Kevin Hilman" <khilman@kernel.org>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Sebastian Reichel" <sre@kernel.org>,
"Pali Rohár" <pali.rohar@gmail.com>
Subject: Re: [PATCH] ARM: dts: Revert disabling of smc91x for n900
Date: Wed, 7 Jan 2015 21:00:12 +0100 [thread overview]
Message-ID: <20150107200012.GA6548@amd> (raw)
In-Reply-To: <54AD5447.2070601@ti.com>
Hi!
> >> Sure, updated patch below. Can somebody please test boot it on
> >> a production n900 too to make sure it no longer causes issues?
> >
> > Actually... how do you manage your n900 to boot? Does it also boot
> > from 0xffff?
> >
> > I believe I'm hitting dtb size limit (again), and 3.19-rc3 does not boot
> > unless I somehow make dtb smaller... like the patch below.
> >
> > ---
> >
> > make dtb smaller so that it boots.
>
> I am using chained boot (NOLO->u-boot->kernel (zImage +dtb
> concatenated) on a real n900
>
> I have the same issue as well. using omap2plus_defconfig.
> I was able to bisect next tags as follows: next-20141128 worked,
> next-20141201 stopped booting and the change was new dts addition,
> removing the dts addition helped next-20141201 boot as well.
>
> Current state:
>
> https://github.com/nmenon/kernel-test-logs/blob/next-20150107/omap2plus_defconfig/n900.txt#L447
>
> https://github.com/nmenon/kernel-test-logs/blob/v3.19-rc3/omap2plus_defconfig/n900.txt#L448
>
>
> I had complained originally here:
> http://marc.info/?t=141946203100001&r=1&w=2 Apologies on not following
> up on the thread, got distracted.
Actually, I noticed this some time ago, and there's some additional
discussion at
Subject: Re: dtb size limit? was Re: Tiny dts change breaks boot on n900
Message-ID: <20141110150915.GH31454@atomide.com>
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-01-07 20:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 23:02 [PATCH] ARM: dts: Revert disabling of smc91x for n900 Tony Lindgren
2015-01-05 23:09 ` Pali Rohár
2015-01-05 23:10 ` Tony Lindgren
2015-01-06 15:03 ` Sebastian Reichel
2015-01-06 15:23 ` Pali Rohár
2015-01-06 8:00 ` Pavel Machek
2015-01-06 16:59 ` Tony Lindgren
2015-01-06 19:44 ` Aaro Koskinen
2015-01-06 19:54 ` Tony Lindgren
2015-01-06 20:17 ` Tony Lindgren
2015-01-06 20:34 ` Pali Rohár
2015-01-06 21:24 ` Tony Lindgren
2015-01-06 20:42 ` Pavel Machek
2015-01-06 21:56 ` Aaro Koskinen
2015-01-06 22:04 ` Tony Lindgren
2015-01-06 19:59 ` Pali Rohár
2015-01-07 9:57 ` Pavel Machek
2015-01-07 15:44 ` Nishanth Menon
2015-01-07 16:40 ` Tony Lindgren
2015-01-07 20:09 ` Pavel Machek
2015-01-07 21:25 ` Pavel Machek
2015-01-08 9:01 ` Pali Rohár
2015-01-08 18:54 ` Tony Lindgren
2015-01-07 20:00 ` Pavel Machek [this message]
2015-01-06 17:38 ` Kevin Hilman
2015-02-18 15:19 ` Pali Rohár
2015-02-18 16:33 ` Tony Lindgren
2015-02-18 19:04 ` Pali Rohár
2015-02-18 22:42 ` Tony Lindgren
2015-02-18 22:52 ` Pali Rohár
2015-02-19 4:50 ` Tony Lindgren
2015-02-19 10:59 ` Pali Rohár
2015-02-19 16:47 ` Pali Rohár
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=20150107200012.GA6548@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=khilman@kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pali.rohar@gmail.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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