search for: aknowledg

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***...

...d with userspace. If userspace acknowledges the feature, > it can inform vhost about the endianness to use with a new ioctl. > > This feature is mutually exclusive with virtio 1.0. Even if the vhost device > advertises virtio 1.0 and legacy cross-endian features, it cannot receive > aknowledgement for both at the same time. > > Hot paths are being preserved from any penalty when the config option is > disabled or when virtio 1.0 is being used. > > Signed-off-by: Greg Kurz <gkurz at linux.vnet.ibm.com> > --- > drivers/vhost/Kconfig | 10 ++++++++++ &gt...

...d with userspace. If userspace acknowledges the feature, > it can inform vhost about the endianness to use with a new ioctl. > > This feature is mutually exclusive with virtio 1.0. Even if the vhost device > advertises virtio 1.0 and legacy cross-endian features, it cannot receive > aknowledgement for both at the same time. > > Hot paths are being preserved from any penalty when the config option is > disabled or when virtio 1.0 is being used. > > Signed-off-by: Greg Kurz <gkurz at linux.vnet.ibm.com> > --- > drivers/vhost/Kconfig | 10 ++++++++++ &gt...

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.

...w feature to be negotiated with userspace. If userspace acknowledges the feature, it can inform vhost about the endianness to use with a new ioctl. This feature is mutually exclusive with virtio 1.0. Even if the vhost device advertises virtio 1.0 and legacy cross-endian features, it cannot receive aknowledgement for both at the same time. Hot paths are being preserved from any penalty when the config option is disabled or when virtio 1.0 is being used. Signed-off-by: Greg Kurz <gkurz at linux.vnet.ibm.com> --- drivers/vhost/Kconfig | 10 ++++++++++ drivers/vhost/net.c | 5 +++...

...space acknowledges the feature, > > it can inform vhost about the endianness to use with a new ioctl. > > > > This feature is mutually exclusive with virtio 1.0. Even if the vhost device > > advertises virtio 1.0 and legacy cross-endian features, it cannot receive > > aknowledgement for both at the same time. > > > > Hot paths are being preserved from any penalty when the config option is > > disabled or when virtio 1.0 is being used. > > > > Signed-off-by: Greg Kurz <gkurz at linux.vnet.ibm.com> > > --- > > drivers/vhost...

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/.