search for: vdv

Hi, Xorcom astribanks get initialized straight on when using Ubuntu 11.10 packages but I am having a hard time to get the same result running in a qemu/libvirt image. The first difficulty is that astribanks devices get different usb device ids during their initialisation process, requiring hot plug support. I have figured out how to solve this issue using the technique described in this post :

...ice > * @vdev: vdpa device > @@ -178,6 +183,7 @@ struct vdpa_config_ops { > u64 (*get_vq_state)(struct vdpa_device *vdev, u16 idx); > struct vdpa_notification_area > (*get_vq_notification)(struct vdpa_device *vdev, u16 idx); > + u32 (*get_vq_irq)(struct vdpa_device *vdv, u16 idx); > > /* Device ops */ > u32 (*get_vq_align)(struct vdpa_device *vdev);

hi*& ppl, what I see? smbstat shows this: veda uucp uucp 17012 vdv (193.168.6.84) Sun Dec 19 14:33:43 1999 squid-wate piv guest 19110 nlv (193.168.6.74) Mon Dec 20 08:51:18 1999 squid-nav paul wheel 19110 nlv (193.168.6.74) Mon Dec 20 08:51:42 1999 nlv nlv guest 19110 nlv (193.168.6.74) Mon Dec 20 09:1...

...> - struct vdpa_vq_state *state); > + int (*get_vq_state)(struct vdpa_device *vdev, u16 idx, > + struct vdpa_vq_state *state); > struct vdpa_notification_area > (*get_vq_notification)(struct vdpa_device *vdev, u16 idx); > int (*get_vq_irq)(struct vdpa_device *vdv, u16 idx);

I'm simulating a Markov process using a vector of proportions. Each value in the vector represents the proportion of the population who are in a particular state (so the vector sums to 1). I have a square matrix of transition probabilities, and for each tick of the Markov clock the vector is multiplied by the transition matrix. To illustrate the sort of thing I mean: pm <-

...th 0 Nov 14 00:44:41 asterisk udevd[452]: seq 1516 done with 0 I have tried with the version of dahdi that comes with Ubuntu 9.10 and I am now trying with the svn version of dahdi with no more success. Does anyone have an idea how I can solve this issue? Thanks, Eric -- Eric van der Vlist <vdv at dyomedea.com> Dyomedea (http://dyomedea.com)

...state)(struct vdpa_device *vdev, u16 idx, > struct vdpa_vq_state *state); > struct vdpa_notification_area > (*get_vq_notification)(struct vdpa_device *vdev, u16 idx); > /* vq irq is not expected to be changed once DRIVER_OK is set */ > int (*get_vq_irq)(struct vdpa_device *vdv, u16 idx); > > /* Device ops */ > u32 (*get_vq_align)(struct vdpa_device *vdev); > u64 (*get_features)(struct vdpa_device *vdev); > int (*set_features)(struct vdpa_device *vdev, u64 features); > void (*set_config_cb)(struct vdpa_device *vdev, > struct vdpa_callbac...

...>>>>> ?????struct vdpa_notification_area >>>>> ?????(*get_vq_notification)(struct vdpa_device *vdev, u16 idx); >>>>> ?????/* vq irq is not expected to be changed once DRIVER_OK is set */ >>>>> ?????int (*get_vq_irq)(struct vdpa_device *vdv, u16 idx); >>>>> >>>>> ?????/* Device ops */ >>>>> ?????u32 (*get_vq_align)(struct vdpa_device *vdev); >>>>> ?????u64 (*get_features)(struct vdpa_device *vdev); >>>>> ?????int (*set_features)(struct vdpa_device *vdev, u6...

...od thing or not, I doubt I can convince Free (http://free.fr) which is one of the biggest ISPs in France to change their policy so that I can receive SIP calls again... If my diagnostic is right, is there a way to work around this issue with asterisk 1.6? Thanks, Eric -- Eric van der Vlist <vdv at dyomedea.com> Dyomedea (http://dyomedea.com)

...????? struct vdpa_vq_state *state); >>> ????struct vdpa_notification_area >>> ????(*get_vq_notification)(struct vdpa_device *vdev, u16 idx); >>> ????/* vq irq is not expected to be changed once DRIVER_OK is set */ >>> ????int (*get_vq_irq)(struct vdpa_device *vdv, u16 idx); >>> >>> ????/* Device ops */ >>> ????u32 (*get_vq_align)(struct vdpa_device *vdev); >>> ????u64 (*get_features)(struct vdpa_device *vdev); >>> ????int (*set_features)(struct vdpa_device *vdev, u64 features); >>> ????void (*set_co...

On Thu, Jul 02, 2020 at 01:51:21PM +0530, Kishon Vijay Abraham I wrote: > This series enhances Linux Vhost support to enable SoC-to-SoC > communication over MMIO. This series enables rpmsg communication between > two SoCs using both PCIe RC<->EP and HOST1-NTB-HOST2 > > 1) Modify vhost to use standard Linux driver model > 2) Add support in vring to access virtqueue over

On Thu, Jul 02, 2020 at 01:51:21PM +0530, Kishon Vijay Abraham I wrote: > This series enhances Linux Vhost support to enable SoC-to-SoC > communication over MMIO. This series enables rpmsg communication between > two SoCs using both PCIe RC<->EP and HOST1-NTB-HOST2 > > 1) Modify vhost to use standard Linux driver model > 2) Add support in vring to access virtqueue over

Hi All I have the following setup Users ------- Machine A ----------- Machine B ----------- Machine C >From machine A to B: Ipsec VPN Allows 192.168.10.0/24 (Users) to connect to 192.168.20.0/24 (Network on machine B) >From machine B to C: Ipsen VPN Allows 196.44.33.118 to coccent to 192.168.241.65 (machine C) I want to rewrite 192.168.20.33 to 192.168.241.65 This can be done

Hi I have a default route to 192.168.1.1 as soon as I start shorewall the default route dissapear. What do I need to do to have it not disappear. Kind Regards My network setup /etc/network/interfaces: # The primary network interface auto eth0 iface eth0 inet static address 192.168.1.17 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255