linux-kernel - Re: rt2x00: slow wifi with correct basic rate bitmap (was Re: stable? quality assurance?)

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]

Date:	Tue, 13 Jul 2010 21:18:36 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Alejandro Riveira Fernández <ariveira@...il.com>
CC:	Martin Steigerwald <Martin@...htvoll.de>,
	linux-kernel@...r.kernel.org,
	Johannes Berg <johannes@...solutions.net>,
	"John W. Linville" <linville@...driver.com>,
	linux-wireless@...r.kernel.org
Subject: Re: rt2x00: slow wifi with correct basic rate bitmap (was Re: stable?
 quality assurance?)

Alejandro Riveira Fernández wrote:
> El Tue, 13 Jul 2010 14:50:14 +0200
> Stefan Richter <stefanr@...6.in-berlin.de> escribió:
>> There were promises made in this thread?  Then I must have read a
>> different mailinglist or so.
> 
>  Ok no promises.
>  Maybe I read to much in to Mr Tso previous mail. My apologies
>  [quote]
>  > So I tend to use -rc3, -rc4, and -rc5 kernels on my laptops, and when
>  > I find bugs, I report them and I help fix them.  If more people did
>  > that, then the 2.6.X.0 releases would be more stable.  But kernel
>  > development is a volunteer effort, so it's up to the volunteers to
>  > test and fix bugs during the rc4, -rc5 and -rc6 time frame. 
>  
>  [...]
>  > [...]                         Linux may be a very good bargain (look
>  > at how much Oracle has increased its support contracts for Solaris!),
>  > but it's still not a free lunch.  At the end of the day, you get what
>  > you put into it.
> 
>   I tested the kernels i reported the bugs and helped (to the best of my
>   knowledge; I'm not a programmer) 
>   I got no result.

"You get what you put into it" probably did not mean "report a bug, get
it fixed, every time".  Often enough, kernel bugs or hardware quirks are
very hard to fix without direct access to affected hardware.

Here is how my involvement with Linux started:  I reported a bug but
nobody reacted.  I collected some more information, reported the bug
again, and it was immediately fixed by the driver authors.  From then on
I kept following driver development as a tester and answered user
questions.  A few years later, the driver authors all had left for other
projects but there were still bugs to tackle.  So I started to write and
submit bug fixes myself.  (I'm not a programmer either but by then I
already knew a lot about the subsystem.)
-- 
Stefan Richter
-=====-==-=- -=== -==-=
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/