From: Herbert Rosmanith <kernel@wildsau.enemy.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc-4.1.1 and kernel-2.4.32
Date: Wed, 21 Jun 2006 16:25:55 +0200 (MET DST) [thread overview]
Message-ID: <200606211425.k5LEPtY6012550@wildsau.enemy.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0606211615390.31302@yvahk01.tjqt.qr>
> In effect (mainline) no. Linux 2.2 and 2.0 won't be fixed for the same
> reason; called deep maintenance. 2.6 has been on the road since Dec 2003,
> that's over 2 years. Do away with the old stuff.
we are in the process of switching, which is not unproblematic. on
the other hand, we have to support existing installations as well.
by the way ... "switching is not unproblematic": I just had to examine
a notebook which had problems with our software: a
"toshiba portege m400". 2.4 seems to work so far, as does 2.6.16.
I also tried 2.6.17, but get a strange problem: it simply hangs
after writing "PCI: probing hardware" (or similar). A closer look
reveals that it hangs in drivers/pci/probe.c, in pci_read_bases. What's
exactly going on, I don't know...
this shows that sometimes the old stuff works better than the new
stuff ;-)
kind regards,
h.rosmanith
next prev parent reply other threads:[~2006-06-21 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 13:17 Herbert Rosmanith
2006-06-21 13:20 ` Herbert Rosmanith
2006-06-21 13:47 ` Michal Piotrowski
2006-06-21 14:18 ` Jan Engelhardt
2006-06-21 14:25 ` Herbert Rosmanith [this message]
2006-06-21 19:29 ` Alistair John Strachan
2006-06-21 19:33 ` Jesper Juhl
2006-06-21 14:11 Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200606211425.k5LEPtY6012550@wildsau.enemy.org \
--to=kernel@wildsau.enemy.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®