[Xen-devel] why in the ustable developement tree are scsi and et

To:	xen-devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] why in the ustable developement tree are scsi and ethernet device driver build in
From:	Ralph Blach <chipper@xxxxxxxxxx>
Date:	Fri, 29 Jul 2005 15:07:09 -0400
Delivery-date:	Fri, 29 Jul 2005 19:05:40 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720)

Why in unstable development tree are are all the device drivers build into the kernel? I had a problem with two ethenets on the same IRQ notworking. This was fixed by making them modules, and they now the twoethernets work on the same irq

Should we be developing with all the drivers as modules, using aninitrd, so that we can keep the kernel size down?


Chip
--
Ralph "Chip" Blach
chipper@xxxxxxxxxx
IBM Linux Technology Center
Raleigh, North Carolina
919 543 1207

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] why in the ustable developement tree are scsi and ethernet d