From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: dtb size limit? was Re: Tiny dts change breaks boot on n900
Date: Mon, 10 Nov 2014 07:09:16 -0800 [thread overview]
Message-ID: <20141110150915.GH31454@atomide.com> (raw)
In-Reply-To: <20141110125806.GA16650@amd>
* Pavel Machek <pavel@ucw.cz> [141110 04:59]:
> On Mon 2014-11-10 13:31:18, Pavel Machek wrote:
> > Hi!
> >
> > I'm confused:
> >
> > This fixes boot on n900. Strange thing is ... adp1653 driver is not
> > even compiled in -- it is module.
> >
> > It looks like tiny change in dts noone should care about breaks
> > boot... I don't even have adp1653 device parsing code written.
> >
> > Something similar happened before -- change in device tree order broke
> > boot.
> >
> > Any ideas? What is going on?
>
> If I replace the blog below with
>
> a = <1>;
> b = <2>;
> c = <3>;
> d = <4>;
>
> Resulting kernel boots. Replacing it with
>
> a-really-long-attribute-name-hopefully-this-breaks-stuff = <1>;
> b = <2>;
> c = <3>;
> d = <4>;
>
> Breaks the boot. I'm using dtb append option. Any ideas? Nonbooting
> dtb is 68910 bytes.
>
> pavel at amd:/data/l/linux-n900$ ls -al arch/arm/boot/dts/omap3-n900.dtb
> -rw-r--r-- 1 pavel pavel 68910 Nov 10 13:52 arch/arm/boot/dts/omap3-n900.dtb
>
> I removed some "smsc,lan91c94" settings, and it boots again. Weird.
Seems like we may still have some issues with the relocation if
it's size related. Or a regression maybe?
See for example commit 5ffb04f6690d ("ARM: zImage: make sure appended
DTB doesn't get overwritten by kernel .bss")
Regards,
Tony
> > diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
> > index f3118bf..557a19e 100644
> > --- a/arch/arm/boot/dts/omap3-n900.dts
> > +++ b/arch/arm/boot/dts/omap3-n900.dts
> > @@ -565,11 +565,6 @@
> > adp1653: adp1653 at 30 {
> > compatible = "ad,adp1653";
> > reg = <0x30>;
> > -
> > - max-flash-timeout-usec = <500000>;
> > - max-flash-intensity-mA = <0>;
> > - max-torch-intensity-mA = <0>;
> > - max-indicator-intensity-uA = <0>;
> > };
> > };
> >
> >
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-10 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 12:31 Tiny dts change breaks boot on n900 Pavel Machek
2014-11-10 12:58 ` dtb size limit? was " Pavel Machek
2014-11-10 15:09 ` Tony Lindgren [this message]
2014-11-10 15:25 ` Andreas Färber
2014-11-16 8:38 ` Pavel Machek
2014-11-16 9:38 ` Geert Uytterhoeven
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=20141110150915.GH31454@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).