From: Bryan O'Donoghue <typedef@eircom.net>
To: bdonadt@arabellasw.com
Cc: 'linuxppc-embedded ' <linuxppc-embedded@ozlabs.org>
Subject: Re: MPC885 CryptoApi support.
Date: Tue, 29 Mar 2005 11:23:15 +0100 [thread overview]
Message-ID: <42492C93.2060906@eircom.net> (raw)
In-Reply-To: <NEBBIHDFOLIPIPJAKJAMMELCGEAA.bdonadt@arabellasw.com>
Bruce Donadt wrote:
> To answer the original question. The code is provided under a GPL license to
> companies that purchase a subscription to the Arabella Linux distribution.
> We have invested many man months in developing a commercial grade security
> solution for the PowerQUICCs and all of it has been written from the ground
> up. You are correct when you say that none of this is included in our "free"
> evaluation kit.
>
> Best Regards,
>
> Bruce
Don't mean to start an argument or unnecessarily continue a discussion,
Bruce, but, GPL=/the right to fork/.
If it is the case that you have provided a GPL-Arabella-Linux-Kernel, to
a customer and all the code is GPL compliant, then that customer, is
*free* to fork and/or redistribute that code, which seems like a bit of
an oxymoron, for a commercial offering !
--
Best
Bryan
next prev parent reply other threads:[~2005-03-29 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 15:33 MPC885 CryptoApi support Autran, Guillaume
2005-03-28 15:57 ` Bruce Donadt
2005-03-29 10:23 ` Bryan O'Donoghue [this message]
2005-03-29 10:43 ` Wolfgang Denk
2005-03-29 10:50 ` Eran Mann
-- strict thread matches above, loose matches on Subject: below --
2005-03-21 18:18 Guillaume Autran
2005-03-21 18:50 ` Eugene Surovegin
2005-03-21 19:01 ` Guillaume Autran
2005-03-21 19:03 ` Eugene Surovegin
2005-03-21 20:54 ` Bruce Donadt
2005-03-24 11:39 ` Marcelo Tosatti
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=42492C93.2060906@eircom.net \
--to=typedef@eircom.net \
--cc=bdonadt@arabellasw.com \
--cc=linuxppc-embedded@ozlabs.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.