From: Digby Tarvin <digbyt@acm.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SPARC Port of v3?
Date: Fri, 16 Jun 2000 15:40:02 +0100 [thread overview]
Message-ID: <200006161440.PAA09802@cthulhu.dircon.co.uk> (raw)
In-Reply-To: <200006161343.JAA22831@cse.psu.edu> from rob pike at "Jun 16, 2000 09:43:35 am"
> I was disappointed to find no sources for a Sparc kernel.
>
> We don't have any modern Sparcs around here, so the old Sparc
> kernel was not kept up to date; the only thing we have is five
> years old. More important, we negotiated with Sun back in 1994
> to be able to release those sources under the old license terms.
> We'd need to renegotiate to release them under the new terms,
> and that's always a lot more work than it seems it should be.
> (Releasing OS sources gives away details of the hardware.)
> Given that the sources are out of date and for obsolete hardware,
> it doesn't seem worthwhile. If someone can get permission from
> Sun and promises to update the kernel, I'll let them have the
> source.
>
I too would be disappointed to lose the ability to utilize my old
Sparc hardware. I had taken it for granted that that would be
there in the new release :-(
I take it the source you refer to here just the version I already have
with the 1995 release ?
Is there anything in there that is not already public knowledge
by virtue of the Sparc version of Linux or NetBSD? Or would support need to
be re-developed from scratch by someone who had not signed a
non-disclosure with Sun before you would be free to distribute?
Havn't had a chance to look at the source for the new release
yet (still have to get hold of a free PC with the right hardware so I can
do the cross compiling), but I was wondering how much the driver level
stuff has changed. Is there a lot of work involved in moving support
for an architecture/machine from 2nd and incorporating it into
the 3rd release system?
Regards,
DigbyT
--
Digby R. S. Tarvin digbyt@acm.org
http://www.cthulhu.dircon.co.uk
next prev parent reply other threads:[~2000-06-16 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-16 13:43 rob pike
2000-06-16 14:40 ` Digby Tarvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-16 20:30 rob pike
2000-06-16 15:07 rob pike
2000-06-16 20:03 ` Digby Tarvin
2000-06-16 11:12 Jean Mehat
2000-06-15 16:29 Stephen Wynne
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=200006161440.PAA09802@cthulhu.dircon.co.uk \
--to=digbyt@acm.org \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).