qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John R. Hogerhuis" <jhoger@speakeasy.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cirrus Logic
Date: Wed, 02 Jun 2004 09:07:32 -0700	[thread overview]
Message-ID: <1086192451.410.237.camel@aragorn> (raw)
In-Reply-To: <40BDBB7A.1080805@fabianowski.de>

On Wed, 2004-06-02 at 04:35, Bartosz Fabianowski wrote:

> I agree that it is very unlikely anybody would care. Most developers 
> also find it boring and annoying to try and figure out the legalities 
> behind every little step they take. I personally just happen to be 
> interested in the legal matters behind things. That is why I posed the 
> question in the first place and that is why I am still interested in 
> seeing whether I can get official permission from Cirrus. Not that 
> others care, I just consider this an interesting task for myself.
> 

I too take interest in these legal issues that crop up.

However, I'm not sure why use of the manuals is an interesting legal
issue when there's no obvious legal issue...

I've never heard using published documentation to implement a clone or
emulation of something being an issue unless you are under NDA or it
involves a patented algorithm. Am I not understanding the problem? Can
you think of an example of such a case? I wonder if Microsoft has a
similar clause in their Win32 documentation, and whether that would stop
the Wine project. And would Microsoft give their permission? If they
could effectively do this, Microsoft would have done this to head off
Wine.

In any event, if you do find someone to ask the convervative answer from
their lawyers would most likely be "no." That's the knee-jerk reaction
when their shareholder interest is orthogonal to the request or possibly
could negatively impact their shareholders. Then what?

Is there any positive interest for the shareholders? If you were to get
a positive response, you'd have to come up with some reasoning that
shows that it is in their shareholders interest to allow their
documentation and hardware to be used to make an emulation. Otherwise I
can almost promise that you will get a "no."

Better to ask forgiveness than permission in some cases.

You'd be more likely to get the answer you want from an independent
lawyer than the successors-in-interest of Cirrus whoever they may be.

-- John.

  reply	other threads:[~2004-06-02 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 12:02 [Qemu-devel] Cirrus Logic Hetz Ben Hamo
2004-06-02 11:35 ` Bartosz Fabianowski
2004-06-02 16:07   ` John R. Hogerhuis [this message]
2004-06-02 17:06     ` Bartosz Fabianowski
2004-06-02 18:35       ` Hetz Ben Hamo

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=1086192451.410.237.camel@aragorn \
    --to=jhoger@speakeasy.net \
    --cc=jhoger@pobox.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).