lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1248973862.22552.4.camel@johannes.local>
Date:	Thu, 30 Jul 2009 19:11:02 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Ivo van Doorn <ivdoorn@...il.com>
Cc:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	Luis Correia <luis.f.correia@...il.com>,
	Mike Galbraith <efault@....de>, linux-wireless@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: [wireless] rt2870sta BUGs on shutdown,
 2.6.30.2->git.today+git.wireless.today

On Thu, 2009-07-30 at 18:52 +0200, Ivo van Doorn wrote:

> [some text expressing his frustration]

This is exactly why I was against staging all the time. Now suddenly
"The Crap" seems like a viable alternative. WAKE UP PEOPLE. The code is
not useful. Just look at the code that Mike pasted into his email. That
alone should be enough to send cold shivers down your spine!

What staging has achieved here is giving the crap vendor code a
blessing, receiving it welcomingly and forgivingly instead of saying
"well screw you, go ahead and ship this to your users but don't ever say
you support Linux well" ... now even some hackers and just just "dumb
users" think that the crap in staging could possibly at some point
become useful code!

It won't. EVER. No matter _how_ much you clean it up, it will NEVER fit
into the code scheme that everything else wireless has adopted.

And, Bartlomiej, don't give me the straw-man argument of user support,
if all you cared about were users you could well have _distros_ ship the
crap. They don't want to, of course, support this, for good reason! As
long as the vendors don't wake up, and some people see The Crap as a
viable alternative, good hardware support will never become a reality.

Look what you've done, really! You've frustrated the only person (Ivo)
who cares about giving these devices _proper_ support to a point where
he's no longer really interested in it because he's always measured
against The Crap right away. And that's perfectly understandable!
Effectively, you're saying that while he may have done good work, you
don't care about it because it's not perfect. Mike at least was willing
to try rt2x00 and work with it.

And now you're coming out of the woods and claiming that The Crap
works?! When the thread started with how it crashed? Get real.

In the end, while the letters you typed into your email claim to say the
opposite, the message of your email is that nobody should care about
rt2x00 and that the vendor driver should remain the status quo. Well, in
that case, get lost, crawl into the staging list and at least don't
bother us with The Crap.

Such attitude is part of the problem, the other big part is that vendors
can now claim their hardware "has mainline Linux support (in the staging
area)" and nobody will be the wiser.

So how about you help work on it, or think about a solution instead?

johannes


Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ