From owner-freebsd-wireless@FreeBSD.ORG Sat Jun 21 02:41:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4EFA020D; Sat, 21 Jun 2014 02:41:58 +0000 (UTC) Received: from mail.metricspace.net (207-172-209-89.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.89]) by mx1.freebsd.org (Postfix) with ESMTP id 2359D24C2; Sat, 21 Jun 2014 02:41:57 +0000 (UTC) Received: from [172.16.1.182] (unknown [172.16.1.182]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 2A92325C50; Sat, 21 Jun 2014 02:41:57 +0000 (UTC) Message-ID: <53A4F0F4.7090507@metricspace.net> Date: Fri, 20 Jun 2014 22:41:56 -0400 From: Eric McCorkle User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Intel 7620AC? References: <53A04AE9.1070401@metricspace.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2014 02:41:58 -0000 On 06/17/2014 11:48, Adrian Chadd wrote: > You also have to be careful that you don't fall afoul of any RCU style > patents. One of the many reasons why mac80211 from linux hasn't been > ported over is that it contains RCU code. Ugh. That sounds like nasty business. Is there any sort of write-up for driver development that outlines the patents we're trying to dodge? > I have a very basic probe/attach working. My next task is implementing > their "transaction" layer that speaks to various busses (although the > only thing they currently ship in Linux is PCIe.) I'm kind of hoping > that once I've implemented that, porting the rest of the driver won't > be so terrible-sounding. > Well, I'm not promising any results, and I only have time for it as a side-project, but if you point me to what you've got or send it to me, I'll take a swing at it.