Update

[l4.git] / l4 / pkg / linux-26-headers / include / linux / virtio_config.h

diff --git a/l4/pkg/linux-26-headers/include/linux/virtio_config.h b/l4/pkg/linux-26-headers/include/linux/virtio_config.h
index 75dc20ba6fff9626524d2ac65fdd44236acba198..a11101e0357d86f499b35360038bc9a2f62dda92 100644 (file)
--- a/l4/pkg/linux-26-headers/include/linux/virtio_config.h
+++ b/l4/pkg/linux-26-headers/include/linux/virtio_config.h
@@ -38,20 +38,27 @@
 #define VIRTIO_CONFIG_S_DRIVER         2
 /* Driver has used its parts of the config, and is happy */
 #define VIRTIO_CONFIG_S_DRIVER_OK      4
+/* Driver has finished configuring features */
+#define VIRTIO_CONFIG_S_FEATURES_OK    8
 /* We've given up on this device. */
 #define VIRTIO_CONFIG_S_FAILED         0x80
 
-/* Some virtio feature bits (currently bits 28 through 31) are reserved for the
+/* Some virtio feature bits (currently bits 28 through 32) are reserved for the
  * transport being used (eg. virtio_ring), the rest are per-device feature
  * bits. */
 #define VIRTIO_TRANSPORT_F_START       28
-#define VIRTIO_TRANSPORT_F_END         32
+#define VIRTIO_TRANSPORT_F_END         33
 
+#ifndef VIRTIO_CONFIG_NO_LEGACY
 /* Do we get callbacks when the ring is completely used, even if we've
  * suppressed them? */
 #define VIRTIO_F_NOTIFY_ON_EMPTY       24
 
 /* Can the device handle any descriptor layout? */
 #define VIRTIO_F_ANY_LAYOUT            27
+#endif /* VIRTIO_CONFIG_NO_LEGACY */
+
+/* v1.0 compliant. */
+#define VIRTIO_F_VERSION_1             32
 
 #endif /* _LINUX_VIRTIO_CONFIG_H */