public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: State of the Union: Wireless
Date: Thu, 05 Jan 2006 23:39:07 -0600	[thread overview]
Message-ID: <43BE027B.4010806@shaw.ca> (raw)
In-Reply-To: <5rRp0-4X1-3@gated-at.bofh.it>

Jeff Garzik wrote:
> * 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.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-01-06  5:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5rRp0-4X1-3@gated-at.bofh.it>
2006-01-06  5:39 ` Robert Hancock [this message]
2006-01-06  6:42   ` State of the Union: Wireless Randy.Dunlap
2006-01-06 10:26   ` Alistair John Strachan
2006-01-10 12:38 Tim Tassonis
2006-01-10 12:53 ` Adrian Bunk
2006-01-10 13:34   ` Tim Tassonis
2006-01-10 14:13     ` Adrian Bunk
2006-01-10 16:07       ` Tim Tassonis
2006-01-10 16:31         ` Adrian Bunk
2006-01-10 16:17       ` Tim Tassonis
2006-01-11 20:37       ` Pavel Machek
2006-01-14  9:43         ` Jeff Garzik
2006-01-10 14:16 ` Chase Venters
     [not found] ` <mailman.1136898727.7233.linux-kernel2news@redhat.com>
2006-01-11  0:03   ` Pete Zaitcev
2006-01-11  0:29     ` Adrian Bunk
     [not found] <1136541243.4037.18.camel@localhost>
2006-01-06 11:00 ` [Bcm43xx-dev] [Fwd: State of the Union: Wireless] Michael Buesch
2006-01-06 16:04   ` State of the Union: Wireless Mike Kershaw
  -- strict thread matches above, loose matches on Subject: below --
2006-01-06  4:22 Jeff Garzik
2006-01-06 11:31 ` Johannes Berg
2006-01-06 11:46   ` Dominik Brodowski
2006-01-06 12:26     ` Johannes Berg
2006-01-06 12:48     ` Stefan Rompf
2006-01-06 12:53       ` Johannes Berg
2006-01-07 14:49   ` Denis Vlasenko
2006-01-10 13:18     ` Johannes Berg
2006-01-10  6:39 ` Denis Vlasenko
2006-01-10  8:36   ` Chase Venters

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=43BE027B.4010806@shaw.ca \
    --to=hancockr@shaw.ca \
    --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