linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <Kalle.Valo@nokia.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Jiri Benc <jbenc@suse.cz>, Michael Wu <flamingice@sourmilk.net>,
	Michael Buesch <mb@bu3sch.de>
Subject: Re: mac80211 AP mode powersaving problems?
Date: Wed, 29 Aug 2007 17:35:06 +0300	[thread overview]
Message-ID: <873ay2v279.fsf@nokia.com> (raw)
In-Reply-To: <1188376637.7837.149.camel@johannes.berg> (ext Johannes Berg's message of "Wed\, 29 Aug 2007 10\:37\:17 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

> On Wed, 2007-08-29 at 07:18 +0300, Kalle Valo wrote:
>
>> > Can you disable QoS and see if the same weird frames show up again? b43
>> > doesn't really support QoS yet but I don't think that should be causing
>> > such frame corruption.
>> 
>> From b43 or N800? 
>
> N800, I guess, if possible. But since you didn't do this yet you might
> want to try the stuff I sent you first.

I tested your multicast stuff and it worked. Do you still want me to
test with QoS disabled in N800?

>> > Interestingly, your N800 seems to pick up the frames correctly since it
>> > did reply to the ping packets... 
>> 
>> Yes, N800 managed to receive some ping packets from the laptop
>
> Yes, the odd thing however is that it replies to these mangled packets.
> I would guess that's a bug in the QoS implementation on the N800.

Good point. I'll look into that.

-- 
Kalle Valo

  reply	other threads:[~2007-08-29 14:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  7:35 mac80211 AP mode powersaving problems? Johannes Berg
2007-08-16  5:43 ` Kalle Valo
2007-08-16 13:21   ` Johannes Berg
2007-08-16 14:31     ` Kalle Valo
2007-08-16 14:42       ` Johannes Berg
     [not found]         ` <86wsvv8m9t.fsf@coulee.tdb.com>
2007-08-16 17:02           ` Johannes Berg
2007-08-16 18:37             ` Russell Senior
2007-08-17 10:14               ` Johannes Berg
2007-08-27 15:58         ` Kalle Valo
2007-08-28  8:48           ` Johannes Berg
2007-08-28 10:59             ` Kalle Valo
2007-08-28 11:05               ` Johannes Berg
2007-08-28 11:11                 ` Kalle Valo
2007-08-28 16:06                 ` Kalle Valo
2007-08-28 16:18                   ` Johannes Berg
2007-08-28 18:08                     ` Kalle Valo
2007-08-28 18:43                       ` Johannes Berg
2007-08-29  4:18                         ` Kalle Valo
2007-08-29  8:37                           ` Johannes Berg
2007-08-29 14:35                             ` Kalle Valo [this message]
2007-08-30 11:56                               ` Johannes Berg
2007-08-29  0:12                   ` Johannes Berg
2007-08-29  0:58                   ` Johannes Berg
2007-08-29 10:11                     ` Johannes Berg
2007-08-29 17:50                       ` Michael Buesch
2007-08-30 11:54                         ` Johannes Berg
2007-08-29 14:32                     ` Kalle Valo
2007-08-30 11:55                       ` Johannes Berg
2007-08-22  7:49   ` b43 vs. the TIM (was: mac80211 AP mode powersaving problems?) Johannes Berg

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=873ay2v279.fsf@nokia.com \
    --to=kalle.valo@nokia.com \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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).