linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Grimm <patrick@lunatiki.de>
To: "Chatre, Reinette" <reinette.chatre@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [HOTFIX] Re: mac80211/iwl4965: ad-hoc broken in 2.6.25-rc1
Date: Fri, 15 Feb 2008 00:40:05 +0100	[thread overview]
Message-ID: <200802150040.05188.patrick@lunatiki.de> (raw)
In-Reply-To: <47B487EE.3030401@scherping.de>

Am Donnerstag, 14. Februar 2008 19:26:54 schrieb Richard Scherping:
> Chatre, Reinette schrieb:
> > On Wednesday, February 13, 2008 1:07 AM, Richard Scherping  wrote:
> >>> iwl4965: I iwl4965_tx_skb Dropping - !iwl4965_is_associated:
> >>> iwl4965_is_associated(priv)=1; priv->assoc_id=0;
> >>> priv->assoc_station_added=1
> >>
> >> Simply uncommenting the check for priv->assoc_id to be
> >> non-zero (line 2938 in iwl4965-base.c) made ad-hoc working.
> >> Thanks for helping me to find this!
> >> Does this change have any negative side effects?
> >>
> >> Richard
> >
> > Could you please try the attached patch instead?
>
> Works for me (iwl4965). Thanks!
For me not.
I use 3945ABG card in an ad-hoc network with 4 other wlan devices
like rt2500 and ath5k.
I have applied your
0001-iwlwifi-only-check-for-association-id-when-associat.patch
patch. But i can't see incoming packets witch tcpdump.
I have try to commet out  the check for associat with the same
result. 

dmesg
iwl3945: I iwl3945_rx_handle r = 76, i = 75, REPLY_3945_RX, 0x1b
iwl3945: I iwl3945_rx_handle r = 77, i = 76, REPLY_3945_RX, 0x1b
iwl3945: I iwl3945_mac_tx enter
iwl3945: I iwl3945_tx_skb Dropping - !iwl3945_is_associated
iwl3945: I iwl3945_mac_tx leave
iwl3945: I iwl3945_rx_handle r = 78, i = 77, REPLY_3945_RX, 0x1b
iwl3945: I iwl3945_rx_handle r = 79, i = 78, REPLY_3945_RX, 0x1b

Patrick

  reply	other threads:[~2008-02-15  0:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 19:31 mac80211/iwl4965: ad-hoc broken in 2.6.25-rc1 Richard Scherping
2008-02-12 21:51 ` Chatre, Reinette
2008-02-12 23:06   ` Richard Scherping
2008-02-13  9:06     ` [HOTFIX] " Richard Scherping
2008-02-13 22:20       ` Chatre, Reinette
2008-02-14 18:26         ` Richard Scherping
2008-02-14 23:40           ` Patrick Grimm [this message]
2008-02-14 23:57             ` Chatre, Reinette
2008-02-15  0:21               ` Chatre, Reinette
2008-02-15  1:29                 ` Patrick Grimm
2008-02-15 16:39                   ` Chatre, Reinette
2008-02-15 21:12                     ` Richard Scherping
2008-02-15 21:21                       ` Chatre, Reinette
2008-02-16  0:19                       ` Patrick Grimm
2008-02-17 21:37                         ` Patrick Grimm

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=200802150040.05188.patrick@lunatiki.de \
    --to=patrick@lunatiki.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.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).