linux-kernel - Re: Current status of rt2800usb and staging/rt2870

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: <efe7343f0910141126o54ea2e31r5327e0db06a8b7ec@mail.gmail.com>
Date:	Wed, 14 Oct 2009 19:26:49 +0100
From:	Luis Correia <luis.f.correia@...il.com>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Cc:	"John W. Linville" <linville@...driver.com>,
	Dan Williams <dcbw@...hat.com>,
	Ivo van Doorn <ivdoorn@...il.com>,
	Ozan Çağlayan <ozan@...dus.org.tr>,
	linux-wireless@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Current status of rt2800usb and staging/rt2870

On Wed, Oct 14, 2009 at 18:33, Bartlomiej Zolnierkiewicz
<bzolnier@...il.com> wrote:
> On Wednesday 14 October 2009 18:47:11 John W. Linville wrote:
>> On Wed, Oct 14, 2009 at 05:28:21PM +0200, Bartlomiej Zolnierkiewicz wrote:
>>
>> > I don't have a have a problem with it personally as long as people accept
>> > the competition..  but instead of working on _their_ projects they go around
>> > screaming at everybody who does not want to spin inside the great process
>> > designed by them..
>>
>> Please whine somewhere else.  You have the freedom to work in
>> drivers/staging all you want.  You do not have the power to force us to
>> like it -- especially in a case where you are diverting attention from
>> the community-maintained drivers instead of cooperating with them.
>
> Cooperating you say.
>
> rtl8187 -- before starting the work on rtl8187se I've pinged the maintainer
> to coordinate the effort and hear his opinion on how to progress..
>
> I've never heard back.
>
> rt2x00 -- I know that people have datasheets for some chipsets but I've
> never heard "How can we help you" etc. thing.

I have all the datasheets that Ralink supplied to us.
All of them are PRELIMINARY and most have errors, and therefore useless.

All useful information is in the crap drivers.

Ralink never provide better ones, and even our 'inside guy' says the
hardware documentation guys are always very late in providing more
info.

So, for me, it isn't lack of documentation that will ever help, believe me.

>
> All I've ever heard was _lies_ about current state of affairs or that
> my work is in the way.

AFAICS, your work was never questioned, at least by me.
You are welcome to work on rt2x00 , that was also never a problem. All
you would need is join in.

Ralink also said they were commited to present drivers for new chipset
to be mac80211 compliant, we're waiting on that.

So, you're really welcome to join the rt2x00 team Bartlomiej, the only
thing we ask is that all work should be done using the existing
rt2x00lib, rt2x00pci and rt2x00usb base 'libraries'.

Luis Correia,
rt2x00 project admin
--
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/