From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M1NTH-0003ng-Me
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:26:19 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M1NTG-0003mj-O6
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:26:18 -0400
Received: from [199.232.76.173] (port=38221 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M1NTG-0003mc-Hd
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:26:18 -0400
Received: from fg-out-1718.google.com ([72.14.220.153]:46283)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1M1NTG-0001x5-2Y
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:26:18 -0400
Received: by fg-out-1718.google.com with SMTP id e21so1540315fga.8
	for <qemu-devel@nongnu.org>; Tue, 05 May 2009 09:26:17 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <200905051717.25034.paul@codesourcery.com>
References: <200905051231.09759.paul@codesourcery.com>
	<f43fc5580905050856g557fd461i3deaf04e7c6fb744@mail.gmail.com>
	<200905051717.25034.paul@codesourcery.com>
Date: Tue, 5 May 2009 19:26:17 +0300
Message-ID: <f43fc5580905050926n37eac7cdwe8d32b4f98bf1fad@mail.gmail.com>
Subject: Re: [Qemu-devel] [RFC] New device API
From: Blue Swirl <blauwirbel@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org

On 5/5/09, Paul Brook <paul@codesourcery.com> wrote:
> > About "int" property, I'd use a wider type to support 64 bit properties.
>
>
> Ok.
>
>
>  > 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.

>  The ESP DMA bits where we pass function pointers are a temporary hack, and
>  should go away.
>
>
>  > What happens if you try to register two devices of the same type, can
>  > you identify them somehow? In OF, this is handed with by adding @ and
>  > address.
>
>
> I guess I'll either use an informative suffix (like OF/FDT), or have separate
>  type and instance name.
>
>
>  Paul
>