linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: "Thomas Bächler" <thomas@archlinux.org>, linux-wireless@vger.kernel.org
Subject: Re: RaLink RT2500 802.11g Cardbus/mini-PCI
Date: Fri, 11 Apr 2008 00:07:41 +0200	[thread overview]
Message-ID: <47FE8FAD.9020802@archlinux.org> (raw)
In-Reply-To: <200804021932.26046.IvDoorn@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

Ivo van Doorn schrieb:
>>>> Does the above mean that the stock driver in 2.6.25 will still be slow?
>>> Most likely yes.
>>> Although I hear mixed reports, some say it depends on the rate selection
>>> algorithm, some claim rt2x00 in 2.6.24 is faster then wireless-testing and
>>> others claim the exact opposite.
>>> At the moment it is hard to tell, but I haven't collected data yet with specific
>>> information about the used rate selection module and exact data transfer
>>> numbers.
>>>
>>> Ivo
>>>
>> I rebuilt 2.6.25-rc8 (again) to use the 'simple' algorithm instead of 
>> the 'PID' algorithm by default. rt2500pci is still fast!
> 
> Good to hear. :)
> 
> Thanks for the test.
> 
> Ivo

Bad news again:

With 2.6.25-rc8, rt2500pci is fast. When I apply this patch:
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.25-rc8-git8.bz2
on top of rc8, then it is slow again. I can't make sense of it, maybe 
you can.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2008-04-10 22:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 21:41 RaLink RT2500 802.11g Cardbus/mini-PCI Felipe Maya
2008-03-31 22:10 ` Ivo van Doorn
2008-03-31 22:28   ` Felipe Maya
2008-04-01  8:51     ` Ivo Van Doorn
2008-04-01 22:11       ` TK
2008-04-02 11:19       ` Felipe Maya
2008-04-01 18:01   ` Thomas Bächler
2008-04-01 18:09     ` Ivo van Doorn
2008-04-02  9:13       ` Thomas Bächler
2008-04-02 10:21       ` Thomas Bächler
2008-04-02 17:32         ` Ivo van Doorn
2008-04-10 22:07           ` Thomas Bächler [this message]
2008-04-12 10:46             ` Ivo van Doorn
2008-04-12 17:54               ` Thomas Bächler
2008-04-13  7:41                 ` Johannes Berg
2008-04-13  8:07                   ` Johannes Berg
2008-04-13  8:31                     ` Thomas Bächler
2008-04-13 10:11                       ` Johannes Berg
2008-04-13 10:20                         ` Thomas Bächler
     [not found]                         ` <1ba2fa240804130936o21f08b50jd35658a495a66eb4@mail.gmail.com>
2008-04-13 17:42                           ` Johannes Berg
2008-04-14 11:39                       ` Ivo van Doorn
2008-04-14 17:37                         ` Thomas Bächler
2008-04-14 17:47                           ` Ivo van Doorn
     [not found] <20080402001213.7b879a73@localhost>
     [not found] ` <36899.201.36.161.238.1207134354.squirrel@mamao.cetuc.puc-rio.br>
2008-04-02 11:54   ` TK
2008-04-02 12:47     ` Ivo Van Doorn

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=47FE8FAD.9020802@archlinux.org \
    --to=thomas@archlinux.org \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@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).