All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Chuck Campbell <campbell@accelinc.com>,
	Jamie Lokier <jamie@shareable.org>,
	Arjan van de Ven <arjanv@redhat.com>,
	Lennert Buytenhek <buytenh@gnu.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [OT] use of patented algorithms in the kernel ok or not?
Date: Tue, 13 Jan 2004 16:04:49 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0401131525290.9807@chaos> (raw)
In-Reply-To: <20040113193549.GB294@elf.ucw.cz>

On Tue, 13 Jan 2004, Pavel Machek wrote:

> Hi!
>
> > > > I know that equivalent code, which is covered by most if not all of
> > > > the patents, is sold by some software companies to product developers
> > > > _in the USA_ without prelicensed patents.  The problem of acquiring
> > > > suitable patent licenses is left to the purchasers.
> > > >
> > > > Rationally I would expect that if someone is able to sell code and
> > > > leave the problem of patent licensing to the purchaser, then one
> > > > should be able to _give away_ code and leave the problem of patent
> > > > licensing to the recipient.
> > >
> > > As far as I can see, it is okay to ignore patents *if
> > > you are doing research*. So you should be able to offer
> > > it to US people for research purposes.
> >
> > According to recently passed legislation, this may no longer be true.  It
> > remains to be tested, but my understanding is that this "research" shield
> > is now gone.
>
> Time to move to Cuba?
>
> [Well, I thought that explicit reason for patents is "to promote
> research", and it used to be okay to improve upon someone else's
> patent. If patents no longer serve that purpose (if you can't improve
> upon someone elses work, it is worse than he keeping it secret; and
> patents were made so that people would not keep stuff secret), perhaps
> its time to ask if they are still constitutional?]
> 								Pavel
>

According to current Patent Law in the United States;

FYI: Read

http://www4.law.cornell.edu/uscode/35/273.html

You infringe just by smelling like a patent. However, there
are lots of defenses to infringement: prior art, prior reduction
to practice, practically anything done in "good faith", i.e., use
of a process that was not known to be patented. Good faith is
required to show that infringement was stopped as soon as the
inventor brought the infringement to the attention of the
infringer, etc.

Basically, you do NOT have to check to see if your "process" or
whatever has been previously invented. You do, however, need to
stop infringing as soon as such infringement becomes known.

For that reason, it is my opinion (not the opinion of any court,
or officer of the court) that a search for possible patent
infringements can only lead to hardship. You might find an
infringement that was never enforced or is not enforceable,
forcing you to rewrite stuff that is "common public knowledge".
Or you might find that everything is original and, therefore have
a false sense of security (Santa Claus Operations ^M^MSCO^M^M might
sue you anyway....)

For patents that have been secured by a company, but made secret
by the government, you certainly have no way of knowing if an
invention exists. For instance, it is common knowledge that the
transistor was invented by Bill Shockley and John Bardeen at
AT&T in 1948.  However, arming mechanisms for torpedos, used
in WWII, used transistors. The boards containing them had a
US Navy Anchor stamp, marked 1945, 3 years before they were
invented. This was my source of transistors, from Eli Hefferon's
electronic scrap, as a boy!

Also, when I made a  solid-state rate-gyro as a high school
Science Fair project, I got a cease and desist order from a
federal court in New York, because Sperry claimed that what
I developed was their secret invention... Go figure.

It was many years later that I understood that the "acoustic gyro"
I made  as a kid used the same principles as the strap-down-laser-gyro
that Sperry had developed for ICBMs. The government apparently thought
that my project would make obvious to "the enemy" what was obvious to
all my class-mates, --hardly an earth shaking invention.

Basically do what original thought, review of published documentation,
and ordinary care lets you do. Don't waste time worrying about suits
from the ass^M^Mrectums that exist. If they want to sue, they will.
If they don't, they won't. They won't let facts get in the way.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-01-13 21:04 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 23:11 [OT] use of patented algorithms in the kernel ok or not? Lennert Buytenhek
2003-12-19  6:10 ` Linus Torvalds
2003-12-19  7:38 ` Paul Jackson
2003-12-19  8:47 ` Arjan van de Ven
2003-12-19 11:38   ` Jan-Benedict Glaw
2003-12-20 17:28   ` Stefan Traby
2003-12-21 10:33   ` Jamie Lokier
2003-12-21 16:57     ` Pavel Machek
2004-01-13 15:35       ` Chuck Campbell
2004-01-13 19:35         ` Pavel Machek
2004-01-13 21:04           ` Richard B. Johnson [this message]
2003-12-22  0:37     ` jw schultz
2003-12-21 23:39   ` Lennert Buytenhek
2003-12-21  1:25 ` jw schultz
2003-12-21 19:40   ` Lennert Buytenhek
2003-12-21  1:12 Albert Cahalan
2003-12-21 10:53 ` Jamie Lokier
2003-12-21 13:35   ` James Morris
2003-12-21 14:30     ` Jamie Lokier
2003-12-21 16:03       ` Xavier Bestel
2003-12-21 14:56     ` Arjan van de Ven
2003-12-21 19:33       ` Stan Bubrouski
2003-12-21 23:25         ` Helge Hafting
2003-12-21 19:29   ` Stan Bubrouski
2003-12-21 19:55     ` Matthias Schniedermeyer
2003-12-21 20:11       ` Stan Bubrouski
2003-12-21 21:52       ` Francois Romieu
2003-12-21 21:57     ` Jamie Lokier
2003-12-22  9:50       ` John Bradford
2003-12-22 15:34         ` Adrian Cox
2003-12-22  1:43 James Lamanna
2003-12-22 11:32 ` Matti Aarnio

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=Pine.LNX.4.53.0401131525290.9807@chaos \
    --to=root@chaos.analogic.com \
    --cc=arjanv@redhat.com \
    --cc=buytenh@gnu.org \
    --cc=campbell@accelinc.com \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.