netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: netdev@vger.kernel.org
Cc: linville@tuxdriver.com
Subject: [PATCH 0/10] rt2x00
Date: Sun, 27 Aug 2006 17:39:10 +0200	[thread overview]
Message-ID: <200608271739.10503.IvDoorn@gmail.com> (raw)

Hi,

Here is a new update for rt2x00.
After these patches rt2x00 seems to slowly become active.
Current problematic issues:

Solid association but high packet loss (rt2400pci)
Very short association duration (rt2500pci)
On big endian machines device doesn't wake up (rt2500usb)
Hard to start association, and association is very short (rt2500usb)
Solid association but no packet transfer (rt61pci)
Only lives rarely, doesn't seem to do much (rt73usb)

Anyway here is the patch series for wireless-dev.
Note these patches are against the current wireless-dev tree,
without the crc and rfkill patches since those have not been
applied to the tree yet since they are waiting for maintainer approval.
This will not cause conflicts with the patch, but could cause some fuzz warnings
later when all patches are applied.

Ivo

                 reply	other threads:[~2006-08-27 15:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200608271739.10503.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    /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).