From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Stefan Bader <stefan.bader@canonical.com>,
Manoj Iyer <manoj.iyer@canonical.com>,
kernel-team@lists.ubuntu.com,
"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: [KARMIC] review these for rt2x00 (adds rt2800pci)
Date: Fri, 17 Jul 2009 18:36:04 +0200 [thread overview]
Message-ID: <200907171836.04947.IvDoorn@gmail.com> (raw)
In-Reply-To: <43e72e890907170900r401a0b46tc56736f88d4436a2@mail.gmail.com>
On Friday 17 July 2009, Luis R. Rodriguez wrote:
> On Fri, Jul 17, 2009 at 1:00 AM, Stefan Bader<stefan.bader@canonical.com> wrote:
> > Ivo Van Doorn wrote:
> >>
> >> On Fri, Jul 17, 2009 at 1:15 AM, Luis R. Rodriguez<mcgrof@gmail.com>
> >> wrote:
> >>>
> >>> On Thu, Jul 16, 2009 at 9:56 AM, Stefan Bader<stefan.bader@canonical.com>
> >>> wrote:
> >>>>
> >>>> At least this seems to be material for 3 or 4 patches
> >>>> - adapt the rfkill stuff
> >>>> - some documentation update
> >>>> - add the new pci version of the 2800 (with that rt2x00soc lib
> >>>> which might be another patch)
> >>>> - and some fixes...
> >>>
> >>> Not only that but this driver is not yet merged upstream, there should
> >>> be a good reason for that.
> >>>
> >>> Ivo, what's the status on rt2800pci? Some users have been asking about
> >>> it.
> >>
> >> The status is that it is not functioning correctly, during boot it
> >> will print out
> >> tons of errors about the device not being ready, and afterward it cannot
> >> scan,
> >> connect or do anything useful.
> >>
> >> And I think those problems can be considered enough reasons for not
> >> merging
> >> the driver upstream yet. ;)
> >>
> >> Ivo
> >
> > I would say so. :) Assuming there is a bit of truth in those claims of that
> > tarball working better than the current kernel code, we might take away all
> > the new driver bloat and see what remains (which might be the part Ivo has
> > anyways in wireless testing...)
>
> Its not part of wireless-testing.
Well any patches in rt2x00.git which I have not send to linux-wireless yet
should _not_ be merged to anywhere since they are often incomplete,
incorrect or plain broken.
Ivo
next prev parent reply other threads:[~2009-07-17 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 23:15 [KARMIC] review these for rt2x00 (adds rt2800pci) Luis R. Rodriguez
2009-07-17 7:11 ` Ivo Van Doorn
2009-07-17 8:00 ` Stefan Bader
2009-07-17 16:00 ` Luis R. Rodriguez
2009-07-17 16:36 ` Ivo van Doorn [this message]
2009-07-17 16:53 ` Luis R. Rodriguez
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=200907171836.04947.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-wireless@vger.kernel.org \
--cc=manoj.iyer@canonical.com \
--cc=mcgrof@gmail.com \
--cc=stefan.bader@canonical.com \
/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;
as well as URLs for NNTP newsgroup(s).