Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:45636 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751338Ab1KQVL2 (ORCPT ); Thu, 17 Nov 2011 16:11:28 -0500 Subject: Re: 802.11p implementation... From: Johannes Berg To: Nick Kossifidis Cc: Jan de Jongh , linux-wireless@vger.kernel.org In-Reply-To: (sfid-20111117_220842_818501_6C09A1EA) References: <1320585006.11133.2.camel@jlt3.sipsolutions.net> (sfid-20111117_220842_818501_6C09A1EA) Content-Type: text/plain; charset="UTF-8" Date: Thu, 17 Nov 2011 22:11:25 +0100 Message-ID: <1321564285.3997.47.camel@jlt3.sipsolutions.net> (sfid-20111117_221132_114881_24C95346) Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, 2011-11-17 at 22:59 +0200, Nick Kossifidis wrote: > What else do you need from the driver and the protocol stack ? From a > quick look at the patches you use, you only want half width channel > support and to disable beacons by setting beacon interval to 0. Is > that all ? That, btw, is a complete hack and not an actual implementation of the 802.11p spec -- I don't think we'll want that upstream. johannes