From: Tom Cooksey <thomas.cooksey@trolltech.com>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: linux-embedded mailing list <linux-embedded@vger.kernel.org>
Subject: Re: Getting physical addresses of mmap'd pages from userspace
Date: Wed, 15 Oct 2008 09:06:40 +0200 [thread overview]
Message-ID: <200810150906.41064.thomas.cooksey@trolltech.com> (raw)
In-Reply-To: <48F4BEFA.10801@billgatliff.com>
On Tuesday 14 October 2008 17:47:06 Bill Gatliff wrote:
> Tom Cooksey wrote:
>
> > <RANT>
> > What I don't understand is that I'm trying to do some pretty interesting & cool
> > stuff with their processors (of course I would say that!), which will probably
> > help them sell more units. Why then do they make it so difficult to work with
> > them? It feels like they're shooting themselves in the foot. Madness.
> > </RANT>
>
> Not to perpetuate this further, but I can't resist... :)
>
> That's because their product won't stand on its own; it needs vendor lock-in to
> be successful. There really isn't any other explanation for such behavior.
>
> Think like a biologist. If an organism does something, then the upside must be
> better then the downside of NOT doing that something, or the organism wouldn't
> waste scarce time and energy doing it--- no matter how ridiculous that something
> might be. Unusual markings, mating calls, mullet haircuts...
>
> One would think that in the world of high-technology, there would be a huge
> upside to making products easy to use, which would naturally require free
> availability of documentation and code (among other things). But vendors seem
> to work contrary to that objective, which must mean that there's an even bigger
> upside to NOT making a product easy to use.
>
> Put another way, their revenue stream depends on making your life as painful as
> possible, so that you won't want to risk repeating that pain by switching to a
> competitor's product. It's a "shock collar ^K^K^K electrically-enhanced
> training aid", so to speak, and we're the dogs. And not the
> chihuahua-in-Paris-Hilton's-purse kind of dogs, either.
>
> Here's more evidence to support my point: what exactly is the cost to release
> documentation without an NDA? About US$0, which is considerably less than the
> expense of executing an NDA. So why have the NDA? Because that expense must be
> an "investment" in something that nets a larger return to the vendor of the
> documents in question. What might that be? Hmmm....
I always assumed it's because releasing the source opens them up to patent
infringement law suits? Some companies are more paranoid than others.
next prev parent reply other threads:[~2008-10-15 7:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 16:15 Getting physical addresses of mmap'd pages from userspace Tom Cooksey
2008-10-10 16:37 ` Bart Van Assche
2008-10-10 19:12 ` Robert Schwebel
2008-10-13 6:33 ` Tom Cooksey
2008-10-13 7:00 ` Robert Schwebel
2008-10-13 7:20 ` Tom Cooksey
2008-10-13 7:28 ` Thomas Petazzoni
2008-10-13 7:31 ` Robert Schwebel
2008-10-13 12:50 ` Bill Gatliff
2008-10-13 13:23 ` Robert Schwebel
2008-10-13 15:58 ` George G. Davis
2008-10-13 16:09 ` Robert Schwebel
2008-10-14 6:36 ` Tom Cooksey
2008-10-14 15:47 ` Bill Gatliff
2008-10-15 7:06 ` Tom Cooksey [this message]
2008-10-15 8:30 ` James Chapman
2008-10-15 18:27 ` Robert Schwebel
2008-10-15 18:29 ` Bill Gatliff
2008-10-13 9:37 ` Gilad Ben-Yossef
[not found] ` <48F31155.6090603@codefidence.com>
2008-10-13 9:38 ` Tom Cooksey
2008-10-13 12:48 ` Bill Gatliff
2008-10-13 14:45 ` Tom Cooksey
2008-10-13 15:09 ` Daniel THOMPSON
2008-10-13 17:21 ` George G. Davis
2008-10-13 17:29 ` Chris
2008-10-14 6:46 ` Tom Cooksey
2008-10-14 7:31 ` Daniel J Laird
2008-10-14 9:03 ` Tom Cooksey
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=200810150906.41064.thomas.cooksey@trolltech.com \
--to=thomas.cooksey@trolltech.com \
--cc=bgat@billgatliff.com \
--cc=linux-embedded@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