From: Jens Axboe <jens.axboe@oracle.com>
To: linux-wireless@vger.kernel.org, ipw3945-devel@lists.sourceforge.net
Subject: Rate problems with iwl3945
Date: Thu, 18 Oct 2007 21:11:03 +0200 [thread overview]
Message-ID: <20071018191102.GI10674@kernel.dk> (raw)
Hi,
I wrote yesterday about my peering issues with this driver. After
getting the hint that iwlist scan would make it associate, I got that
working.
Copying some files I noticed it was slow, though. iwconfig reveals that
it's only running at 5.5Mb/s and indeed I only get around 650-700kb/sec
copying data. I tried to force it to 54M, but no matter what setting I
try with iwconfig rate, it stays at 5.5 and the performance stinks. With
ipw3945 I always got around ~3mb/s scp'ing data.
With the risk of sounding rude, is this driver expected to be of
production quality? It doesn't link, performance is bad. Am I better off
sticking to ipw3945 still? Are there patches out there I can try? Who
maintains this driver?
--
Jens Axboe
next reply other threads:[~2007-10-18 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 19:11 Jens Axboe [this message]
2007-10-18 19:29 ` Rate problems with iwl3945 Johannes Berg
2007-10-18 19:36 ` Jens Axboe
2007-10-18 19:41 ` Jens Axboe
2007-10-18 19:43 ` Jens Axboe
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=20071018191102.GI10674@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--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).