similar to: Restricting the manager interface to a number?

Hi! System: Debian/testing with selfcompiled kernel 3.5.5 (same error with 3.4 or 3.6) XEN: 4.1.3 After booting the Dom0 I notice the following errors: [ 2.939078] microcode: CPU0 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.991998] microcode: CPU0 update to revision 0xa0b failed [ 2.992035] microcode: CPU1 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.995882] microcode: CPU1 update to

AFAICT our current version does not correspond to any version in the Linux history. This commit resynchronised to the state in Linux commit 598bae70c2a8e35c8d39b610cca2b32afcf047af. Differences from upstream: find_cpio_data is __init, printk instead of pr_*. This appears to fix Debian bug #785187. "Appears" because my test box happens to be AMD and the issue is that the (valid) cpio

Hi! I have the following questions/problems with * 1.4. We have several Snom phones (320 and 360). Hints are configured in extensions.conf (core show hints shows the correct values). My Snom phone is registered to some numbers (validated by using sip show subscriptions). I see the lights blinking if someone calls the subscribed number and steady lights if the call is established. So far, so

On Tue, 2015-05-19 at 13:31 +0200, Stephan Seitz wrote: > On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: > >Here's an idea. First extract the real initrd from the back half of the > >initrd: > > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > > kernel > > kernel/x86 > >

On Thu, 2015-05-14 at 22:45 +0200, Stephan Seitz wrote: > On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote: > >> > according to the documentation the option ucode=scan should tell XEN to > >> > look for a microcode update in an uncompressed initrd. > >> > > >> > While I don?t use the Debian kernel the tools to generate the

Hi! I would like to know the status of the frequency scaling in XEN. I found a web site saying that XEN doesn’t work with frequency scaling, at the other hand I found some fixes for powernow-k8 to get rid of some messages. I have an AMD64. powerno-k8 works find with non-XEN kernels, but with XEN-kernels I get the error: powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3400+ processors

> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory structure

On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote: >> > according to the documentation the option ucode=scan should tell XEN to >> > look for a microcode update in an uncompressed initrd. >> > >> > While I don?t use the Debian kernel the tools to generate the initrd are >> > part of Debian. The command ?cpio -i <

On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: >Here's an idea. First extract the real initrd from the back half of the >initrd: > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > kernel > kernel/x86 > kernel/x86/microcode > kernel/x86/microcode/GenuineIntel.bin > 16 blocks

On Tue, May 19, 2015 at 12:47:51PM +0100, Ian Campbell wrote: >The reconcatenate bit is easy, just: > $ cat initrd.ucode initrd.real > initrd.img >With initrd.real extracted above. > >initrd.ucode creation I'm a little unsure about but something like: > >$ mkdir initrd.ucode.tree >$ cd initrd.ucode.tree >$ cat /boot/initrd.img | cpio -id >$ find >.

Package: xen-hypervisor-4.5-amd64 Version: 4.5.0-1 Severity: normal Dear Maintainer, according to the documentation the option ucode=scan should tell XEN to look for a microcode update in an uncompressed initrd. While I don?t use the Debian kernel the tools to generate the initrd are part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? creates the directory structure

>>> On 01.07.15 at 16:43, <ian.campbell at citrix.com> wrote: > AFAICT our current version does not correspond to any version in the > Linux history. This commit resynchronised to the state in Linux > commit 598bae70c2a8e35c8d39b610cca2b32afcf047af. > > Differences from upstream: find_cpio_data is __init, printk instead of > pr_*. > > This appears to fix

Hello all, I''m trying to get my servers to work with Xen, but as I use sata2, it looks like only a recent kernel will do the job. But unferotunately, ony and official 2.6.8 is provided, which doesn''t boot at all on those machines. I''ve tried ubuntu''s 2.6.22-xen, but ti looks very buggy. Where could we find patches for 2.6.22/23 to add Xen? How could I gete a

Oof, I didn't think about Clang not being in the same place. Perhaps we could put this in clang-tools-extra to solve that? As for the unification of the code bases. I was assuming we didn't want to just throw a ton of code over the wall anyway so the merge was going to need to be reviewed chunk by chunk anyhow. Support for the two formats should be possible to add in parallel (although, I

Hi, This is a bit off-topic, but still related to telephony. Is there a barebones TAPI driver that exists that would allow me to call up a command line with, as parameter, the number to dial. For exemple, Outlook integrates with TAPI, so that TAPI driver would allow me to call my own app with the phone number as argument. ex when clicking on 555-555-5555: the TAPI driver would call

Since the goal is to start llvm-tapi more or less from scratch, I feel the best approach initially is to focus on the structure as a key point of feedback in initial reviews. Once the foundations are set, integrating Mach-O TAPI in parallel with the ELF implementation should be relatively straightforward. The features outside of stubbing aren't as appealing for ELF, so I probably won't be

On Thu, Sep 27, 2018 at 3:12 PM Rui Ueyama via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Thu, Sep 27, 2018 at 2:42 PM Armando Montanez via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Since the goal is to start llvm-tapi more or less from scratch, I feel >> the best approach initially is to focus on the structure as a key >> point of

Hi, To make a long story short, I can't install any TAPI driver on my XP platform. A. Within Config Panel|Modems and Telephony options|Advanced parameters, I've got a list of 7 TAPI drivers. Among them is Omniis TAPI driver for Asterisk. B. I can properly configure this driver (line, context, ...). C. When I open Outlook 2002 Contacts panel, I can select "Call this contact"

Hello all, LLVM-TAPI seeks to decouple the necessary link-time information for a dynamic shared object from the implementation of the runtime object. This process will be referred to as dynamic shared object (DSO) stubbing throughout this proposal. A number of projects have implemented their own versions of shared object stubbing for a variety of reasons related to improving the overall linking

Absolutely. The goal of the tool is to produce both textual and binary DSO stubs. This means you could take a DSO, produce a textual stub, modify it however you wish, and then produce a linkable binary stub from that modified .tbe. That, or you could bypass the textual portion altogether and just produce binary stubs from DSOs. While the textual format is useful, the goal is to make the tool