From: "Thomas Bächler" <thomas@archlinux.org>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RaLink RT2500 802.11g Cardbus/mini-PCI
Date: Wed, 02 Apr 2008 11:13:03 +0200 [thread overview]
Message-ID: <47F34E1F.6030201@archlinux.org> (raw)
In-Reply-To: <200804012009.02448.IvDoorn@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1584 bytes --]
Ivo van Doorn schrieb:
> Hi,
>
>>>> Is the last kernel code working with RaLink RT2500 802.11g Cardbus/mini-PCI?
>>> With 'latest' do you mean:
>>> latest 2.6.25-rc kernel?
>>> latest wireless-testing git snapshot
>>> latest rt2x00 git snapshot
>>>
>>> The latter 2 should work fine, the first one has known issues
>>> but the state variates per person.
>> I was complaining about speed a while ago, so after reading this post, I
>> thought I should try again and tell you:
>>
>> The version in wireless-testing seems to work great, a test download
>> gave me 1.24MB/s, which is about the same speed I get with my (Intel
>> wireless) laptop. I am using rt2500pci.
>>
>> 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
>
Okay, I tried again with 2.6.25-rc8 from linux-2.6 git. Speed is still
great. However, with both wireless-testing and linux-2.6 I seem to be
using the 'pid' algorithm:
phy0: Selected rate control algorithm 'pid'
With 2.6.24 I seem to be using the 'simple' rate control algorithm. I
don't know how to switch rate control algorithms without rebuilding
though, so I can't test 'simple' with 2.6.25.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2008-04-02 9:30 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 [this message]
2008-04-02 10:21 ` Thomas Bächler
2008-04-02 17:32 ` Ivo van Doorn
2008-04-10 22:07 ` Thomas Bächler
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=47F34E1F.6030201@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).