From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M1NcT-0003Q9-Fu
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:35:49 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M1NcO-0003L4-SK
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:35:49 -0400
Received: from [199.232.76.173] (port=39492 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M1NcO-0003L0-JW
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:35:44 -0400
Received: from mx20.gnu.org ([199.232.41.8]:57087)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1M1NcO-0004VY-7D
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:35:44 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1M1NcN-0002Ub-8b
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:35:43 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [RFC] New device API
Date: Tue, 5 May 2009 17:35:40 +0100
References: <200905051231.09759.paul@codesourcery.com>
	<200905051717.25034.paul@codesourcery.com>
	<f43fc5580905050926n37eac7cdwe8d32b4f98bf1fad@mail.gmail.com>
In-Reply-To: <f43fc5580905050926n37eac7cdwe8d32b4f98bf1fad@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200905051735.40550.paul@codesourcery.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org

> >  > I don't think the ptr property can be used to construct OpenFirmware
> >  > properties, because the length of the data is not handled.
> >
> > This is intended to be used to link between devices. An OF implementation
> >  would probably use a phandle. I may rename to device/object to clarify.
>
> Still, it would be useful to have a way for the devices to be able to
> export strings and blobs to the device tree.

Right. ptr is the wrong way to represent those though :-)

Note that I don't intend for devices to modify the configuration data. qemu 
may want to manipulate it bit to support commandline driven machine 
modifications (like -net nic), but that bit doesn't exist yet.

Paul