From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: ath5k-devel <ath5k-devel@lists.ath5k.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Nick Kossifidis <mick@madwifi-project.org>
Subject: Re: [ath5k-devel] Thanks for TX power patch
Date: Fri, 13 Mar 2009 12:38:28 +0200 [thread overview]
Message-ID: <1236940708.4708.14.camel@maxim-laptop> (raw)
In-Reply-To: <1236895489.17849.3.camel@maxim-laptop>
On Fri, 2009-03-13 at 00:04 +0200, Maxim Levitsky wrote:
> On Thu, 2009-03-12 at 17:33 -0400, Bob Copeland wrote:
> > On Thu, Mar 12, 2009 at 5:32 PM, Bob Copeland <me@bobcopeland.com> wrote:
> > > On Thu, Mar 12, 2009 at 5:25 PM, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> > >> Just to be clear, I got oopses, and hangs after resume from disk by just
> > >> using compat-wireless-2009-03-10 _without_ Nick's patches.
> > >
> > > Interesting, I thought you said that, but I tried the same stuff on
> > > plain wireless testing and didn't have any problems.
> >
> > Oh, and you said compat-wireless -- can you try wireless-testing just
> > to make sure it's not some structure definition build conflict with
> > compat-wireless?
> >
>
> Will do, soon.
>
> Best regards,
> Maxim Levitsky
>
Just compiled and installed latest wireless-testing with Nick's patches,
and your patch.
System is rock solid, module reload/s2disk/s2ram/long transfers work
just fine.
(I tested against my laptop, and got 1.5 Mbytes/s in both directions.
which is maximum speed possible - yes I know that everything goes
through AP...)
Now my both wifi device are supported almost perfectly:
still small issues with rate control on iwl3945, and
not that great led on ath5k - both issues are pure software issues, and
when I have time I will look at improving led algorithm.
Big thanks,
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-03-13 10:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 23:39 Thanks for TX power patch Maxim Levitsky
2009-03-11 0:12 ` Nick Kossifidis
2009-03-11 8:15 ` Tulio Magno Quites Machado Filho
2009-03-12 14:14 ` Bob Copeland
2009-03-12 21:25 ` Maxim Levitsky
2009-03-12 21:32 ` [ath5k-devel] " Bob Copeland
2009-03-12 21:33 ` Bob Copeland
2009-03-12 22:04 ` Maxim Levitsky
2009-03-13 10:38 ` Maxim Levitsky [this message]
2009-03-13 18:23 ` Bob Copeland
2009-03-13 18:29 ` Nick Kossifidis
2009-03-13 19:06 ` Maxim Levitsky
2009-03-13 0:30 ` Bob Copeland
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=1236940708.4708.14.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=mick@madwifi-project.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