Return-path: Received: from mail-wi0-f171.google.com ([209.85.212.171]:65397 "EHLO mail-wi0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759193Ab3AQIpQ (ORCPT ); Thu, 17 Jan 2013 03:45:16 -0500 Received: by mail-wi0-f171.google.com with SMTP id hn14so4271229wib.4 for ; Thu, 17 Jan 2013 00:45:15 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <1358378606.15012.63.camel@jlt4.sipsolutions.net> References: <1358248982.4648.1.camel@jlt4.sipsolutions.net> <1358378606.15012.63.camel@jlt4.sipsolutions.net> From: Krishna Chaitanya Date: Thu, 17 Jan 2013 14:14:53 +0530 Message-ID: (sfid-20130117_094521_962238_3D9ABE73) Subject: Re: Tx AMSDU Support To: Johannes Berg Cc: Adrian Chadd , linux-wireless , nbd@openwrt.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Ok...will try with the below ones..Marvell definitely has support for AMSDU Tx. On Thu, Jan 17, 2013 at 4:53 AM, Johannes Berg wrote: > 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 >