From owner-freebsd-questions@FreeBSD.ORG Tue Aug 19 18:21:34 2014 Return-Path: Delivered-To: freebsd-questions@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 29B31CAB for ; Tue, 19 Aug 2014 18:21:34 +0000 (UTC) Received: from cyrus.watson.org (cyrus.watson.org [198.74.231.69]) by mx1.freebsd.org (Postfix) with ESMTP id EE61E3F6B for ; Tue, 19 Aug 2014 18:21:33 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [198.74.231.63]) by cyrus.watson.org (Postfix) with ESMTPS id 920B146B42 for ; Tue, 19 Aug 2014 14:21:33 -0400 (EDT) Received: from fledge.watson.org (doug@localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.8/8.14.8) with ESMTP id s7JILXAr010269 for ; Tue, 19 Aug 2014 14:21:33 -0400 (EDT) (envelope-from doug@fledge.watson.org) Received: from localhost (doug@localhost) by fledge.watson.org (8.14.8/8.14.8/Submit) with ESMTP id s7JILXcf010266 for ; Tue, 19 Aug 2014 14:21:33 -0400 (EDT) (envelope-from doug@fledge.watson.org) Date: Tue, 19 Aug 2014 14:21:33 -0400 (EDT) From: doug Reply-To: doug@safeport.com To: freebsd-questions@freebsd.org Subject: Re: how to encourage a wireless driver to exist? In-Reply-To: <20140819191143.3f4648b7f0416b5d5bc32ce6@yahoo.es> Message-ID: References: <003e01cfb9db$8c11b1e0$a43515a0$@dcollins.info> <20140818233121.GA6745@z.hsd1.ma.comcast.net> <20140818195748.375442d8@scorpio> <20140819101620.8d438b891873ce6f6b61d051@yahoo.es> <6E8C8DB0-35AE-411D-BB34-D5D38E27E172@kraus-haus.org> <20140819191143.3f4648b7f0416b5d5bc32ce6@yahoo.es> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (fledge.watson.org [127.0.0.1]); Tue, 19 Aug 2014 14:21:33 -0400 (EDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2014 18:21:34 -0000 On Tue, 19 Aug 2014, Eduardo Morras wrote: > On Tue, 19 Aug 2014 09:44:19 -0400 > Paul Kraus wrote: > >> On Aug 19, 2014, at 4:16, Eduardo Morras wrote: >> >>> All this description is hardware and managed by hardware. >> >> I would be shocked if all of the requirements of IEEE 802.11af are >> handled in the hardware! Go back and actually read and understand >> that specification. I do not expect the hardware to be querying a >> geolocation database (often multiple databases) and acting >> accordingly. > > Not the requirements, but the description writed by Jerry. As I said too: > >>> Except for ciphers, autentication, etc.. the same applies for/with/to the rest of your descriptions, some of them still in development. > > There are parts of the standard like autentication, geolocation you cite and other parts that managed by the driver, but those part are mostlyt hardware agnostic and works with minor changes, if any, for all drivers. > > The hard part for 802.11n was done by, IIRC, Adrian Chadd and others, new drivers use the infrastructure created by them to not reimplement the wheel. > >> I have been watching this specific bit of spectrum from the Wireless >> Microphone / FCC side for a decade now. If systems start coming into >> use that do NOT follow the required procedures there will be hell to >> pay as these specific frequencies are in use by lots of other users >> besides wireless networking. > > When I began to use wireless, it was fantastic. Now, all my neighbours has > wifi, smartphones, wireless telephones, bluetooth devices etc... and speeds > went down to 500-600KB/sec. I wired again my home with gig ethernet. 0 > problems. > The original question was how to, or more to the point, is it possible to get a driver for the xyz wifi card. If there is an answer to that (past write it dude), it probably will involve back-porting from PC-BSD or finding a way to support drivers written for Linux or any BSD that is somewhat more X11-centric. As an aside, http://laptop.bsdgroup.de/freebsd/ linked to by the handbook and PC-BSD support threads remains down.