From: "C.Newport" <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: sparc32 status
Date: Tue, 13 Jul 2004 22:38:34 +0000 [thread overview]
Message-ID: <200407132338.34377.crn@netunix.com> (raw)
In-Reply-To: <20040713160257.GA8148@foobazco.org>
On Tuesday 13 July 2004 9:41 pm, Keith M Wesolowski wrote:
> > I tracked down a man in Sun who designed this stuff and gave his contact
> > info to Keith. Sun4D should now be fixable.
>
> I'm sure he can help, especially with SMP, but most of the breakage is
> Linux-specific and has little to do with lack of hardware knowledge.
> The above example points out code that worked in 2.2 and has since
> been broken. Under the circumstances, I can only assume the reason I
> haven't gotten a patch for this is that nobody cares.
Firstly, thanks for your effort so far, it is appreciated.
Sun4d is not a question of "nobody cares", the point is that without SMP it
is rather pointless. AIUI, SMP has never worked because nobody knew how to
initialise the bus handling correctly due to a lack of documentation.
This is why I tracked down the man in Sun who knows how it works.
Once the bus handling issues are understood the rest should be almost
identical to Sun4m.
These are really nice machines when filled with processors and memory.
Under 2.2 with only one processor it is a power-hogging boat anchor.
With 6 processors and 1.5Gb my 1000E is almost as fast as a 4 processor
E450 running Solaris 8, and uses about the same amount of power.
BTW there is an E10k on EBay UK for 2500UKP if someone would like it for
testing. Oldest model with only 2 system boards and 6x250MHz processors, but
that is good enough for testing and training.
next prev parent reply other threads:[~2004-07-13 22:38 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
2004-07-13 20:41 ` Keith M Wesolowski
2004-07-13 22:38 ` C.Newport [this message]
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=200407132338.34377.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.