Skip to contentSkip to conversation

State of the Union: Wireless

DISCUSSION Robert Hancock 3 participants 3 messages Jan 6, 2006 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 6 lines · Jeff Garzik

* Release early, release often. Pushing from an external repository to the official kernel tree every few months creates more problems than it solves. Out-of-tree drivers fail to take advantage of recent kernel changes and coding practices, which leads to bugs and incompatibilities. Slow pushing leads to huge periodic updates, which are awful for debugging, testing, and general use.

I think this is an especially big problem, from a user's perspective at least.. I'm tired of patching up my laptop kernel with the latest ieee80211 and ipw2200 on every update because the mainline kernel contains an ancient version which is almost useless to me, and the Intel guys apparently don't feel like merging newer versions upstream until they get it perfect, or something..

I'm sure this would make it easier for other driver developers to work with the ieee80211 stack as well, if the current version wasn't maintained entirely out of tree for all intents and purposes..

The other complaint I have is that there's just too much breakage happening.. you update the wireless driver, then you have to update the wireless tools, then maybe WPA Supplicant stops working, etc. etc.

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
#2 lore raw

On Thu, 05 Jan 2006 23:39:07 -0600 Robert Hancock wrote:

btw, what happened to the netdev list copy??

thanx,
---
~Randy

#3 lore raw
In reply to Robert Hancock
Quoted 8 lines · Robert Hancock
Quoted 6 lines · Jeff Garzik

* Release early, release often. Pushing from an external repository to the official kernel tree every few months creates more problems than it solves. Out-of-tree drivers fail to take advantage of recent kernel changes and coding practices, which leads to bugs and incompatibilities. Slow pushing leads to huge periodic updates, which are awful for debugging, testing, and general use.

Quoted 6 lines

I think this is an especially big problem, from a user's perspective at least.. I'm tired of patching up my laptop kernel with the latest ieee80211 and ipw2200 on every update because the mainline kernel contains an ancient version which is almost useless to me, and the Intel guys apparently don't feel like merging newer versions upstream until they get it perfect, or something..

Robert, this was _one_ kernel, 2.6.14, and has since been rectified. Install 2.6.15 and be happy with your bleeding edge driver supporting firmware 2.4.

The last thing we need is Yet Another Flame War about the ipw2x00 drivers. They're some of the best drivers in the wireless tree.

Signature · 6 lines
Cheers,
Alistair.

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