From: higepon <higepon@gmail.com>
To: Pantelis Koukousoulas <pktoss@gmail.com>
Cc: Brian Jackson <iggy@theiggy.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio documentation or BSD licensed driver?
Date: Mon, 4 May 2009 19:36:29 +0900 [thread overview]
Message-ID: <f07386410905040336m77f93966j8d545f6f06189a93@mail.gmail.com> (raw)
In-Reply-To: <1295ed070905040223m3e4f08cq259c4ab696b7ef44@mail.gmail.com>
Hi.
I really appreciate your help. Thanks.
That's what I want to know about.
> 2) Think of virtio-net as just another (sophisticated) PCI driver and
> look at its implemenation
> in qemu. Although qemu is not BSD licensed, your work is unlikely to
> be considered a derivative
> of qemu since you are implementing a driver for that virtual
> "hardware", not another copy it.
Maybe this is suitable for my OS.
> The BSD virtio headers, the paper and the virtio-net qemu
> implementation should be enough to
> allow you to write a driver for your OS imho (it is already more info
> than you typically get for
> real hardware)
Okay I will start from reading the paper.
> P.S., in practice I believe several developers for other OSes look at
> the sources of linux drivers
> as sort of a really good documentation for hardware, even if the
> license of their OS is incompatible.
> IANAL and all that, but I 'd be really suprised if you got sued for
> porting virtio-net to your hobby OS :)
Interesting and resonable.
But Since Mona OS is my life work, i want to avoid from license problems.
Cheers.
next prev parent reply other threads:[~2009-05-04 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 4:05 [Qemu-devel] virtio documentation or BSD licensed driver? higepon
2009-05-04 4:21 ` Brian Jackson
2009-05-04 6:07 ` higepon
2009-05-04 9:23 ` Pantelis Koukousoulas
2009-05-04 10:36 ` higepon [this message]
2009-05-10 14:08 ` higepon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f07386410905040336m77f93966j8d545f6f06189a93@mail.gmail.com \
--to=higepon@gmail.com \
--cc=iggy@theiggy.com \
--cc=pktoss@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).