> "Uwe" == Uwe Hermann <[EMAIL PROTECTED]> writes:
Uwe> OK, not being a SPARC expert myself, I'd still like to see a
Uwe> list of issues or bugs which are worth dropping a whole
Uwe> sub-architecture.
Well, if I remember correctly, it was the kernel that was the problem.
There is
Slightly like watching a group of boys poking a nearly dead dog.
On 23/07/07, Ben Finney <[EMAIL PROTECTED]> wrote:
Uwe Hermann <[EMAIL PROTECTED]> writes:
> On Tue, May 22, 2007 at 04:38:04PM +0200, Frans Pop wrote:
> > Do you really think this is a decision that was made lightly? The
> > pro
On Mon, Jul 23, 2007 at 02:39:10PM +0200, Uwe Hermann wrote:
> OK, not being a SPARC expert myself, I'd still like to see a list of
> issues or bugs which are worth dropping a whole sub-architecture.
>
> Maybe some of them don't even require a SPARC guru to fix them? Maybe
> some are "easy" enough
Uwe Hermann <[EMAIL PROTECTED]> writes:
> On Tue, May 22, 2007 at 04:38:04PM +0200, Frans Pop wrote:
> > Do you really think this is a decision that was made lightly? The
> > problem is, and that has been mentioned before, that *there is no
> > upstream maintainer* for sparc32. Unless some people
Uwe Hermann wrote:
Well, I just saw three or more sparc32 patches being committed to Linus'
git tree today or yesterday, so that may not be quite correct.
You are missing the point. Those patches were created by enthusiastic
users fixing the problems that they have experienced.
Until someo
On Tue, May 22, 2007 at 04:38:04PM +0200, Frans Pop wrote:
> Do you really think this is a decision that was made lightly?
> The problem is, and that has been mentioned before, that *there is no
> upstream maintainer* for sparc32. Unless some people step up and ensure
> that upstream issues _are_
Hi,
Frans Pop <[EMAIL PROTECTED]> writes:
> The problem is, and that has been mentioned before, that *there is no
> upstream maintainer* for sparc32. Unless some people step up and ensure
> that upstream issues _are_ fixed in a timely manner, sparc32 is
> effectively dead.
"Upstream" should r
Frans,
Thanks for that pointer. After trawling through some of the
mailing lists and searching for bug reports I found Robert Reif's
reply indicating this is related to drm and the fact that sparc does
not support cmpxcgh at the moment.
Still not sure how to exactly reproduce this, but I'll try t
Turbo Fredriksson dijo [Wed, May 23, 2007 at 12:07:01AM +0200]:
> Frans> Debian cannot afford to have a broken kernel for a release
> Frans> subarch for that period of time. Kernel development moves
> Frans> too fast for that.
>
> Do we really NEED (read: _require_) the 'latest and gre
On Wed, May 23, 2007 at 12:07:01AM +0200, Turbo Fredriksson wrote:
> If I knew anything about kernel interior and development, I'd be happy
> to step up, but...
Why don't you step up and learn then?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
> "Frans" == Frans Pop <[EMAIL PROTECTED]> writes:
Frans> Debian cannot afford to have a broken kernel for a release
Frans> subarch for that period of time. Kernel development moves
Frans> too fast for that.
Do we really NEED (read: _require_) the 'latest and greatest' (or whateve
elw <[EMAIL PROTECTED]> writes:
> It seems obvious that someone will *eventually* fix sparc32 support in
> the kernel upstream.
Why is that obvious? We were a huge SPARC shop and I don't think we have
any hardware left that can't run 64-bit SPARC code. I expect many sites
that were running SPAR
On Tuesday 22 May 2007 16:03, [EMAIL PROTECTED] wrote:
> > The main reason is the fact that sparc32 support is no longer being
> > maintained upstream for the kernel [2]. A result of that is that the
> > 2.6.21 kernel is currently broken, which forces the issue.
>
> It seems obvious that someone wi
The sparc32 port has been struggling for some time. Last month Jurij
Smakov, currently the most active Debian Sparc porter, raised the
question if support sparc32 should be dropped for Lenny [1].
The main reason is the fact that sparc32 support is no longer being
maintained upstream for the
Frans Pop wrote:
On Monday 21 May 2007 21:49, Martin Habets wrote:
FYI, 2.6.21 is rock solid on my SS20 here. Do you consider it broken
just because of some cdrom issues? Or is there more?
I don't have more details than this:
http://lists.debian.org/debian-kernel/2007/05/msg00305.html
On Monday 21 May 2007 21:49, Martin Habets wrote:
> FYI, 2.6.21 is rock solid on my SS20 here. Do you consider it broken
> just because of some cdrom issues? Or is there more?
I don't have more details than this:
http://lists.debian.org/debian-kernel/2007/05/msg00305.html
pgpfhbQ39fOPO.pgp
Descr
On Mon, May 21, 2007 at 12:00:24PM +0200, Frans Pop wrote:
> The sparc32 port has been struggling for some time. Last month Jurij
> Smakov, currently the most active Debian Sparc porter, raised the question
> if support sparc32 should be dropped for Lenny [1].
I agree with this intent, as I wrot
On Mon, May 21, 2007 at 07:44:44PM +0100, Mark Brown wrote:
> The plan is to continue the existing port, dropping support for 64 bit
> kernels and allowing use of SPARC v9 instructions rather than to do a
I, of course, mean *32* bit kernels there.
Sorry.
*sigh*
--
"You grabbed my hand and w
On Mon, May 21, 2007 at 09:58:00AM -0700, Joe Buck wrote:
> Fine, as long as you provide 32-bit as well as 64-bit userland. Otherwise
The plan is to continue the existing port, dropping support for 64 bit
kernels and allowing use of SPARC v9 instructions rather than to do a
new port with 64 bit
On Mon, May 21, 2007 at 09:58:00AM -0700, Joe Buck wrote:
> On Mon, May 21, 2007 at 12:00:24PM +0200, Frans Pop wrote:
> > The sparc32 port has been struggling for some time. Last month Jurij
> > Smakov, currently the most active Debian Sparc porter, raised the question
> > if support sparc32 sho
On Mon, May 21, 2007 at 12:00:24PM +0200, Frans Pop wrote:
> The sparc32 port has been struggling for some time. Last month Jurij
> Smakov, currently the most active Debian Sparc porter, raised the question
> if support sparc32 should be dropped for Lenny [1].
Fine, as long as you provide 32-bit
21 matches
Mail list logo
