From: "Tom \"spot\" Callaway" <tcallawa@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: Sun4c interrupt controller - Sun4d relevance
Date: Sun, 12 Aug 2007 19:27:24 +0000 [thread overview]
Message-ID: <1186946844.4243.56.camel@new-host-2> (raw)
In-Reply-To: <46BF2A25.9090900@netunix.com>
On Sun, 2007-08-12 at 20:23 +0100, Chris Newport wrote:
> Last Solaris support for sun4d was Solaris 2.8 so all of the code will
> be there in 2.6 somewhere. Maybe it is just a special case within sun4m
> with a few extra drivers, or maybe the code has not been released.
> The SS1000 is frustratingly similar to the SS20, most of the devices are
> common.
>
> ISTR that Sun4d was a joint venture with Cray, so some code might
> be encumbered. I have not seen code so I can only guess.
I hate to be a bother here, but aren't there some legal concerns with
looking at Solaris source code, then implementing code in Linux?
Even on OpenSolaris, there is a grey area as to whether one can legally
view CDDL licensed code, then reimplement it as GPL (CDDL is
GPL-Incompatible) for Linux... but on old Solaris, that code should be
proprietary, unless Sun opened it when I wasn't looking.
Mark, can you legally be doing this?
~spot
next prev parent reply other threads:[~2007-08-12 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 15:41 Sun4c interrupt controller - Sun4d relevance Chris Newport
2007-08-12 15:59 ` Blue Swirl
2007-08-12 19:01 ` Mark Fortescue
2007-08-12 19:23 ` Chris Newport
2007-08-12 19:27 ` Tom "spot" Callaway [this message]
2007-08-12 20:58 ` Mark Fortescue
2007-08-13 1:50 ` David Miller
2007-08-13 1:59 ` David Miller
2007-08-13 2:03 ` David Miller
2007-08-13 13:24 ` Chris Newport
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=1186946844.4243.56.camel@new-host-2 \
--to=tcallawa@redhat.com \
--cc=sparclinux@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 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.