From: Mark Mielke <mark@mark.mielke.cc>
To: Karim Yaghmour <karim@opersys.com>
Cc: yodaiken@fsmlabs.com, linux-kernel@vger.kernel.org
Subject: Re: A reply on the RTLinux discussion.
Date: Tue, 28 May 2002 11:39:38 -0400 [thread overview]
Message-ID: <20020528113938.B17353@mark.mielke.cc> (raw)
In-Reply-To: <57.c083d0f.2a237c49@aol.com> <20020527123643.9297A11973@denx.denx.de> <20020528060406.A18344@hq.fsmlabs.com> <3CF3A009.E7320E98@opersys.com>
On Tue, May 28, 2002 at 11:19:37AM -0400, Karim Yaghmour wrote:
> Thanks Victor for taking the time to go through some of the issues.
> yodaiken@fsmlabs.com wrote:
> > 1. MYTH: "The acceptance of Linux in embedded is being harmed by
> > uncertainty over intellectual property"
> That is your own assesment, which is of course somewhat biased since I
> don't see you coming out and telling us: "True, the market has a problem
> with my patent." This standpoint is the only one expected. But given
> that you are not the only vendor out there, others have testified on this
> list that indeed Linux has a hard time penetrating in the embedded/rt
> market precisely because of your patent.
Sounds like people who can't get customers calling foul to the one
that can.
> I will leave it to the average LKML reader to decide whether the problems
> I discribe are "myth" of "fact" in light of all the testimony presented on
> this list.
I would label it "seriously exaggerated fact to obtain market share".
> Also, you omit to explain why the 11,000 developers sampled by the VDC
> point "real-time limitations" as their #1 show-stopper for using Linux.
"Real-time limitations" *are* the #1 show-stopper for using Linux. This
isn't an argument for or against your point.
> > And most of embedded Linux use does not require hard real-time.
> You're trying to play the "niche" trick here, pointing out that your
> patent is OK because it's a niche market. As I pointed out very
> early in this thread, embedded/rt is far from being a niche.
Actually, it looked like he was just presenting a fact. Most people that
say they need RT, don't, and the few that do, do not tend to mind patents.
> > 2. MYTH "The patent license is a terrible burden and terribly vague".
> FSMLabs cannot be compared in any way to any other open source company:
> I can rewrite Qt and distribute it under the license I like
> I can rewrite MySQL and distribute it under the license I like
> I can't rewrite RTLinux and distribute it under the license I like
> As for your dismissal of the "motivation behind the act", it does not
> dismiss any of our arguments, but only reinforces them.
Most companies with serious RT requirements do not wish to re-write
and distribute 'as they like'. In fact, the only reason they have to
do this now, is because the tools are not mature enough.
The problem here is obviously open-source companies that prefer to
avoid paying for software, because they do not sell software, and
companies that sell software, and do not mind paying for software to
sell software.
The fact is, patents are legal. Live with it, or convince a few
senators that they should remove 'patent infringement' from the set of
actions that can be tried in a court of law.
You are not getting anywhere here.
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2002-05-28 15:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57.c083d0f.2a237c49@aol.com>
2002-05-27 12:36 ` RTAI/RtLinux Wolfgang Denk
2002-05-28 12:04 ` A reply on the RTLinux discussion yodaiken
2002-05-28 14:37 ` Roman Zippel
2002-05-28 15:57 ` Alan Cox
2002-05-28 15:11 ` Roman Zippel
2002-05-28 16:45 ` Alan Cox
2002-05-29 0:31 ` Roman Zippel
2002-05-29 1:34 ` Mark Mielke
2002-05-29 3:11 ` Karim Yaghmour
2002-05-29 8:53 ` Zwane Mwaikambo
2002-05-29 13:54 ` Dana Lacoste
2002-05-29 15:17 ` Alan Cox
2002-05-29 14:20 ` Dana Lacoste
2002-05-29 15:15 ` Mark Mielke
2002-05-29 17:43 ` Dana Lacoste
2002-05-29 18:26 ` Mark Mielke
2002-05-29 15:31 ` Alan Cox
2002-05-29 15:45 ` yodaiken
2002-05-29 17:40 ` Dana Lacoste
2002-06-03 10:09 ` Rob Landley
2002-05-29 13:24 ` Alan Cox
2002-05-29 13:43 ` Roman Zippel
2002-05-29 14:59 ` Alan Cox
2002-05-29 20:18 ` Roman Zippel
2002-05-31 11:57 ` Pavel Machek
2002-05-31 21:34 ` Mark Mielke
2002-05-31 23:19 ` yodaiken
2002-05-28 15:19 ` Karim Yaghmour
2002-05-28 15:39 ` Mark Mielke [this message]
2002-05-28 16:00 ` Karim Yaghmour
2002-06-01 20:37 ` Michael Barabanov
2002-05-28 16:12 James Bottomley
2002-05-28 17:31 ` Roman Zippel
2002-05-28 18:03 ` James Bottomley
2002-05-28 21:21 ` Jeff V. Merkey
2002-05-29 8:58 ` Peter Wächtler
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 12:36 Rose, Billy
2002-05-29 19:46 ` Daniel Phillips
2002-05-29 19:58 ` Mark Mielke
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=20020528113938.B17353@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yodaiken@fsmlabs.com \
/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