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

Re: [Xen-users] Xen and Zaptel PCI cards on DomU

To: Jason <xen@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Xen and Zaptel PCI cards on DomU
From: "Damon Brown" <damon@xxxxxxxxxxxxxx>
Date: Tue, 16 May 2006 19:23:41 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 May 2006 19:24:20 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=AwhjrXP3Bj1v7HV9ZbaHFKqUu+M7zeMjF7aOP/FJ3fWiiSUoWPBTp7T2z7rjEFlEPGnN8opzGPqeHhW6NjnsQnSTibj/kl/N9Rkvzq9XAlHICqMVuxsKhLkbNZ4RNAbr4B65qgJ+zehslddVa+kuTayeJFc05PYBNGNGFB1DWYc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.63.0605162059170.9305@localhost>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <77012e4c0605161106y28d8f28fwca40cf6323fe5cd3@xxxxxxxxxxxxxx> <bc0c36d30605161607l2587ad96h5edfd63804e48375@xxxxxxxxxxxxxx> <Pine.LNX.4.63.0605162059170.9305@localhost>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thanks Jason
Were you able to get it to compile ?  I just get this C error on the asterisk CVS head and stable:

make[1]: Entering directory `/usr/src/xen-3.0.2-2/linux-2.6.16-xen'
  CC [M]  /usr/src/asterisk/zaptel/zaptel.o
/usr/src/asterisk/zaptel/zaptel.c: In function `zt_register':
/usr/src/asterisk/zaptel/zaptel.c:4448: warning: passing arg 2 of `class_device_create' makes pointer from integer without a cast
/usr/src/asterisk/zaptel/zaptel.c:4448: warning: passing arg 3 of `class_device_create' makes integer from pointer without a cast
/usr/src/asterisk/zaptel/zaptel.c:4448: warning: passing arg 4 of `class_device_create' from incompatible pointer type
/usr/src/asterisk/zaptel/zaptel.c:4448: error: too few arguments to function `class_device_create'
/usr/src/asterisk/zaptel/zaptel.c: In function `zt_init':
/usr/src/asterisk/zaptel/zaptel.c:6507: warning: passing arg 2 of `class_device_create' makes pointer from integer without a cast
/usr/src/asterisk/zaptel/zaptel.c:6507: warning: passing arg 3 of `class_device_create' makes integer from pointer without a cast
/usr/src/asterisk/zaptel/zaptel.c:6507: warning: passing arg 4 of `class_device_create' from incompatible pointer type
/usr/src/asterisk/zaptel/zaptel.c:6507: error: too few arguments to function `class_device_create'
/usr/src/asterisk/zaptel/zaptel.c:6508: warning: passing arg 2 of `class_device_create' makes pointer from integer without a cast
/usr/src/asterisk/zaptel/zaptel.c:6508: warning: passing arg 3 of `class_device_create' makes integer from pointer without a cast
/usr/src/asterisk/zaptel/zaptel.c:6508: warning: passing arg 4 of `class_device_create' from incompatible pointer type
/usr/src/asterisk/zaptel/zaptel.c:6508: error: too few arguments to function `class_device_create'
/usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing arg 2 of `class_device_create' makes pointer from integer without a cast
/usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing arg 3 of `class_device_create' makes integer from pointer without a cast
/usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing arg 4 of `class_device_create' from incompatible pointer type
/usr/src/asterisk/zaptel/zaptel.c:6509: error: too few arguments to function `class_device_create'
/usr/src/asterisk/zaptel/zaptel.c:6510: warning: passing arg 2 of `class_device_create' makes pointer from integer without a cast
/usr/src/asterisk/zaptel/zaptel.c:6510: warning: passing arg 3 of `class_device_create' makes integer from pointer without a cast
/usr/src/asterisk/zaptel/zaptel.c:6510: warning: passing arg 4 of `class_device_create' from incompatible pointer type
/usr/src/asterisk/zaptel/zaptel.c:6510: error: too few arguments to function `class_device_create'
/usr/src/asterisk/zaptel/zaptel.c: At top level:
/usr/src/asterisk/zaptel/zaptel.c:176: warning: `fcstab' defined but not used
make[2]: *** [/usr/src/asterisk/zaptel/zaptel.o] Error 1
make[1]: *** [_module_/usr/src/asterisk/zaptel] Error 2
make[1]: Leaving directory `/usr/src/xen-3.0.2-2/linux-2.6.16-xen'
make: *** [linux26] Error 2


Thanks

On 5/16/06, Jason < xen@xxxxxxxxxxxxxxxxx> wrote:
I have been able to get the cheapy fxo cards detected compiled and running, but I have some nasty
issues using it. It seems that those cards are really IRQ happy and when Im using the card, the
rest of the box becomes almost unresponsive.

To compile the code, just build it in your domain0 and set KVERS=2.6.16-xenU (or whatever your
kernel version is). Then just copy the modules into your domU.

--
Jason
The place where you made your stand never mattered,
only that you were there... and still on your feet

On Tue, 16 May 2006, David Muench wrote:

> On 5/16/06, Damon Brown <brown078@xxxxxxxxx> wrote:
>> Hi all,
>>
>> I have been struggling with the feasibility of adding a zaptel 2 port fxo
>> PCI card to a vm for a few weeks.  Initially, I installed xen 3.0.2-2
>> sources and compiled the kernel to include the 1000 HZ timing, which I know
>> is a requirement for ztdummy and I hope to not use.  What I'm running into
>> is the basic understanding of how to get zaptel to compile on a DomU.
>
> I have been using Asterisk on Xen for quite some time now, but without
> any zaptel hardware - just the zaptel and ztdummy drivers. Last night
> I tried to add one of the cheap WCFXO cards, and so far I can't get
> the wcfxo driver to detect the card. It is presented to the domU
> correctly. I am still using Xen 2.0.7, I haven't had time to try 3.0
> yet (and don't have the time to risk destabilizing my setup). Here's
> the messages I get:
>
> May 16 09:24:37 uranus kernel: PCI: Obtained IRQ 18 for device 0000:02:04.0
> May 16 09:24:37 uranus kernel: FXO PCI Master abort
> May 16 09:24:37 uranus last message repeated 36 times
> May 16 09:24:37 uranus kernel: Failed to initailize DAA, giving up...
> May 16 09:24:37 uranus kernel: FXO PCI Master abort
> May 16 09:24:37 uranus kernel: FXO PCI Master abort
> May 16 09:24:37 uranus kernel: wcfxo: probe of 0000:02:04.0 failed with error
> -5
> May 16 09:24:37 uranus kernel: Registered tone zone 0 (United States /
> North America)
>
> root@uranus :~# lspci -v
> 0000:02:04.0 Communication controller: Motorola: Unknown device 5608
>       Subsystem: Motorola: Unknown device 0000
>       Flags: bus master, medium devsel, latency 32, IRQ 18
>       I/O ports at c800 [size=256]
>       Memory at ff6bf000 (32-bit, non-prefetchable) [size=4K]
>       Capabilities: [40] Power Management version 2
>
> If anyone has any ideas, I'd be grateful.
>
> Dave
>
>

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



--
Damon Brown
Web Application Developer and Consultant
Phone: (916)601-8190
e-mail: damon@xxxxxxxxxxxxxx
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users