Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:53238 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757295Ab3APXXB (ORCPT ); Wed, 16 Jan 2013 18:23:01 -0500 Message-ID: <1358378606.15012.63.camel@jlt4.sipsolutions.net> (sfid-20130117_002304_692256_4EF80F22) Subject: Re: Tx AMSDU Support From: Johannes Berg To: Adrian Chadd Cc: Krishna Chaitanya , linux-wireless , nbd@openwrt.org Date: Thu, 17 Jan 2013 00:23:26 +0100 In-Reply-To: (sfid-20130117_000507_832551_2B8978C4) References: <1358248982.4648.1.camel@jlt4.sipsolutions.net> (sfid-20130117_000507_832551_2B8978C4) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, 2013-01-16 at 15:05 -0800, Adrian Chadd wrote: > .. for testing that out, I ended up just using a NIC that implements > AMSDU in software. > > God knows what it was though (intel?).. Probably Broadcom and/or Marvell. johannes