From: Mark Lord <lkml@rtr.ca>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: pomac@vapor.com, marado@isp.novis.pt,
Linux-kernel@vger.kernel.org, fawadlateef@gmail.com,
hostmaster@ed-soft.at, jerome.lacoste@gmail.com,
carlsj@yahoo.com
Subject: Re: New Linux Development Model
Date: Thu, 10 Nov 2005 10:10:43 -0500 [thread overview]
Message-ID: <437362F3.4060401@rtr.ca> (raw)
In-Reply-To: <200511100055.58322.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
>
> Eh? WEP seems to work here with different key sizes. I think most people
> should be satisfied with finally being able to use their wireless controller
> in ANY form on a Centrino laptop without having to find a driver!
Err.. there are lots of different APs out there,
and the in-kernel borken driver doesn't work for me
with several APs I need to access.
Not to mention that WEP doesn't provide any meaningful security,
whereas the out-of-tree driver even does WPA2 with ease.
The big problem for users, is that they used to be able to just go
and grab the *real* ipw2200 driver, and build/install it with a few
simple commands.
But because the kernel now contains all of this way-outdated
stuff for ieee80211 and ipw2200, there are tons of header file
conflicts and protocol mismatches when attempting to build/use
the real driver.
Sure, us kernel folk can cope with all of that (in theory,
though in practice I'm still stuck with 2.6.13 because I haven't
yet gotten working ipw2200 with 2.6.14, with *either* driver).
But things just got WAY more complicated for most users of ipw2200.
Sure, they can ignore us and just continue to run their old vendor
kernels. But this means they don't get up-to-date kernels with
bug fixes and security fixes. And more importantly to LKML,
we've now just cut off a potentially large crowd of kernel-testers.
Ugh. Ugly.
next prev parent reply other threads:[~2005-11-10 15:10 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 1:47 New Linux Development Model 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-11-05 9:42 hostmaster
2005-11-05 10:29 ` 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
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=437362F3.4060401@rtr.ca \
--to=lkml@rtr.ca \
--cc=Linux-kernel@vger.kernel.org \
--cc=carlsj@yahoo.com \
--cc=fawadlateef@gmail.com \
--cc=hostmaster@ed-soft.at \
--cc=jerome.lacoste@gmail.com \
--cc=marado@isp.novis.pt \
--cc=pomac@vapor.com \
--cc=s0348365@sms.ed.ac.uk \
/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