search for: aknowledgements

I am not sure a previous e-mail reached the list (no mail aknowledgement from R-boundle etc.). The question was how to write polygon or segment coordinates into a shapefile set or any other ArcGIS supported format. The library shapefiles seems to do something but the documentation is a bit beyond of my mind.... and I cannot get the meaning of the functions write**** and its application to the case

On Thu, Apr 02, 2015 at 03:17:13PM +0200, Greg Kurz wrote: > This patch brings cross-endian support to vhost when used to implement > legacy virtio devices. Since it is a relatively rare situation, the feature > availability is controlled by a kernel config option (not set by default). > > If cross-endian support is compiled in, vhost abvertises a new feature > to be negotiated

On Thu, Apr 02, 2015 at 03:17:13PM +0200, Greg Kurz wrote: > This patch brings cross-endian support to vhost when used to implement > legacy virtio devices. Since it is a relatively rare situation, the feature > availability is controlled by a kernel config option (not set by default). > > If cross-endian support is compiled in, vhost abvertises a new feature > to be negotiated

Arnaud, my UPS arrived yesterday; thanks for your generosity. I'm using it to power the computer I'm typing on. This moves NUT up a few places on my priority list. In our last email exchange, I believe we agreed on a couple of major points. I want to confirm these before I start modifying the documentation heavily. 1. asciidoc is a good master format for the in-tree documentation. 2.

This patch brings cross-endian support to vhost when used to implement legacy virtio devices. Since it is a relatively rare situation, the feature availability is controlled by a kernel config option (not set by default). If cross-endian support is compiled in, vhost abvertises a new feature to be negotiated with userspace. If userspace acknowledges the feature, it can inform vhost about the

On Thu, 2 Apr 2015 16:20:46 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > On Thu, Apr 02, 2015 at 03:17:13PM +0200, Greg Kurz wrote: > > This patch brings cross-endian support to vhost when used to implement > > legacy virtio devices. Since it is a relatively rare situation, the feature > > availability is controlled by a kernel config option (not

http://bugs.freedesktop.org/show_bug.cgi?id=16103 Summary: http://www.leparisien.fr of 26052008 crashed with swfdec Product: swfdec Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: plugin AssignedTo: swfdec at

Hi, This patchset allows vhost to be used with legacy virtio when guest and host have a different endianness. It is a complete rework of my initial post. Patches 1 to 5 are preliminary work: we move the endianness check out of all memory accessors to separate functions. Patch 6 changes the semantics of the accessors so that they have explicit big endian support. Patch 7 brings the cross-endian

Hi, This patchset allows vhost to be used with legacy virtio when guest and host have a different endianness. It is a complete rework of my initial post. Patches 1 to 5 are preliminary work: we move the endianness check out of all memory accessors to separate functions. Patch 6 changes the semantics of the accessors so that they have explicit big endian support. Patch 7 brings the cross-endian

I have downloaded ruby 1.9.1 binaries to c:\ruby191 (I have ruby 1.8.6 under c:\ruby). I then downloaded gems 1.3.1 and ran "gem install rails --include-dependencies" from c:\ruby191\bin and it ran and came up with a segment error and killed the rails install. Any ideas what I am doing wrong? Thanks Chris -- Posted via http://www.ruby-forum.com/.