similar to: Xen RTC emulation

So I successfully installed the GPLPV drivers in a Windows installation I have running under Xen. Turns out SP2 is needed - I wish this was slightly better documented somewhere, as the machine ended up bluescreening and I had to use /NOGPLPV to get it to boot again so I could upgrade it to SP2. My question is this: I ended up using ''disable'' in device manager for the rtl8139 and

Hi, I have a list(A1) of dataframe and a vector containing a 22 list names. list(A1) abc l m n p q r dce e g h l k m kpo a d c also i have a vector of list names. abc,dce similarly i have 22 elements. I wanna delete or want a list without the list elements whoes name match up the vector. my result should be kpo a d c. i tried lapply it is in working in the way i want. Kindly help me

Hi, I'm having trouble using virtual register in the X86 backend. I implemented a new intrinsic and I use a custom inserter. The goal of the intrinsic is to set the content of the stack to zero at the end of each function. Here is my code: MachineBasicBlock * X86TargetLowering::EmitBURNSTACKWithCustomInserter( MachineInstr *MI, MachineBasicBlock

Hi, Thx for your help... Here is the IR code: ; ModuleID = 'foo_bar.c' target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128" target triple = "x86_64-unknown-linux-gnu" @.str = private unnamed_addr constant [6 x i8] c"MAIN\0A\00", align 1 ; Function Attrs: nounwind uwtable define i32 @main(i32 %argc, i8** %argv) #0 { entry: %retval = alloca i32,

Finally I got around to breaking up the similarly named monolithic patch that caused a regression shortly before the 4.2 release and got therefore reverted. This series consists of the broken up pieces that - according to my testing - don''t expose the reported lockup; the 7th will need debugging to understand what''s wrong there. 1: use RTC_* names instead of literal numbers 2:

There''s an issue on x86_64 whereby booting an unpriv guest using a kernel that has the RTC driver compiled in hangs when the rc scripts run the command hwclock. The patch attached resolves the issue. The patch adds a simple rtc emulation and also on i386, hwclock can get correct date when xenU enabled pirq binding, without this patch, hwclock read will timeout because of lack of update

I am trying to learn some more about the way windows does TPR writes, and tried xentrace for the first time. I did ''xentrace --time-interval=5 xentrace.out'' to capture some data, and then ran it through ''xentrace_format'' using the supplied example defs file. I can see some PF_XEN entries with virt=0xFFFE0080 (address of TPR), but I want to know the value being

Hello, Maybe I'm missing something here. What is the proper way to use RTC with ztdummy now? I'm using -HEAD from a day or two ago on Linux 2.6.11.11. In zaptel/Makefile, I changed CFLAGS to: CFLAGS+=-I. -O4 -g -Wall -DBUILDING_TONEZONE -DUSE_RTC #-DTONEZONE_DRIVER and I get.. make -C /lib/modules/2.6.11.11/build SUBDIRS=/usr/src/zaptel modules make[1]: Entering directory

Hi all, I have installed centos 5.1 x86_64. 2.6.18-53.1.14.el5 Everything seems to be working fine except that the rtc module is not working. cat /proc/interrupts shows: CPU0 CPU1 0: 129 0 XT-PIC-XT timer 1: 330797 0 XT-PIC-XT i8042 2: 0 0 XT-PIC-XT cascade 3: 4 0

Hi guys, I was wondering whether there's anyone who could share his/her experiences with using Microsoft RTC Library. In particular I am wondering what Ethernet capacity should I have in scenario of 30 people using Microsoft RTC Library for SIP communication (PBX is obviously Asterisk :-) ) concurrently (alaw codec being used)? What problems can be expected in such scenario? Would a good 1

Greetings, I'm trying to create a server-based SIP chatroom (using MeetMe w/ ztdummy), where the clients will be mainly connecting with MS RTC Clients. I got the authentication working, but am having a problem where I can only hear audio when I am also making noise into the microphone. This appears to be the VAD/MOH problem mentioned on this list before.

This patch rewrites the rtc/timeoffset entry so the VM''s record can be retrieved with the Java xmlrpc library. If the entry is ''None'' it upsets the xmlrpc parser. This fixes it, though maybe there''s a better place in xend to place similar code. Signed-off-by: Stefan Berger <stefanb@us.ibm.com> _______________________________________________ Xen-devel

Hello there: I think I have a silly kernel configuration problem. I'm running: * vanilla 2.6.27.10 kernel built from source * dahdi-2.1.0.4 built from source So far so good, dahdi module loads just fine: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.1.0.4 when I try to: hal04 dahdi # modprobe dahdi_dummy FATAL: Error inserting dahdi_dummy

Hi all, One of our domU VMs (CentOS 5.6 x86_64) runs a cobol application, which in turn called ''clock'' to get timestamps. Changing this is non-trivial. When I try to call ''clock --debug'' I get: [root@vm0010 ~]# clock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=19: No such device. No usable clock interface found.

The UIP(update in progress) is set when RTC is in updating. And the update cycle begins 244us later after UIP is set. Signed-off-by: Yang Zhang <yang.z.zhang@Intel.com> diff -r 47cb862a07c2 -r edc35b026509 xen/arch/x86/hvm/rtc.c --- a/xen/arch/x86/hvm/rtc.c Mon Mar 05 14:39:07 2012 +0800 +++ b/xen/arch/x86/hvm/rtc.c Mon Mar 05 14:39:41 2012 +0800 @@ -28,6 +28,8 @@ #include

I'm using the the Microsoft Real-Time Communications Client API SDK using Visual Studio 6 and . NET 2003 SE to make SIP calls. Using the examples provided I can make unregistered SIP calls fine, however I am having trouble registering with Asterisk. I have to produce an XML Profile to use when registering with a registrar. The one I use is... <provision

Hi, I'm getting crazy about ztdummy. I have to replicate a PBX where ztdummy is working fine but for some reason I cannot. The two machines have the same kernel, motherboard, the same gcc version and the same zaptel 1.4.8. On the second machine zaptel compiles without errors and ztdummy.ko is generated but when I modprobe it I get the following error in messages: rtc: lost some interrupts

> I'm getting crazy about ztdummy. I have to replicate a PBX where ztdummy > is working fine but for some reason I cannot. > The two machines have the same kernel, motherboard, the same gcc version > and the same zaptel 1.4.8. On the second machine zaptel compiles without > errors and ztdummy.ko is generated but when I modprobe it I get the > following error in messages: >

Does anyone know where to disable rtc support on redhat 9.0 using make menuconfig? I thought I disabled it but still got the following error when trying to make zaprtc: zaprtc.c:109: storage size of `rtc_irq_timer' isn't known zaprtc.c:719: storage size of `rtc_fops' isn't known zaprtc.c:107: warning: `DECLARE_WAIT_QUEUE_HEAD' declared `static' but never defined make: ***

Skipped content of type multipart/alternative-------------- next part -------------- Reliably Transmitting (no NAT) to 111.111.111.50:16666: INVITE sip:111.111.111.50:16666 SIP/2.0 Via: SIP/2.0/UDP 111.111.111.8:5060;branch=z9hG4bK360502ae;rport From: "asterisk" <sip:asterisk@111.111.111.8>;tag=as348de10b To: <sip:111.111.111.50:16666> Contact: