From: hostmaster <hostmaster@ed-soft.at>
To: linux-kernel@vger.kernel.org
Subject: New Linux Development Model
Date: Sat, 05 Nov 2005 10:42:15 +0100 [thread overview]
Message-ID: <436C7E77.3080601@ed-soft.at> (raw)
Hi list.
I tought long about writting this mail. I'm a linux use since many years.
At the moment i'll getting more then frustrated about the actual develoment
model of the kernel. In the latest releases things where broken from release
to release.
For example take the ipw2200 driver.
From 2.6.12 -> 2.6.13 the header file ieee80211.h was incompatible with
driver.
Also transfer speed decreased dramaticaly.
From 2.6.13 -> 2.6.14 you included the ipw2200 driver. But in an too
old version
without WPA support. The external driver on ipw2200.sourceforge.net
seems not
to work with 2.6.14.
I had also several problems with some other not in kernel drivers.
I realy liked it to have the latest state of the art kernel, but at the
moment i'm forced
to use 2.6.12 ( ipw2200 -> WPA ).
I can't understand it why you have to break compatibility from kernel
release to kernel
release. Don't you think that this makes 3'rd party driver developers
frustrated?
It can't be an option for 3'rd party developers and users to check if
external drivers
still works with new kenrel releases.
From my point of view the actual linux kernel is far away from a stable
development
process.
cu
ED.
next reply other threads:[~2005-11-05 9:42 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-05 9:42 hostmaster [this message]
2005-11-05 10:29 ` New Linux Development Model Francois Romieu
2005-11-05 11:29 ` Jean Delvare
2005-11-05 13:19 ` Edgar Hucek
2005-11-05 13:44 ` Adrian Bunk
2005-11-05 13:47 ` Alistair John Strachan
2005-11-05 22:23 ` Mark Lord
2005-11-06 0:28 ` Alistair John Strachan
2005-11-05 14:34 ` Jesper Juhl
2005-11-05 14:48 ` Oliver Neukum
2005-11-05 14:56 ` Fawad Lateef
2005-11-05 15:28 ` Adrian Bunk
2005-11-06 10:52 ` jerome lacoste
2005-11-06 11:55 ` Edgar Hucek
2005-11-06 12:39 ` Adrian Bunk
2005-11-06 12:57 ` Bernd Petrovitsch
2005-11-06 17:38 ` Jean Delvare
[not found] ` <436DEEFC.4020301@ed-soft.at>
2005-11-06 13:43 ` jerome lacoste
2005-11-09 0:11 ` caszonyi
2005-11-09 0:23 ` Con Kolivas
2005-11-09 7:00 ` Diego Calleja
2005-11-09 12:30 ` jerome lacoste
2005-11-09 14:03 ` caszonyi
2005-11-09 15:45 ` Marcos Marado
2005-11-06 16:50 ` John Carlson
2005-11-06 18:17 ` Bernd Petrovitsch
2005-11-09 0:16 ` caszonyi
2005-11-06 15:22 ` Jim Nance
2005-11-06 16:55 ` John Carlson
-- strict thread matches above, loose matches on Subject: below --
2005-11-09 1:47 Ian Kumlien
2005-11-09 11:08 ` Marcos Marado
2005-11-09 11:30 ` Ian Kumlien
2005-11-09 12:03 ` Wed, 9 Nov 2005 13:03:07 +0100
2005-11-09 15:49 ` Ian Kumlien
2005-11-09 15:58 ` Al Viro
2005-11-09 16:32 ` Ian Kumlien
2005-11-09 12:37 ` Marcos Marado
2005-11-09 16:01 ` Ian Kumlien
2005-11-10 0:55 ` Alistair John Strachan
2005-11-10 15:10 ` Mark Lord
2005-11-10 19:29 ` Alistair John Strachan
2005-11-10 19:47 ` Ian Kumlien
2005-11-09 19:05 ` Bill Davidsen
2005-11-09 20:10 ` Marcos Marado
2005-11-10 0:57 ` Alistair John Strachan
2005-11-10 20:08 ` Bill Davidsen
2005-11-10 20:21 ` Alistair John Strachan
2005-11-12 13:45 ` Bill Davidsen
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=436C7E77.3080601@ed-soft.at \
--to=hostmaster@ed-soft.at \
--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