similar to: Some boards won't boot with X100/101P

Hi all! I am in the same situation here in Sweden, but I just got the X100 card and don t get it to work with DTMF caller ID. Is the only way to solve this to buy a TDM400 card w FXO modules? Is it just a driver question or a HW issue with the X100 card? Where to find dok about the new keywords in conf files like "cidstart=polarity" in zapata.conf? rgds Gunnar >>>

I have in my smb.conf file the following entries: time server = yes and logon script = startup.bat Where logon script is as follow: -----start script ----- NET TIME \\SUPERSERVER /SET /YES # Here we map network drives to shares on the Samba Server echo Mapping Network Drives to Samba Server Theremin net use s: \\superserver\scratch net use r: \\superserver\share

Author: krgopi Repository: /hg/zfs-crypto/gate Revision: a813fd7825c4b1d3fb282c08cdf80bc9ffa88a1a Log message: PSARC 2005/654 Nemo soft rings 6306717 For Nemo based drivers, IP can ask dls to do the fanout Files: create: usr/src/uts/common/io/dls/dls_soft_ring.c create: usr/src/uts/common/sys/dls_soft_ring.h update: usr/src/uts/common/Makefile.files update: usr/src/uts/common/inet/ip.h

Hi! > > > Since it is a PCIe card, it does not have the ability to host hardware > > > devices for networking, storage and console. We provide these devices > > > on X100 coprocessors thus enabling a self-bootable equivalent environment > > > for applications. A key benefit of our solution is that it leverages > > > the standard virtio framework for

On Wed, Jul 24, 2013 at 08:31:31PM -0700, Sudeep Dutt wrote: > An Intel MIC X100 device is a PCIe form factor add-in coprocessor > card based on the Intel Many Integrated Core (MIC) architecture > that runs a Linux OS. It is a PCIe endpoint in a platform and therefore > implements the three required standard address spaces i.e. configuration, > memory and I/O. The host OS loads a

This patch adds mergeable receive buffer support to qemu-kvm, to allow enabling it when vhost_net supports it. It also adds a missing call to vhost_net_ack_features() to push acked features to vhost_net. The patch is relative to Michael Tsirkin's qemu-kvm git tree. +-DLS Signed-off-by: David L Stevens <dlstevens at us.ibm.com> diff -ruNp qemu-kvm.mst/hw/vhost_net.c

This patch adds mergeable receive buffer support to qemu-kvm, to allow enabling it when vhost_net supports it. It also adds a missing call to vhost_net_ack_features() to push acked features to vhost_net. The patch is relative to Michael Tsirkin's qemu-kvm git tree. +-DLS Signed-off-by: David L Stevens <dlstevens at us.ibm.com> diff -ruNp qemu-kvm.mst/hw/vhost_net.c

On Wed, Jul 24, 2013 at 08:31:32PM -0700, Sudeep Dutt wrote: > This patch enables the following: > a) Initializes the Intel MIC X100 PCIe devices. > b) Boots and shuts down the card via sysfs entries. > c) Allocates and maps a device page for communication with the > card driver and updates the device page address via scratchpad > registers. > d) Provides sysfs entries for

On Wed, Jul 24, 2013 at 08:31:32PM -0700, Sudeep Dutt wrote: > This patch enables the following: > a) Initializes the Intel MIC X100 PCIe devices. > b) Boots and shuts down the card via sysfs entries. > c) Allocates and maps a device page for communication with the > card driver and updates the device page address via scratchpad > registers. > d) Provides sysfs entries for

We''re building for one case (CONFIG_ACPI_PCI defined) only, yet still had the other case''s code in there. Additionally there was quite a bit of pseudo-duplication between disabled(!) DMI scan and ACPI boot code. acpi_pci_disabled had only a single reader, which is off by default (i.e. must be enable on the command line), so it seems pointless to keep it. Signed-off-by: Jan

Hi! > Since it is a PCIe card, it does not have the ability to host hardware > devices for networking, storage and console. We provide these devices > on X100 coprocessors thus enabling a self-bootable equivalent environment > for applications. A key benefit of our solution is that it leverages > the standard virtio framework for network, disk and console devices, > though in

Hi, I'm trying to configure a clone of X100 for use with asterisk, but i have reached the zaptel.conf step and have not been able to progress further as i'm getting the following error: arnor:~# ztcfg -v Zaptel Configuration ====================== Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) 1 channels configured. ZT_CHANCONFIG failed on channel 1: Invalid

Hello Sudeep Dutt, On Wed, Jul 31, 2013 at 06:46:08PM -0700, Greg Kroah-Hartman wrote: > On Wed, Jul 24, 2013 at 08:31:31PM -0700, Sudeep Dutt wrote: > > An Intel MIC X100 device is a PCIe form factor add-in coprocessor > > card based on the Intel Many Integrated Core (MIC) architecture > > that runs a Linux OS. It is a PCIe endpoint in a platform and therefore > >

Hello Sudeep Dutt, On Wed, Jul 31, 2013 at 06:46:08PM -0700, Greg Kroah-Hartman wrote: > On Wed, Jul 24, 2013 at 08:31:31PM -0700, Sudeep Dutt wrote: > > An Intel MIC X100 device is a PCIe form factor add-in coprocessor > > card based on the Intel Many Integrated Core (MIC) architecture > > that runs a Linux OS. It is a PCIe endpoint in a platform and therefore > >

On Wed, 2013-07-31 at 18:51 -0700, Greg Kroah-Hartman wrote: > On Wed, Jul 24, 2013 at 08:31:32PM -0700, Sudeep Dutt wrote: > > --- /dev/null > > +++ b/drivers/misc/mic/common/mic_device.h > > @@ -0,0 +1,81 @@ > > +/* > > + * Intel MIC Platform Software Stack (MPSS) > > + * > > + * Copyright(c) 2013 Intel Corporation. > > + * > > + * This

On Thu, 2013-09-26 at 14:33 -0700, Joe Perches wrote: > On Thu, 2013-09-26 at 13:54 -0700, Greg Kroah-Hartman wrote: > > On Thu, Sep 05, 2013 at 06:36:08PM -0700, Joe Perches wrote: > > > Whitespace neatening... > > > > > > Multiline statement argument alignment. > > > Argument wrapping. > > > Use kmalloc_array instead of kmalloc. > >

On Thu, Sep 05, 2013 at 06:36:08PM -0700, Joe Perches wrote: > Whitespace neatening... > > Multiline statement argument alignment. > Argument wrapping. > Use kmalloc_array instead of kmalloc. > > --- -ENOSIGNEDOFFBY :(

On Thu, 2013-09-26 at 13:54 -0700, Greg Kroah-Hartman wrote: > On Thu, Sep 05, 2013 at 06:36:08PM -0700, Joe Perches wrote: > > Whitespace neatening... > > > > Multiline statement argument alignment. > > Argument wrapping. > > Use kmalloc_array instead of kmalloc. > > > > --- > > -ENOSIGNEDOFFBY :( These were just suggestions for Sudeep.

On Thu, 2013-09-26 at 13:54 -0700, Greg Kroah-Hartman wrote: > On Thu, Sep 05, 2013 at 06:36:08PM -0700, Joe Perches wrote: > > Whitespace neatening... > > > > Multiline statement argument alignment. > > Argument wrapping. > > Use kmalloc_array instead of kmalloc. > > > > --- > > -ENOSIGNEDOFFBY :( These were just suggestions for Sudeep.

On Thu, Sep 05, 2013 at 06:36:08PM -0700, Joe Perches wrote: > Whitespace neatening... > > Multiline statement argument alignment. > Argument wrapping. > Use kmalloc_array instead of kmalloc. > > --- -ENOSIGNEDOFFBY :(