From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nick Logan <nick_logan@symantec.com>
Subject: skeleton FE/BE driver
Date: Mon, 09 Jan 2006 15:41:21 +0000
Message-ID: <43C28421.3050500@symantec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Is there an updated skeleton driver including the latest set of xenbus 
changes? I'm looking into developing a new driver and wondered what the 
best place to start is. I've tried Rusty's skeleton driver but have 
realised that it doesn't include the latest state changes. As I want to 
figure out what xenstore writes are required to create a new device, I 
thought that the skeleton driver would be the best place to start rather 
than use a driver that relied on xend to write to xenstore. If there 
isn't a working skeleton driver, I'll have to start with the vbd driver.

Nick Logan