Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Chris Hallinan" <challinan@gmail.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Bug 1623
Date: Mon, 10 Mar 2008 19:50:50 -0400	[thread overview]
Message-ID: <c4aed99f0803101650n69aaaac0n540f5acbc6dd554c@mail.gmail.com> (raw)
In-Reply-To: <1ba2fa240803100805o17d8239cm741891e5895dd07f@mail.gmail.com>

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.

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.

Given that input, is there somewhere else we could look?  I will
update the bug record with these findings.

-Chris

  parent reply	other threads:[~2008-03-10 23:50 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 [this message]
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

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=c4aed99f0803101650n69aaaac0n540f5acbc6dd554c@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