From: Alejandro Bonilla <abonilla@linuxwireless.org>
To: Hubert Tonneau <hubert.tonneau@fullpliant.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 upgrade overall failure report
Date: Sat, 16 Apr 2005 12:59:50 -0500 [thread overview]
Message-ID: <42615296.8060607@linuxwireless.org> (raw)
In-Reply-To: <055FPDS12@server5.heliogroup.fr>
I usually never complain, or give negative motivation, but this is a
reality.
>Now, what's wrong with that ?
>Well, the fact is that new hardware is only supported by latest kernel,
>so at the end, you have to upgrade, and so you get more and more complexity
>whether you like it or not.
>As an example, for servers, 2.4 is still fine, but laptops already require 2.6
>
>
If it wouldn't be because my wifi card only works in 2.6 and cause the
speedstep support for my laptop, I would be using 2.4 kernels.
>As a result, the complexity versus stability compromise is less and less
>suited for most real life uses.
>
>Now the problem with the kernel complexity is:
>. ultimate implementation requires much more testing than simple good one (TCP
> sample)
>. it makes life harder for device drivers writers (tigon3 or fusion sample)
>
I have returned laptops to get them exchanged for one's that have a
e100/e1000 instead the tigon3. It's a shame that manufacturers still use
this chip on servers and laptops.
next prev parent reply other threads:[~2005-04-16 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 16:20 2.6 upgrade overall failure report Hubert Tonneau
2005-04-16 17:13 ` 2.6 upgrade overall failure report (me too) Mikael Abrahamsson
2005-04-16 17:59 ` Alejandro Bonilla [this message]
2005-04-29 9:17 ` 2.6 upgrade overall failure report Andrew Morton
2005-04-29 15:56 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2005-04-29 9:57 Hubert Tonneau
2005-05-02 15:31 Moore, Eric Dean
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=42615296.8060607@linuxwireless.org \
--to=abonilla@linuxwireless.org \
--cc=hubert.tonneau@fullpliant.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.