Hi,
Actually the drivers you linked to are completely ported from NetBSD and
under the BSD license, so they can be used. The non-BSD licensed virtio
drivers that were ported from FreeBSD have been removed from gitorious.
There's also a different copy of FreeBSD virtio drivers that are under
the BSD license, which you could use as a reference for your work if you
want:
http://lists.freebsd.org/pipermail/freebsd-current/2011-January/022045.html
The NetBSD driver code also has balloon driver at nbsd_code/viomb.c,
which you could also implement.
Tim
On 2/27/11 5:34 PM, Pratyush Kshirsagar wrote:
> Yes, you are right but I did some work porting virtio network driver
> from NetBSD before we moved forward to port it from FreeBSD.
> Attached is the partly done code.
> The other basic calls needed for block and network drivers are kept
> same by Tim and me so that we don't do lot of cleaning and book
> keeping stuff.
>
> The working code is in "net" directory and not the nbsd_code.
> you need to make the outer dir and then the do make in net.
> use kldload -v ./virtio.ko followed by kldload -v ./virtio_net.ko
> Thus when you use dmesg it will show the messages during the netword
> device probe and attach() with the network device number/id.
>
> You can mail me for further information.
>
> - Pratyush Kshirsagar.
>
> 2011/2/27 St廧hanie Ouillon <stephanie@minet.net
> <mailto:stephanie@minet.net>>
>
> Hello,
>
> I've read the posts on the DragonFly BSD Digest site about virtio,
> but I have some questions about it.
>
> A virtual network driver was ported from NetBSD, using some
> FreeBSD code that wasn't supposed to be public under a BSD
> license. So for the moment, the code that is published on
> gitorious
> (http://gitorious.org/virtio-drivers/virtio-drivers/trees/master)
> can't be used at all ? Can somebody tell me more about that ?
> Thanks !
>
>
> Regards,
>
> St廧hanie
>
>