All of lore.kernel.org
 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>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	"Vladimir Koutny" <vlado@ksp.sk>
Subject: Re: RaLink RT2500 802.11g Cardbus/mini-PCI
Date: Mon, 14 Apr 2008 19:37:00 +0200	[thread overview]
Message-ID: <4803963C.2000101@archlinux.org> (raw)
In-Reply-To: <200804141339.45645.IvDoorn@gmail.com>

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

Ivo van Doorn schrieb:
>>> No, wait, I'm confused, the original patch is correct. As far as I can
>>> tell, the code there is correct. The bug in that code was actually
>>> introduced by me based on the wrong thinking I just did again.
>> I figured as much from the original commit message. So rt2500pci works 
>> properly when the use_short_preamble has the wrong value, and breaks 
>> when it has the right one.
>> By the way, 2.6.25-rc8 was the first time that rt2500pci was ever fast 
>> enough to be usable at all for me, so the bug you introduced seemed to 
>> be the fix for my speed problems (which is odd). My guess is that 
>> rt2500pci treats use_short_preamble wrong.
> 
> Could you test this with the below patch?
> This enables short_preamble for all rt2x00 drivers regardless of what mac80211 issues.

What tree is this against? It doesn't apply to linux-2.6.git 
(2.6.25-rc9), which was the one I was talking about all the time. I did 
not test the wireless-testing or rt2x00 tree.



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

  reply	other threads:[~2008-04-14 17:37 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
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 [this message]
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=4803963C.2000101@archlinux.org \
    --to=thomas@archlinux.org \
    --cc=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=vlado@ksp.sk \
    /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.