From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Luis Correia <luis.f.correia@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Dan Williams" <dcbw@redhat.com>,
"Ivo van Doorn" <ivdoorn@gmail.com>,
"Ozan Çağlayan" <ozan@pardus.org.tr>,
linux-wireless@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current status of rt2800usb and staging/rt2870
Date: Wed, 14 Oct 2009 22:41:00 +0200 [thread overview]
Message-ID: <200910142241.01013.bzolnier@gmail.com> (raw)
In-Reply-To: <efe7343f0910141126o54ea2e31r5327e0db06a8b7ec@mail.gmail.com>
On Wednesday 14 October 2009 20:26:49 Luis Correia wrote:
> On Wed, Oct 14, 2009 at 18:33, Bartlomiej Zolnierkiewicz
> <bzolnier@gmail.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'.
Well, I will still continue to work on staging drivers:
- I need to understand vendor drivers better before doing any larger rt2x00
modifications. Cleaning it up is just an added value while reading it..
- I feel quite comfortable working on de-convoluting crappy code and has years
of experience of doing it.
- I'm still using Ralink hardware personally so I need something that provides
the basic usability _now_.
but since I'm also going to start adding some missing bits to rt2x00 soon
I would be happy to join rt2x00 project..
next prev parent reply other threads:[~2009-10-14 20:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 11:24 Current status of rt2800usb and staging/rt2870 Ozan Çağlayan
2009-10-13 15:52 ` Ivo van Doorn
2009-10-13 17:27 ` Bartlomiej Zolnierkiewicz
2009-10-13 18:17 ` Ivo van Doorn
2009-10-13 19:21 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:00 ` Ivo van Doorn
2009-10-13 20:42 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:15 ` Dan Williams
2009-10-13 21:57 ` Bartlomiej Zolnierkiewicz
2009-10-13 22:21 ` Luis Correia
2009-10-14 14:14 ` John W. Linville
2009-10-13 22:24 ` Dan Williams
2009-10-13 22:42 ` Bartlomiej Zolnierkiewicz
2009-10-14 14:15 ` John W. Linville
2009-10-14 1:58 ` Thomas Fjellstrom
2009-10-14 13:51 ` Ivo van Doorn
2009-10-14 14:09 ` John W. Linville
2009-10-14 14:52 ` Bartlomiej Zolnierkiewicz
2009-10-14 14:56 ` John W. Linville
2009-10-14 15:28 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:47 ` John W. Linville
2009-10-14 17:33 ` Bartlomiej Zolnierkiewicz
2009-10-14 18:26 ` Luis Correia
2009-10-14 20:41 ` Bartlomiej Zolnierkiewicz [this message]
2009-10-14 18:56 ` Ivo van Doorn
2009-10-14 20:10 ` Bartlomiej Zolnierkiewicz
2009-10-15 6:28 ` Gertjan van Wingerde
2009-10-15 9:47 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:55 ` Luis R. Rodriguez
2009-10-15 14:47 ` Bartlomiej Zolnierkiewicz
2009-10-15 19:06 ` Luis R. Rodriguez
2009-10-16 17:13 ` Bartlomiej Zolnierkiewicz
2009-10-14 1:52 ` Mike Galbraith
2009-10-13 16:44 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:41 ` Ozan Çağlayan
2009-10-13 20:44 ` Bartlomiej Zolnierkiewicz
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=200910142241.01013.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=dcbw@redhat.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=luis.f.correia@gmail.com \
--cc=ozan@pardus.org.tr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.