From: "C.Newport" <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: sparc32 status
Date: Tue, 13 Jul 2004 20:00:07 +0000 [thread overview]
Message-ID: <200407132100.07918.crn@netunix.com> (raw)
In-Reply-To: <20040713160257.GA8148@foobazco.org>
On Tuesday 13 July 2004 5:02 pm, Keith M Wesolowski wrote:
> Due to a conflict of interest, I'll no longer be maintaining the
> sparc32 tree. Although I hope there will soon be an announcement of a
> new maintainer, in the interim please direct all patches and bug
> reports to the list.
> -- spot's sun4 patch
(see below)
> -- sun4d ranges fixup is hosed, see sbus.c:sbus_bus_ranges_init:
>
> /*
> * XXX This functions appears to be a distorted version of
> * prom_sbus_ranges_init(), with all sun4d stuff cut away.
> * Ask DaveM what is going on here, how is sun4d supposed to work... XXX
> */
I tracked down a man in Sun who designed this stuff and gave his contact info
to Keith. Sun4D should now be fixable.
> ... blow away all of the a.out build support cruft.
> There is zero use for any of this ancient crap anymore.
>
> This means C_SYMBOL() et al. may die as well.
>
> I had been meaning to do this for years.
>
> ** DONE
ISTM that this effectively blows Sun4 support out of the water.
Sun4 has not worked in a long while - Decision time ?.
Do we need Sun4 support ? - I have a 4/110 here tested with SunOS4.1.4
if someone would like to make the effort.
Add to list :- fc.c, fcal.c, pluto.c Needs updating to new SCSI API.
Most sun4d machines came with fc and pluto storage so they are
rather cramped for disk space without this.
next prev parent reply other threads:[~2004-07-13 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 16:02 sparc32 status Keith M Wesolowski
2004-07-13 18:56 ` Jan-Benedict Glaw
2004-07-13 18:58 ` Jan-Benedict Glaw
2004-07-13 20:00 ` C.Newport [this message]
2004-07-13 20:41 ` Keith M Wesolowski
2004-07-13 22:38 ` C.Newport
2004-07-23 21:50 ` Patrick Finnegan
2004-07-24 1:16 ` C.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=200407132100.07918.crn@netunix.com \
--to=crn@netunix.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.