Return-path: Received: from mail-ea0-f170.google.com ([209.85.215.170]:60281 "EHLO mail-ea0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751136Ab3DEJpI (ORCPT ); Fri, 5 Apr 2013 05:45:08 -0400 Received: by mail-ea0-f170.google.com with SMTP id a15so1331201eae.29 for ; Fri, 05 Apr 2013 02:45:07 -0700 (PDT) Message-ID: <515E9D1F.8000701@gmail.com> (sfid-20130405_114514_181757_C2A61E50) Date: Fri, 05 Apr 2013 12:45:03 +0300 From: Nick Kossifidis MIME-Version: 1.0 To: Adrian Chadd CC: linux-wireless@vger.kernel.org, =?UTF-8?B?UmljYXJkbyBUdWLDrW8=?= Subject: Re: [ath5k][802.11p] Deactivate beacon References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed Apr 3 23:56:46 2013, Adrian Chadd wrote: > On 3 April 2013 00:30, Ricardo Tubío wrote: >> My name is Ricardo Tubío and I am currently trying to use GCDC patches for the >> 'ath5k' driver in order to meet IEEE 802.11p automotive requirements. I would >> like to know if somebody has either a patch for deactivating the beacon or can >> help me in locating the code where the beacon is implemented. > > Where are these patches hiding? > > I've just been sent a couple of unex cards to implement 802.11p on FreeBSD. > So I'd like to see what the current state of the art with ath5k is. > > Thanks! > > > > Adrian > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html http://comments.gmane.org/gmane.linux.kernel.wireless.general/80154