From: andrea.glorioso@binary-only.com
To: Nicolas Pitre <nico@cam.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Monta Vista software license terms
Date: Wed, 05 Feb 2003 19:13:20 +0100 [thread overview]
Message-ID: <87wukeegu7.fsf@topo.binary-only.priv> (raw)
In-Reply-To: <Pine.LNX.4.44.0302051247280.8496-100000@xanadu.home> (Nicolas Pitre's message of "Wed, 5 Feb 2003 12:57:49 -0500 (EST)")
Just a quick clarification before this thing explodes in another "ten
thousan messages" thread.
>>>>> "np" == Nicolas Pitre <nico@cam.org> writes:
np> On Wed, 5 Feb 2003 andrea.glorioso@binary-only.com wrote:
>> >>>>> "rl" == Robert Love <rml@mvista.com> writes:
>>
rl> Further, all of the source is available anyhow in various open
rl> source projects.
>> I failed to find any source for Montavista XIP implementation,
>> which they claim they have put on their "Consumer Electronics"
>> release.
np> Hey, it's one of my many duties to release this XIP code to
np> the community. In other words, Monta Vista do actually pay me
np> to give that source away.
That's wonderful (no kidding).
np> It's just not up to the cleanliness level I expect of
np> community source even if customers usually don't care, and I
np> didn't have time to clean it up yet. But if you really insist
np> I can give you a raw patch.
It would be quite interesting for me, sincerely. Feel free to send me
the patch if you can.
np> I find it quite saddening that a lot of people only care about
np> making up shit while the company in question is devoting a lot
np> of money in salary to hire kernel developers full time whose
np> work has always been merged to community trees so far.
As far as I'm concerned, I just wrote:
- that Montavista claims they implemented XIP as part of their
"Consumer Electronics Edition" package;
- that source code is included in Montavista preview kit, but that I
couldn't find any XIP reference in it;
- that probably XIP is a part of the CEE edition but *not* of the
preview kit, hence the lack of source code for that specific part in
the ISO I downloaded; incidentally, that also means that right now I'm
not entitled to have source code for Montavista XIP implementation
(and I stated that clearly);
I personally don't have anything against Montavista, and I think
they're doing a good work (I know that you have to balance between
distributing source code and having your old-minded customers run away
in fear). I still think that having an encrypted ISO image is pure
brain damage, because it doesn't buy Montavista anything as far as I
can tell and it just slows down casual observers - which, by the way,
are the kind of people Montavista is supposed to attract. :)
Let's straighten out this issue. Maybe a public development tree of
Montavista kernels, with a big red flag saying "don't use this on
production systems" would be enough.
Best regards,
--
Andrea Glorioso andrea.glorioso@binary-only.com
Binary Only http://www.binary-only.com/
Via A. Zanolini, 7/b Tel: +39-348.921.43.79
40126 Bologna Fax: +39-051-930.31.133
next prev parent reply other threads:[~2003-02-05 18:05 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 11:58 Monta Vista software license terms Nilmoni Deb
2003-02-05 17:04 ` Disconnect
2003-02-05 17:25 ` Christoph Hellwig
2003-02-05 17:10 ` Robert Love
2003-02-05 17:18 ` Nilmoni Deb
2003-02-05 17:23 ` Robert Love
2003-02-05 17:36 ` andrea.glorioso
2003-02-05 17:57 ` Nicolas Pitre
2003-02-05 18:13 ` andrea.glorioso [this message]
2003-02-05 18:15 ` Christoph Hellwig
2003-02-05 18:24 ` Steven Dake
2003-02-05 18:28 ` Christoph Hellwig
2003-02-05 19:41 ` Alan Cox
2003-02-05 18:47 ` Christoph Hellwig
2003-02-05 18:52 ` Steven Dake
2003-02-05 18:31 ` Nicolas Pitre
2003-02-05 18:34 ` Christoph Hellwig
2003-02-05 18:41 ` Nicolas Pitre
2003-02-05 18:42 ` Christoph Hellwig
2003-02-05 19:00 ` Nicolas Pitre
2003-02-05 18:51 ` Ben Greear
2003-02-05 18:54 ` Dana Lacoste
2003-02-05 18:56 ` Christoph Hellwig
2003-02-05 19:25 ` Hugo Mills
2003-02-06 8:08 ` Andre Hedrick
2003-02-05 18:44 ` Nilmoni Deb
2003-02-05 17:16 ` Daniel Jacobowitz
2003-02-05 17:38 ` andrea.glorioso
2003-02-05 17:54 ` Christoph Hellwig
2003-02-05 18:04 ` andrea.glorioso
2003-02-06 1:11 ` jeff millar
2003-02-06 2:19 ` James Buchanan
2003-02-06 9:12 ` Andre Hedrick
2003-02-06 14:37 ` Alan Cox
2003-02-06 18:41 ` Valdis.Kletnieks
2003-02-06 19:14 ` Charles Cazabon
2003-02-06 20:36 ` Andre Hedrick
2003-02-10 7:18 ` Oliver Xymoron
2003-02-10 7:24 ` Christoph Hellwig
2003-02-10 13:24 ` Alan Cox
2003-02-10 17:42 ` Oliver Xymoron
2003-02-10 21:33 ` David Schwartz
2003-02-11 7:42 ` Horst von Brand
2003-02-11 19:39 ` David Schwartz
2003-02-11 20:42 ` Horst von Brand
2003-02-11 22:11 ` David Schwartz
2003-02-12 8:00 ` Horst von Brand
2003-02-12 13:26 ` Mark Hounschell
2003-02-12 15:32 ` Chris Friesen
2003-02-12 20:18 ` David Schwartz
2003-02-13 2:21 ` Jamie Lokier
2003-02-13 2:41 ` David Schwartz
2003-02-13 3:01 ` Jamie Lokier
2003-02-12 3:25 ` Derek Fawcus
2003-02-12 4:13 ` David Schwartz
2003-02-05 18:47 ` Nilmoni Deb
2003-02-05 17:17 ` Christoph Hellwig
2003-02-05 18:17 ` Nicolas Pitre
2003-02-05 18:20 ` Christoph Hellwig
2003-02-05 18:33 ` Nicolas Pitre
2003-02-05 18:40 ` Russell King
2003-02-06 11:31 ` Alex Bennee
2003-02-05 17:28 ` Chris Friesen
2003-02-05 17:31 ` Russell King
2003-02-05 19:15 ` Alan Cox
2003-02-05 19:02 ` Nilmoni Deb
2003-02-05 19:12 ` Daniel Jacobowitz
2003-02-05 21:11 ` Nilmoni Deb
2003-02-06 23:06 ` Bill Davidsen
2003-02-06 23:59 ` Nilmoni Deb
2003-02-09 14:52 ` Bill Davidsen
2003-02-09 16:50 ` Nilmoni Deb
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 19:11 Dan Kegel
2003-02-06 20:38 ` Andre Hedrick
2003-02-07 17:28 ` Dan Kegel
2003-02-11 22:27 Larry McVoy
[not found] <20030212201840.AAA15967%shell.webmaster.com@whenever>
2003-02-12 20:46 ` Valdis.Kletnieks
2003-02-12 21:30 ` David Schwartz
2003-02-12 21:41 ` Derek Fawcus
[not found] <20030212213022.AAA17490%shell.webmaster.com@whenever>
2003-02-12 21:43 ` Valdis.Kletnieks
2003-02-12 22:31 ` David Schwartz
2003-02-12 23:04 ` Daniel Forrest
2003-02-12 23:28 ` David Schwartz
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=87wukeegu7.fsf@topo.binary-only.priv \
--to=andrea.glorioso@binary-only.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.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 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.