From: Larry McVoy <lm@bitmover.com>
To: "Kevin O'Connor" <kevin@koconnor.net>
Cc: Erwin Rol <erwin@muffin.org>,
linux-kernel@vger.kernel.org, RTAI users <rtai@rtai.org>
Subject: Re: RTAI/RtLinux
Date: Sat, 25 May 2002 21:18:57 -0700 [thread overview]
Message-ID: <20020525211857.C20253@work.bitmover.com> (raw)
In-Reply-To: <1022317532.15111.155.camel@rawpower> <20020525090537.G28795@work.bitmover.com> <20020526000337.A31674@arizona.localdomain>
On Sun, May 26, 2002 at 12:03:37AM -0400, Kevin O'Connor wrote:
> Using an analogy, consider what would occur if a company revealed it had a
> patent on some key part of the Linux dcache - a patent free for all GPL
> users, but requiring a license for any commercial code. In theory this
> isn't a problem, but what happens when that company starts demanding
> licensing fees from application developers like Oracle, IBM, and even
> BitKeeper Inc? What if the patent holder was Rational Inc and they were
> not eager to license the patent to some companies?
If you think that we don't worry about this, you're wrong. That's why we
write our own code here and don't depend on outside code, and it's also
why we are constantly spending time in the patent database. We've made
changes to BK to avoid Rational patents. Actually, that may not be true,
I just assumed that Rational had the merge alg they use patented but I
never actually found a patent for it. No worries, we came up with a
much nicer way to do it that I'm positive they do not have patented
because their system can't do it.
And that's what the RTAI guys or anyone else would have to do as well.
That's why real engineering is so expensive, it's not enough to just
build it, you have to build it in a way that hasn't been covered by
some patent. The only real way I know to do that cheaply is to be
ahead of everyone else. Otherwise you have to do your homework. And
at this point, it's virtually impossible to be ahead of everyone else,
too much ground has been covered. So you watch the patent database,
you think about how other people solve the problems, you do what you
can. It's not pleasant. That's way they pay you to do it.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-05-26 4:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 9:05 RTAI/RtLinux Erwin Rol
2002-05-25 9:16 ` RTAI/RtLinux Erwin Rol
2002-05-25 13:30 ` RTAI/RtLinux Alan Cox
2002-05-25 13:42 ` RTAI/RtLinux Erwin Rol
2002-05-25 13:21 ` RTAI/RtLinux Der Herr Hofrat
2002-05-25 15:08 ` RTAI/RtLinux Erwin Rol
2002-05-25 16:05 ` RTAI/RtLinux Larry McVoy
2002-05-25 16:28 ` RTAI/RtLinux Karim Yaghmour
2002-05-25 16:30 ` RTAI/RtLinux Erwin Rol
2002-05-25 17:31 ` RTAI/RtLinux Randy.Dunlap
2002-05-25 17:40 ` RTAI/RtLinux Eric Brunner-Williams in Portland Maine
2002-05-25 18:04 ` RTAI/RtLinux Randy.Dunlap
2002-05-25 17:42 ` RTAI/RtLinux Wolfgang Denk
2002-05-26 4:03 ` RTAI/RtLinux Kevin O'Connor
2002-05-26 4:17 ` RTAI/RtLinux Alexander Viro
2002-05-26 4:18 ` Larry McVoy [this message]
[not found] <57.c083d0f.2a237c49@aol.com>
2002-05-27 12:36 ` RTAI/RtLinux Wolfgang Denk
[not found] <a0.2767541f.2a239ebb@aol.com>
2002-05-27 15:18 ` RTAI/RtLinux Wolfgang Denk
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=20020525211857.C20253@work.bitmover.com \
--to=lm@bitmover.com \
--cc=erwin@muffin.org \
--cc=kevin@koconnor.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rtai@rtai.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