mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: pomac@vapor.com
Cc: 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 00:55:58 +0000	[thread overview]
Message-ID: <200511100055.58322.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <1131552065.2413.90.camel@localhost>

On Wednesday 09 November 2005 16:01, Ian Kumlien wrote:
[snip]
> > I totally disagree. See: for those who don't crawl on lkml, don't
> > compile kernels or modules or stuff like that, they had two choices: be
> > without ipw2100 or ipw2200 or learn how to put the drivers in their
> > kernels. Now, with the stock kernel you have ipw* support, even if
> > limited for some uses. Most people will be happy with this version, but
> > yes, there's still work to be done. When there's a new version
> > considered stable it will get merged into the kernel. Until then, if you
> > want to ride the unstable horse, you'll have to patch it yourself into
> > the kernel.
>
> Since it has to be out of tree the way it is now, you don't patch or
> upgrade, you simply have to make it compile. And if you are happy with
> wlan driver that hardly does wep then you have some issues as well.

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!

> > If you want to simplify the process of building the unstable versios of
> > ipw* or if you think that the newer versions of ipw* should be
> > considered the new stable, or if you at some point disagree with ipw*
> > development model you should complain in ipw2100 mailing list at
> > http://lists.sourceforge.net/lists/listinfo/ipw2100-devel .
> > Kernel-related, the decision of supporting the latest stable is good and
> > justifiable.
>
> Thats why we have "experimental" drivers in the kernel?
>
> like, f.ex.:
> Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)
> New SysKonnect GigaEthernet support (EXPERIMENTAL)
>
> Or the protocols? (STCP, DCCP, etc)
>
> IF a unstable version of a driver is better for the user isn't it better
> to merge it as experimental instead of merging a old version that wreaks
> havock on users of newer kernels (and they will STILL run the unstable
> version on older kernels anyways).

I'm not sure what you mean by "wreaks havoc". There have been bugfixes, but 
they do not affect many general use-cases. Equally the WPA work really IS 
brand new.

The primary "havoc" I had when upgrading to 2.6.14 was finding the older 
firmware and co-installing it.

> Note: I use skge myself, so pointing out that they are experimental is
> in no way negative, i actually prefer it to the stable driver.

I really don't think this is your call. The driver maintainer can push 
whatever code he's most happy with for whatever reasons he likes. I'm 
confident that in time appropriate changes from 1.0.8 will make it into 
mainline.

Perhaps the only criticism here that is valid is that Intel haven't released a 
1.0.9 that builds against release quality (2.6.14) kernels _yet_. But at best 
that is a topic for another mailing list, not the LKML.

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2005-11-10  0:58 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- 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=200511100055.58322.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --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 \
    /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®