From: Jeff Garzik <jgarzik@pobox.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Adrian Bunk <bunk@stusta.de>, Tim Tassonis <timtas@cubic.ch>,
linux-kernel@vger.kernel.org
Subject: Re: State of the Union: Wireless
Date: Sat, 14 Jan 2006 04:43:33 -0500 [thread overview]
Message-ID: <20060114094333.GA9510@havoc.gtf.org> (raw)
In-Reply-To: <20060111203731.GF2456@ucw.cz>
On Wed, Jan 11, 2006 at 08:37:32PM +0000, Pavel Machek wrote:
> Hi!
>
> > > 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
> > - people forced to use OSS drivers can't use applications only
> > supporting ALSA
>
> Well, it is different. Current ieee80211 stack is going to be
> maintained by Intel -- because they need it for their hw.
> And it will be very easy to find maintainer for the new stack...
>
> So we already have two-stack situation here.
No, ieee80211 has always been intended for use by all drivers.
Read the archives... there have been a few efforts to start merging
HostAP and ieee80211 code, and further efforts exist out of tree that
add softmac support.
Remember Linux's maxim: do what you must, and no more.
That implies that new users SHOULD update ieee80211 for their needs.
Jeff
next prev parent reply other threads:[~2006-01-14 9:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=20060114094333.GA9510@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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
all inboxes | Powered by JetHome®