> Is there a reason why Solaris emulation exists in three different places:
>
> Solaris/sparc64: Linus' kernel tree
> Solaris/sparc32: iBCS
> Solaris/x86: My development iBCS tree
>
> Now the final one is fair enough - I haven't really released it yet, but why
> are sparc32 and sparc64 kept separate?
>
> Is there a reason for the sparc64 version being integrated into the kernel but
> not sparc32? Would it be better to remove the sparc64 version and merge it
> instead with the iBCS code, to prevent duplication of effort?
Given that the sparc64 work is newer, why would we want to try to merge it
with the older iBCS stuff? The theoretical answer was that someone was
supposed to port the sparc64 work in the kernel to sparc32, and it's on my
list, but right now sparcbook stuff is at higher priority, and I'd be
happy for someone else to backport the sparc64 work to sparc32, but it
seems I'm the only one who cares who actually intends to work on the code.
-D
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/