From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jdl.com (jdl.com [208.123.74.7]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 8DE8EDE13B for ; Sat, 23 Feb 2008 04:01:34 +1100 (EST) To: Scott Wood Subject: Re: [PATCH] Add support for binary includes. In-Reply-To: Your message of "Fri, 22 Feb 2008 10:08:20 CST." <20080222160820.GA19571@ld0162-tx32.am.freescale.net> References: <20080220191941.GA2062@ld0162-tx32.am.freescale.net> <20080222160820.GA19571@ld0162-tx32.am.freescale.net> Date: Fri, 22 Feb 2008 10:24:56 -0600 From: Jon Loeliger Message-Id: Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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? Thanks, jdl