Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932113Ab3IKUw5 (ORCPT ); Wed, 11 Sep 2013 16:52:57 -0400 Received: from mail-we0-f181.google.com ([74.125.82.181]:40911 "EHLO mail-we0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755628Ab3IKUw4 (ORCPT ); Wed, 11 Sep 2013 16:52:56 -0400 MIME-Version: 1.0 X-Originating-IP: [2620:0:1000:1b02:6e3b:e5ff:fe16:f1aa] In-Reply-To: References: Date: Wed, 11 Sep 2013 13:52:55 -0700 Message-ID: Subject: Re: [GIT PULL] Device tree updates for v3.12 From: Olof Johansson To: Tim Bird Cc: Tony Luck , Linus Torvalds , Grant Likely , Rob Herring , Linux Kernel Mailing List , "devicetree@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 992 Lines: 24 On Wed, Sep 11, 2013 at 1:21 PM, Tim Bird 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/