summaryrefslogtreecommitdiff
path: root/contributing.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2013-09-26 15:58:55 +0200
committerThomas Schwinge <thomas@codesourcery.com>2013-09-26 15:58:55 +0200
commit583535d65ef20474d970c71f90d39ff5f5bf7180 (patch)
tree9867c64dd41e510613fc1e95a357c832dc71c3d5 /contributing.mdwn
parent295f1c447d706315e5bce15365f89c9e6983c721 (diff)
parent99f7a42c80813fcbec01277ceb13a82f7f4421c7 (diff)
Merge commit '99f7a42c80813fcbec01277ceb13a82f7f4421c7'
Conflicts: open_issues/dde.mdwn
Diffstat (limited to 'contributing.mdwn')
-rw-r--r--contributing.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributing.mdwn b/contributing.mdwn
index 75b99bbd..68dcca0c 100644
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -103,7 +103,7 @@ access to it from userland. exec would probably call it from `hurd/exec/exec.c`,
which exposes the partitions of the disk image, using parted, and
the parted-based storeio (`settrans -c foos1 /hurd/storeio -T typed
part:1:file:/home/samy/tmp/foo`). This would be libnetfs-based.
-* Write virtio drivers for KVM. Ideally they would be userland. That means getting documented about how virtio works, and implement it. The hurdish part is mostly about exposing the driver interface. The devnode translator can be used as a skeleton.
+* Write [[virtio drivers for KVM|virtio#KVM]].
* Port valgrind. There is a whole
[[GSoC proposal|community/gsoc/project_ideas/valgrind ]] about this, but the
basic port could be small.