From: "Chris Hallinan" <challinan@gmail.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Bug 1623
Date: Tue, 11 Mar 2008 12:34:16 -0400 [thread overview]
Message-ID: <c4aed99f0803110934h1d92eff3hbedd62df61160122@mail.gmail.com> (raw)
In-Reply-To: <1ba2fa240803102317q6173e243nd7dff52fe83089f2@mail.gmail.com>
On Tue, Mar 11, 2008 at 2:17 AM, Tomas Winkler <tomasw@gmail.com> wrote:
> On Tue, Mar 11, 2008 at 1:50 AM, Chris Hallinan <challinan@gmail.com> wrote:
> > On Mon, Mar 10, 2008 at 11:05 AM, Tomas Winkler <tomasw@gmail.com> wrote:
> >
> > > On Mon, Mar 10, 2008 at 4:02 PM, Chris Hallinan <challinan@gmail.com> wrote:
> > > > http://bughost.org/bugzilla/show_bug.cgi?id=1623
> > > >
> > > > Anything else I can do to help move this along? I'd love to dive into
> > > > the code, I just need a little guidance! I've written and debugged a
> > > > few Linux drivers in my day...
> > > >
> > > > Any other testing you need, I'd be happy to assist.
> > > >
> > > > Thanks,
> > > >
> > > > Chris
> > >
> > > We've recently committed fixes to 4965 rate scaling can you try the
> > > latest version of wireless-testing kernel?
> > >
> > I was unable to get either 1.2.25 nor top-of-tree from git (iwlwifi)
> > to compile with wireless-testing kernel.
>
> I see, the point is that wireless-testing already contains latest
> iwlwifi driver much newer then 1.2.25. so no need for patching just
> compile the kernel.
OK, sorry for the confusion, iwl4965 was not enabled by default, and I
assumed it was not there.
I've completed the test, wireless-testing kernel from two days ago
does not resolve the slow wireless connection. I will update the bug
report with this data.
>
>
> > As another data point, it appears the iwl4965 operates at full speed
> > using a more up-to-date Wireless Access Point such as the
> > Cisco/Linksys WAP4400N.
>
> I'm not so familiar with the Linksys-B AP. Is it B-only AP?
> I suspect there is a problem in rate scaling and we are going beyond
> the CCK rates which B-only AP cannot hear.
> but this is only shutting to darkness, need to reproduce.
> I'm not sure if you have a sniffer but capture of traffic would be very useful.
It's an old Wireless-B unit, so I can only guess it's 'B' only. It is
a Linksys WAP11 Ver. 2.0
Firmware: v2.05, Aug. 04, 2003. Unfortunately, the hotels and coffee
shops around the country are filled with these units, and I travel for
a living, so I'm holding out hopes for a solution, and stand ready to
help in any way I can.
Again, I will update the bug report with this data.
Regards,
Chris
prev parent reply other threads:[~2008-03-11 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 14:02 Bug 1623 Chris Hallinan
2008-03-10 15:05 ` Tomas Winkler
2008-03-10 16:24 ` Chris Hallinan
2008-03-10 23:50 ` Chris Hallinan
2008-03-11 6:17 ` Tomas Winkler
2008-03-11 15:03 ` Luis R. Rodriguez
2008-03-11 15:13 ` Filippo Zangheri
2008-03-11 15:31 ` Tomas Winkler
2008-03-11 16:34 ` Chris Hallinan [this message]
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=c4aed99f0803110934h1d92eff3hbedd62df61160122@mail.gmail.com \
--to=challinan@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.com \
/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