public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Tim Tassonis <timtas@cubic.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: State of the Union: Wireless
Date: Tue, 10 Jan 2006 17:31:00 +0100	[thread overview]
Message-ID: <20060110163100.GM3911@stusta.de> (raw)
In-Reply-To: <43C3DBBE.3090001@cubic.ch>

On Tue, Jan 10, 2006 at 05:07:26PM +0100, Tim Tassonis wrote:
> Adrian Bunk wrote:
> >On Tue, Jan 10, 2006 at 02:34:00PM +0100, Tim Tassonis wrote:
> >>Like the OSS/Alsa or XFree3.x/XFree4.x situations.
> >
> >And OSS/ALSA is an example why this is not a good thing:
> >- OSS in the kernel is unmaintained
> 
> Because it is dead, yes...

And this is exactly what you predicted for one of the merged stacks.

>...
> >But if you have the possibility to choose which stack to use at the 
> >beginning (as in the wireless case), the only reasonable solution is to 
> >choose _one_ stack.
> 
> ... _if_ you have the possibility, yes. But you might end up having 
> chosen the wrong one. There is a reason why two stacks exist.

The decision was already in the past - there is one stack that is 
already merged.

The question is whether there is a different stack that is considered 
that much better that switching to this stack including converting all 
drivers is worth the effort.

In the short term, having different stacks with different features and 
deficites only creates confusion.

In the long term, different stacks in the kernel will be a maintenance 
nightmare.

> Tim

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-01-10 16:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 12:38 State of the Union: Wireless 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 [this message]
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
     [not found] <5rRp0-4X1-3@gated-at.bofh.it>
2006-01-06  5:39 ` Robert Hancock
2006-01-06  6:42   ` Randy.Dunlap
2006-01-06 10:26   ` Alistair John Strachan
  -- 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=20060110163100.GM3911@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timtas@cubic.ch \
    /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