Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from mms1.broadcom.com ([216.31.210.17]:3163 "EHLO mms1.broadcom.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751109Ab1CWKbx (ORCPT <rfc822;linux-wireless@vger.kernel.org>);
	Wed, 23 Mar 2011 06:31:53 -0400
Message-ID: <4D89CC09.8060702@broadcom.com>
Date: Wed, 23 Mar 2011 11:31:37 +0100
From: "Roland Vossen" <rvossen@broadcom.com>
MIME-Version: 1.0
To: "Johannes Berg" <johannes@sipsolutions.net>,
	"Larry Finger" <Larry.Finger@lwfinger.net>
cc: "Arend Van Spriel" <arend@broadcom.com>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Henry Ptasinski" <henryp@broadcom.com>,
	"Dowan Kim" <dowan@broadcom.com>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: Logs spammed by brcm80211
References: <4D878FBC.5010204@lwfinger.net>
 <op.vspg80mq3ri7v4@arend-laptop>
 <1300733794.3804.0.camel@jlt3.sipsolutions.net>
In-Reply-To: <1300733794.3804.0.camel@jlt3.sipsolutions.net>
Content-Type: text/plain;
 charset=utf-8;
 format=flowed
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

Hello guys,

> Are you saying you expect mac80211 to fragment packets that don't fit
> into a txop? That's not done for sure.

Likely it is a problem in our driver. I have been victimized to take a 
look at it, so consider me your point of this contact for this one ;-) 
I'll keep you guys posted.

Bye, Roland.