From: reinette chatre <reinette.chatre@intel.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [ipw3945-devel] [PATCH 3/8] iwl3945 : fix rate scaling
Date: Thu, 12 Mar 2009 10:50:46 -0700 [thread overview]
Message-ID: <1236880246.13699.17.camel@rc-desk> (raw)
In-Reply-To: <1236824994.7177.3.camel@maxim-laptop>
On Wed, 2009-03-11 at 19:29 -0700, Maxim Levitsky wrote:
> On Thu, 2009-03-12 at 03:29 +0200, Maxim Levitsky wrote:
> > On Wed, 2009-03-11 at 11:17 -0700, Reinette Chatre wrote:
> > > From: Abhijeet Kolekar <abhijeet.kolekar@intel.com>
> > >
> > > Patch fixes the bug 1900 at
> > > http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1900
> > >
> > > Issues:
> > > Throughput and success ratio calculations were not done properly.
> > > Number of retries were exceeding 16.
> >
> > ether.
> >
> > On the other omitting the 'disable_hw_scan=1' option (which appears to
> > work once again, since few days ago it broke s2disk with hung scan) -
>
> Ah , I remember now. The disable_hw_scan=0 breaks (!)
> the rfkill support.
Could you please provide more details about this issue? We are
interested in steps to reproduce and logs you may have.
Thanks
Reinette
next prev parent reply other threads:[~2009-03-12 17:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 18:17 [PATCH 0/8] iwlwifi driver updates 03/11/2009 Reinette Chatre
2009-03-11 18:17 ` [PATCH 1/8] iwl3945: fix sparse error Reinette Chatre
2009-03-11 18:17 ` [PATCH 2/8] iwl3945: use iwl_led structure Reinette Chatre
2009-03-11 18:17 ` [PATCH 3/8] iwl3945 : fix rate scaling Reinette Chatre
2009-03-11 18:17 ` [PATCH 4/8] iwl3945: use iwl_tx_cmd_complete Reinette Chatre
2009-03-11 18:17 ` [PATCH 5/8] iwl3945: unmap previously mapped memory Reinette Chatre
2009-03-11 18:17 ` [PATCH 6/8] iwlagn: fix warning when set WEP key Reinette Chatre
2009-03-11 18:18 ` [PATCH 7/8] iwlwifi: print contents of control register when error occurs Reinette Chatre
2009-03-11 18:18 ` [PATCH 8/8] iwlwifi: correct log level " Reinette Chatre
2009-03-12 1:29 ` [ipw3945-devel] [PATCH 3/8] iwl3945 : fix rate scaling Maxim Levitsky
2009-03-12 2:29 ` Maxim Levitsky
2009-03-12 17:50 ` reinette chatre [this message]
2009-03-12 21:21 ` Maxim Levitsky
2009-03-12 21:58 ` Helmut Schaa
2009-03-12 22:03 ` Maxim Levitsky
2009-03-12 23:58 ` Maxim Levitsky
2009-03-13 6:28 ` Helmut Schaa
2009-03-12 22:41 ` Abhijeet Kolekar
2009-03-12 23:56 ` Maxim Levitsky
2009-03-13 0:18 ` Maxim Levitsky
2009-03-13 20:29 ` [PATCH 1/8] iwl3945: fix sparse error Kalle Valo
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=1236880246.13699.17.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maximlevitsky@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;
as well as URLs for NNTP newsgroup(s).