qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] why is kqemu closed?
Date: Tue, 11 Apr 2006 11:25:27 -0400	[thread overview]
Message-ID: <20060411152527.GA15858@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <68BDF8E1-CEAF-4900-A0E5-FB91E913F1D4@elis.ugent.be>

On Tue, Apr 11, 2006 at 05:14:59PM +0200, Jonas Maebe wrote:
> 
> On 11 apr 2006, at 17:05, Leonardo E. Reiter wrote:
> 
> >what if I am a hardware vendor in a desperately competitive market,  
> >such as say, video cards.  Releasing my source code to the driver  
> >would mean giving up some IP that allows me to surpass the  
> >capabilities of my competitor for a few weeks.
> 
> Actually, the reason ATi and NVidia don't open source their graphics  
> drivers is because they are both afraid that as soon as as they do  
> that, the other one will sue them into oblivion based on software  
> patents.
> 
> See http://wiki.ffii.org/Smirl041025En for the full story.
> 
> 
> Jonas
> 
> 

I wonder, could it be possible that Fabrice is worried about the same
thing? Who holds the patents for x86 virtualization technologies?

Then again, Fabrice is in France iiuc... 

> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2006-04-11 15:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 15:16 [Qemu-devel] why is kqemu closed? Rakotomandimby Mihamina
2006-04-10 15:20 ` Hetz Ben Hamo
2006-04-10 15:47   ` Auke Kok
2006-04-10 15:55     ` Hetz Ben Hamo
2006-04-10 15:56     ` Leonardo E. Reiter
2006-04-11  4:37       ` Auke Kok
2006-04-11  7:58         ` Brad Campbell
2006-04-11 16:22           ` Jim C. Brown
2006-04-11  8:37         ` Ricardo Almeida
2006-04-11  9:46         ` Johannes Schindelin
2006-04-11 10:05           ` Jamie Lokier
2006-04-11 15:05         ` Leonardo E. Reiter
2006-04-11 15:14           ` Jonas Maebe
2006-04-11 15:25             ` Jim C. Brown [this message]
2006-04-11 16:04               ` Jonas Maebe
2006-04-11 15:36           ` Paul Brook
2006-04-11 15:43             ` M. Warner Losh
2006-04-11 16:00               ` Paul Brook
2006-04-11 16:29                 ` M. Warner Losh
2006-04-11 16:09           ` Jim C. Brown
2006-04-11 17:10             ` Enough already! " Bakul Shah
2006-04-11 15:17         ` Sebastian Kaliszewski
2006-04-11 15:31           ` M. Warner Losh
2006-04-11 12:33       ` andrzej zaborowski
2006-04-11 13:58         ` Jamie Lokier
2006-04-11 15:10         ` Sebastian Kaliszewski
2006-04-11 15:19           ` M. Warner Losh
2006-04-10 15:57     ` Brett (Mare) Henley
2006-04-10 16:02       ` Leonardo E. Reiter
2006-04-10 19:11     ` M. Warner Losh

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=20060411152527.GA15858@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --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).