linux-kernel - Re: [GIT PULL] Device tree updates for v3.12

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOesGMhUAqKWsJEnK1-5TwRpE62WqVug9kYEziaJ3dtkEiGs4g@mail.gmail.com>
Date:	Wed, 11 Sep 2013 13:52:55 -0700
From:	Olof Johansson <olof@...om.net>
To:	Tim Bird <tbird20d@...il.com>
Cc:	Tony Luck <tony.luck@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Rob Herring <rob.herring@...xeda.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [GIT PULL] Device tree updates for v3.12

On Wed, Sep 11, 2013 at 1:21 PM, Tim Bird <tbird20d@...il.com> wrote:
> Thanks.  This gives me an order-of-magnitude measurement for this sort of thing.
> I'll measure it directly myself on our hardware as soon as I can.
>
> I've heard an ugly rumor that the device tree from our silicon vendor
> may grow to be
> as big as 130K in the near future. I'm still following up to see if
> there's any truth
> to this (so don't quote me on it), but if it does get that big it
> might be an issue.  As
> stated previously, the vast majority of our device tree files consists
> of values that
> are not device-specific.

The biggest ones in mainline today compile to a ~30K binary. Not sure
a vendor expects to add in there to gain another 100KB.


-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/