linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Andreas Hartmann <andihartmann@01019freenet.de>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Felix Fietkau <nbd@openwrt.org>
Subject: Re: Compat-wireless-3.2-rc6-3 is broken for rt2860 device
Date: Tue, 24 Jan 2012 16:19:27 +0100	[thread overview]
Message-ID: <CAGXE3d8AbZB2GuPN0x8cNdvPXmKAH3Soug=COahvma4yQKFN5A@mail.gmail.com> (raw)
In-Reply-To: <20120124143909.GA5217@redhat.com>

On Tue, Jan 24, 2012 at 3:39 PM, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> On Tue, Jan 24, 2012 at 09:07:04AM +0100, Helmut Schaa wrote:
>> > but the machine does crash anyway. Could hdr be null, too?
>>
>> Ok, I'll do some testing as soon as time allows and get back to you then.
>
> Not sure how good idea is is, but perhaps we could introduce mac80211 flag
> that will disable behaviour of f0425bed commit for drivers, which will
> set that flag.

I don't think this is a good idea, since if it is a device workaround
it should be
implemented in the driver. That's what I tried before but according to Andreas
the patch causes a crash. But in general it should be possible to bring a
BA session down by calling ieee80211_stop_tx_ba_session from the driver.
Not sure why that'll crash :(

Helmut

  reply	other threads:[~2012-01-24 15:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 13:49 Compat-wireless-3.2-rc6-3 is broken for rt2860 device Andreas Hartmann
2011-12-31 20:35 ` Andreas Hartmann
2012-01-03 21:51   ` Helmut Schaa
2012-01-04  8:38     ` Andreas Hartmann
2012-01-04 15:04       ` Helmut Schaa
2012-01-05  8:44         ` Andreas Hartmann
2012-01-09 10:23           ` Helmut Schaa
2012-01-09 13:29             ` Andreas Hartmann
2012-01-09 13:45               ` Helmut Schaa
2012-01-10  8:03                 ` Andreas Hartmann
2012-01-10  9:50                   ` Helmut Schaa
2012-01-10 11:56                     ` Andreas Hartmann
2012-01-10 12:23                       ` Helmut Schaa
2012-01-10 13:01                         ` Andreas Hartmann
2012-01-10 13:43                           ` Helmut Schaa
2012-01-10 14:41                             ` Andreas Hartmann
2012-01-17  9:09                     ` Andreas Hartmann
2012-01-20  7:29                     ` Andreas Hartmann
2012-01-23 13:29                       ` Helmut Schaa
2012-01-23 16:03                         ` Andreas Hartmann
2012-01-23 16:36                           ` Helmut Schaa
2012-01-23 17:44                             ` Andreas Hartmann
2012-01-24  8:07                               ` Helmut Schaa
2012-01-24 14:39                                 ` Stanislaw Gruszka
2012-01-24 15:19                                   ` Helmut Schaa [this message]
2012-01-24  7:29                         ` Stanislaw Gruszka
2012-01-24  8:01                           ` Andreas Hartmann
2012-01-24  8:06                           ` Helmut Schaa
2012-01-04 12:29     ` Andreas Hartmann

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='CAGXE3d8AbZB2GuPN0x8cNdvPXmKAH3Soug=COahvma4yQKFN5A@mail.gmail.com' \
    --to=helmut.schaa@googlemail.com \
    --cc=andihartmann@01019freenet.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=sgruszka@redhat.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).