WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] adding device driver kernel module for xen/linux

To: "Fajar A. Nugraha" <fajar@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] adding device driver kernel module for xen/linux
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 17 Jan 2006 12:10:14 -0000
Delivery-date: Tue, 17 Jan 2006 12:17:53 +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
Thread-index: AcYbKqw/6DK0IIdvQa2Eny/5bQ5wQQANA/SA
Thread-topic: [Xen-devel] adding device driver kernel module for xen/linux
> I wanted to add a kernel module (bcm5700, device driver for 
> Broadcom network adapter) to linux 2.6, xen-3.0.0. Is it 
> possible to use the kernel module (source) as-is, without 
> modifications, or do I need to edit the module source code to 
> be Xen-specific?

The code should not need to be modified.
 
> I noticed that the files tg3.c and tg3.h on linux-2.6.12-xen 
> is the same as the one on pristine-linux-2.6.12, so 
> presumably, no change is needed. 
> However, using bcm5700 module on linux-2.6.12-xen kernel 
> doesn't work, while using bcm5700 on native linux (on the 
> same machine) works.

The tg3 driver certainly works for me. When you say native, do you mean
2.6.12 native? Perhaps you have a very new version of the chip that
needs a more recent driver?

Perhaps more likely, you may have an interrupt routeing issue. Does the
NIC appear to be using the same interrupt number in both the native and
xen cases?

Ian 

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

<Prev in Thread] Current Thread [Next in Thread>