From: Tim Tassonis <timtas@cubic.ch>
To: linux-kernel@vger.kernel.org
Subject: Re: State of the Union: Wireless
Date: Tue, 10 Jan 2006 17:17:35 +0100 [thread overview]
Message-ID: <43C3DE1F.9010807@cubic.ch> (raw)
In-Reply-To: <20060110141324.GJ3911@stusta.de>
>
> I won't try to speak for Linus (perhaps he'd like to pipe up at some point),
> but I think you're pulling that concept wayy out of context here.
>
> Quoting ManagementStyle:
>
>> Btw, another way to avoid a decision is to plaintively just whine "can't
>> we just do both?" and look pitiful. Trust me, it works. If it's not
>> clear which approach is better, they'll eventually figure it out. The
>> answer may end up being that both teams get so frustrated by the
>> situation that they just give up.
>
> Built into that paragraph, I think, is the assumption that you never 'do
> both'.
Well, we'd have to ask Linus about this one. I think it can be a good
idea to do both, if you're not sure which one is better.
>
> Also, referring to OSS/Alsa is just a great way to illustrate the problem with
> your idea. There is, today, finally a "dominant" solution, but how long did
> it take us to get there? By my count, a really long time! And along the way
> we've had to deal with all kinds of applications that just support the first
> and not the other. And it seems like far too many people still have just one
> foot in the door - take for instance the README files shipped with commercial
> game ports that advise using OSS at the first hint of trouble with Alsa.
A network device is way better abstracted by the operating system, so
compatibility issues are of much smaller concern.
> Is this what we want for wireless?
We wouldn't get it, see above.
next prev parent reply other threads:[~2006-01-10 16:17 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
2006-01-10 16:17 ` Tim Tassonis [this message]
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=43C3DE1F.9010807@cubic.ch \
--to=timtas@cubic.ch \
--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