From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M1NKp-0008PY-Cn
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:17:35 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M1NKj-0008OI-Io
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:17:34 -0400
Received: from [199.232.76.173] (port=56454 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M1NKj-0008OD-Fb
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:17:29 -0400
Received: from mx20.gnu.org ([199.232.41.8]:56003)
	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 1M1NKj-0008Lg-4K
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:17:29 -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 1M1NKi-0001Vk-8A
	for qemu-devel@nongnu.org; Tue, 05 May 2009 12:17:28 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [RFC] New device API
Date: Tue, 5 May 2009 17:17:24 +0100
References: <200905051231.09759.paul@codesourcery.com>
	<f43fc5580905050856g557fd461i3deaf04e7c6fb744@mail.gmail.com>
In-Reply-To: <f43fc5580905050856g557fd461i3deaf04e7c6fb744@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200905051717.25034.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

> 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.

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