From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwl3945 regression: associates but no data is transfered
Date: Thu, 22 Jan 2009 13:34:48 -0500 [thread overview]
Message-ID: <20090122183448.GC3646@tuxdriver.com> (raw)
In-Reply-To: <87priffb95.fsf@litku.valot.fi>
On Thu, Jan 22, 2009 at 08:26:14PM +0200, Kalle Valo wrote:
> Hello,
>
> I upgraded to the latest wireless-testing and my iwl3945 is now
> broken. It can associate but no data is transfered after that. Tried
> with open and wep modes. With dhcp I cannot get ip and with static ip
> ping to the gateway doesn't work.
>
> Any hints?
Lots of iwlwifi stuff merged yesterday...
Chatre, Reinette (1):
iwl3945: add debugging for wrong command queue
Helmut Schaa (2):
iwl3945: fix some warnings when compiled without debug
iwlagn: fix hw-rfkill while the interface is down
Jay Sternberg (4):
iwlwifi: correct Kconfig to prevent following entries from not indenting
iwlwifi: remove static from 5000 structures
iwlwifi: add recognition of Intel WiFi Link 6000 and 6050 Series
iwlwifi: add recognition of Intel WiFi Link 100 Series
Reinette Chatre (1):
iwlwifi: return NETDEV_TX_OK from _tx ops
Samuel Ortiz (3):
iwl3945: Use iwl_txq_update_write_ptr
iwlwifi: Add TFD library operations
iwl3945: Use iwl-hcmd host command routines
Winkler, Tomas (6):
iwlwifi: make iwl-power.c more readable
iwlwifi: fix iwl_mac_set_key and iwl3945_mac_set_key
iwlwifi: kill iwl3945_scan_cancel and iwl3945_scan_cancel_timeout
iwlwifi: kill scan39
iwlwifi: remove unused or twice defined members in iwl_priv
iwlwifi: eliminate power_data_39.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-01-22 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 18:26 iwl3945 regression: associates but no data is transfered Kalle Valo
2009-01-22 18:34 ` John W. Linville [this message]
2009-01-22 23:41 ` samuel
2009-01-22 23:55 ` Larry Finger
2009-01-23 0:42 ` samuel
2009-01-23 1:06 ` Larry Finger
2009-01-23 5:32 ` Harvey Harrison
2009-01-23 0:07 ` Sedat Dilek
2009-01-23 1:20 ` Sedat Dilek
2009-01-22 19:41 ` Sedat Dilek
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=20090122183448.GC3646@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=kalle.valo@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.