Sparc64 doesn't care about you, and you shouldn't care about Sparc64

[Joe Nosay]

Is it possible to have the instruction sets moved from one architecture to
another? Would this require more registers? Since there are Open
Architectures, it should be possible to create a CPU with shared
instruction sets.

On Tue, Nov 17, 2015 at 4:27 AM, Mark Linimon <linimon at lonesome.com> wrote:

> On Tue, Nov 17, 2015 at 12:06:35AM -0700, Warner Losh wrote:
> > We don’t have a “king of the kernel” or “king of mips” or anything
> > like that.  We document that you send mail to mips@ when you don’t
> > know the right person to send.
>
> And I don't see why we should.  What would we gain from this administrative
> overhead?
>
> What we lose is: dealing with people who have the title not doing work,
> or people not having the title, doing the work, being irritated by not
> having the title.
>
> svn can, with a little effort, demonstrate who is looking after what.
>
> All I see is cost and no benefit.  This isn't an "org chart" kind of
> issue IMHO.
>
> In FreeBSD, why delegate responsibility to anyone other than those who
> take it by their own initiative?
>
> mcl
> _______________________________________________
> freebsd-sparc64 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
> To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe at freebsd.org"
>