From: Heitzso <heitzso@growthmodels.com>
To: sparclinux@vger.kernel.org
Subject: Re: [gentoo-sparc] ss20/ross/smp
Date: Fri, 06 May 2005 12:14:51 +0000 [thread overview]
Message-ID: <427B5FBB.1090704@growthmodels.com> (raw)
In-Reply-To: <4279EFEB.2070705@growthmodels.com>
Keith M Wesolowski wrote:
>In the year-plus since you first posted this you could have read, at a
>leisurely pace, the entire sparcv8 manual five times and the Linux
>smp4m implementation twenty. And if you had, you would be able to fix
>the problem instead of testing someone else's nonexistent fixes.
>These machines cost, what, ten bucks now? I guarantee you the
>limiting factor isn't testing resources.
>
>If you want this port to live, get hacking. If you get stuck, there
>are people here who can and often will answer your questions.
>Otherwise it's not much use posting periodically to remind people that
>you'd like it fixed but aren't willing to do any of the work needed to
>make that happen.
>
>
>
If someone could point to a couple of the broken places
that need work for sparc32 smp to function I'll look at them.
Does someone maintain a task list for sparc32 SMP?
I.e. a list of code blocks that need to be cleaned up in order
for sparc32 SMP to work?
Wouldn't this be good for the ultralinux site to manage?
Is that possible?
Thanks
next prev parent reply other threads:[~2005-05-06 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 10:05 ss20/ross/smp Heitzso
2005-05-05 12:15 ` ss20/ross/smp Ulrich Teichert
2005-05-05 12:53 ` ss20/ross/smp Heitzso
2005-05-05 13:08 ` ss20/ross/smp Stephen P. Becker
2005-05-05 13:22 ` ss20/ross/smp Ulrich Teichert
2005-05-05 14:50 ` ss20/ross/smp Heitzso
2005-05-05 18:04 ` ss20/ross/smp Ulrich Teichert
2005-05-06 0:42 ` [gentoo-sparc] ss20/ross/smp Keith M Wesolowski
2005-05-06 12:14 ` Heitzso [this message]
2005-05-06 14:50 ` Bob Breuer
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=427B5FBB.1090704@growthmodels.com \
--to=heitzso@growthmodels.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.