public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Alexander Stohr <alexander.stohr@gmx.de>
Cc: airlied@gmail.com, kendallb@scitechsoft.com,
	linux-kernel@vger.kernel.org
Subject: Re: Re: HARDWARE: Open-Source-Friendly Graphics Cards -- Viable?]
Date: Fri, 29 Oct 2004 19:14:34 -0400	[thread overview]
Message-ID: <9e47339104102916141019bd23@mail.gmail.com> (raw)
In-Reply-To: <015101c4bde1$1051bce0$8511050a@alexs>

On Fri, 29 Oct 2004 19:12:15 +0200, Alexander Stohr
<alexander.stohr@gmx.de> wrote:
> Hi Jon, Hi audience,
> 
> (I just got aware of that discussion because i got that mail CCed
> trough a resend on a general discussion list about software patents.)
> 
> Even if ATI and nVidia, plus maybe even IBM, would sign a well written
> and working agreement between them all, it would not stop anybody else
> out there in the world that is holding patents from inspecting the unveiled
> data and then looking for specific things that might work for pressing out
> some Billion dollars from those companys. Patents do work, but they do
> work mostly for the lawers income, and for companys that have the only
> purpose for getting revenues from a "bought up" patent portfolio. Those
> can be really nastys, even if you are Microsoft you dont like to pull out

The best way to make this work would be to get ATI, nVidia, IBM and
Intel into a room and do a cross licensing deal on the interface
portion of the designs. If the four companies also enter into a mutual
defense pact that will stop any third parties from causing trouble.

On the other hand, this strategy doesn't work if you are currently,
knowingly violating an existing valid patent.

Keeping things secret does nothing to protect you from a patent
infringement suit. All it does is make it a little harder to initially
detect that there are grounds for one. Once someone files suit they
will use the legal process to get all your secret designs anyway.

I also question if keeping interfaces secret is gaining anyone any
advantages over the competitors. Everyone involved possess an
excellent engineering staff capable of easily figuring out what the
other groups are doing. GPUs compete on functional units, chip
processes, parallelism, marketing and manufacturing cost, not on the
device driver programming model.

My belief is that everyone involved would gain from contributing to a
common pool of code for Linux. I don't believe that doing this is
going to alter anyone's market share; but it will make the users a lot
happier and breed goodwill for all involved.

-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2004-10-29 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1098806794.6000.7.camel@tara.firmix.at>
2004-10-29 17:12 ` Re: HARDWARE: Open-Source-Friendly Graphics Cards -- Viable?] Alexander Stohr
2004-10-29 23:14   ` Jon Smirl [this message]
2004-10-30 16:48     ` Alexander Stohr
2004-10-30 17:57       ` Jon Smirl

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=9e47339104102916141019bd23@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=airlied@gmail.com \
    --cc=alexander.stohr@gmx.de \
    --cc=kendallb@scitechsoft.com \
    --cc=linux-kernel@vger.kernel.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