From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from de01egw01.freescale.net (de01egw01.freescale.net [192.88.165.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "de01egw01.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 10004DE057 for ; Sat, 23 Feb 2008 03:28:48 +1100 (EST) Date: Fri, 22 Feb 2008 10:28:21 -0600 From: Scott Wood To: Jon Loeliger Subject: Re: [PATCH] Add support for binary includes. Message-ID: <20080222162821.GC19571@ld0162-tx32.am.freescale.net> References: <20080220191941.GA2062@ld0162-tx32.am.freescale.net> <20080222160820.GA19571@ld0162-tx32.am.freescale.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Feb 22, 2008 at 10:24:56AM -0600, Jon Loeliger wrote: > So, like, the other day Scott Wood mumbled: > > > > > > Can I ask; what is the intended usage of such a thing? How large > > > would a typical binary blob be? > > > > I use it for embedding guest device trees in a hypervisor's device tree. > > Why wouldn't we instead, say, extend the source sytax > to allow a sub-tree or an embedded tree, rather than > obscuring an opaque form of that guest device tree? That was what I tried initially, but the implementation was much more complicated, and path references are problematic. -Scott