[Aurora-sparc-user] [Fwd: Re: sparc32 esp connected CDROM failures]
Tom 'spot' Callaway
tcallawa at redhat.com
Fri Mar 16 17:08:07 EDT 2007
Well folks, Dave lays out the law:
Do we want to keep supporting sparc32 systems? There is no current
upstream kernel maintainer for sparc32 (sparc64 is maintained by Dave
Miller).
Right now, all the other SPARC Linux distributions (except Debian and
Aurora) have dropped sparc32 support. Debian has dropped support for old
sparc32, only sun4m are supported now.
Rather than just doing it, I'd like to hear people's thoughts.
~spot
-------- Forwarded Message --------
From: David Miller <davem at davemloft.net>
To: tcallawa at redhat.com
Cc: sparclinux at vger.kernel.org
Subject: Re: sparc32 esp connected CDROM failures
Date: Fri, 16 Mar 2007 13:52:13 -0700 (PDT)
From: "Tom 'spot' Callaway" <tcallawa at redhat.com>
Date: Fri, 16 Mar 2007 14:47:00 -0500
> The ioctl error repeats once more in the sequence...but the CDROM seems
> to work ok, as compared to sparc32, where it refuses to work.
Unfortunately that puts the ball in your or someone else's court,
since I don't have any sparc32 systems and therefore any way to work
on sparc32 bugs.
Sorry.
Really, you should drop sparc32 support in Aurora if you want my
opinion. Then you can build glibc sparcv9 by default and make other
significant improvements to the userspace. I probably won't ever use
Aurora until you make this switch, the performance just from being
able to -mcpu=v8 -mtune=ultrasparc all of userspace is very noticable.
Making a distribution for a kernel platform that has no active
maintainer is beyond foolish, you'll always have bugs that nobody
is going to fix other than yourself and that doesn't scale and
will continually hold up the release.
More information about the Aurora-sparc-user
mailing list