cvs commit: src/lib/libpthread Makefile src/lib/libpthread/test
sigsuspend_d.c src/lib/libpthread/thread thr_cancel.c thr_concurrency.c
thr_nanosleep.c thr_private.h thr_sig.c thr_sigmask.c ...
julian at elischer.org
Fri Jul 18 17:32:12 PDT 2003
On Fri, 18 Jul 2003, David O'Brien wrote:
> Who are "the arches"? KSE is a new feature, so the responsibility is on
> the KSE developers to complete their implementation on all Tier-1
> platforms. I've offered Alpha boxes to all the KSE developers and have
> had zero takers... (same for i386 SMP boxes... but that's another story)
I dont know the alpha and having a box isn't going to help that.
I can "guide" soemone who DOES know it as to what the kernel
MD parts should do but I'm not in a position to code them.
They are pretty trivial to describe, but you need to know a lot about
the architecture in question to know how each function should be
I guess what I should do is produce a recipe as to what needs to be
added to to each architecture's MD files to 'complete' that
architecture. With that I think specialists in each architecture should
have little problem filling in the gaps.
More information about the cvs-all