From owner-freebsd-wireless@FreeBSD.ORG Fri Sep 5 10:33:47 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 68CC9952; Fri, 5 Sep 2014 10:33:47 +0000 (UTC) Received: from mail-yh0-x22c.google.com (mail-yh0-x22c.google.com [IPv6:2607:f8b0:4002:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1DD401FF6; Fri, 5 Sep 2014 10:33:47 +0000 (UTC) Received: by mail-yh0-f44.google.com with SMTP id a41so7317423yho.3 for ; Fri, 05 Sep 2014 03:33:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=KWM+Oe961IwFW1eAbk1c0YZ9izAftxOCt+xP6z96BYY=; b=WdX9D5QOd1QeJmlTf8Xb80HykG18P5+H0evVHIDSwg+ncCtq60nhmlRXDKPI4a7VFw 030IAgUxydri0mkMrJW3NMoF3T87y3vOugEuilhBkfoTbw/l67TOL/lCiQ0HDK5+0zLL L4or8gcHR6bmF0WHUecV0MR+ETty1gqxWU3kDMlr/c3aVu6Cf6zo+8kEflF1qLejW0CA SQh1y16Y/qCg7Bu+eR2Zg6bQCzLRjFoZP79z5hZwjydc76hmWqSZbx8EhFMs+nBf6XFH AJxSVNqViha6vWgqhUwUe+fkR6HCeVKMERz5WIPJOihauVt1UQKOqBanAnvmhAGAJANd 9cZw== MIME-Version: 1.0 X-Received: by 10.236.133.165 with SMTP id q25mr13284324yhi.62.1409913225966; Fri, 05 Sep 2014 03:33:45 -0700 (PDT) Received: by 10.170.147.4 with HTTP; Fri, 5 Sep 2014 03:33:45 -0700 (PDT) In-Reply-To: <20140904135018.GA2241@tiny-r269739> References: <20140904135018.GA2241@tiny-r269739> Date: Fri, 5 Sep 2014 14:33:45 +0400 Message-ID: Subject: Re: FreeBSD wireless support is lacking; needs better documentation From: Sergey Ryazanov To: Matthias Apitz Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org, Dirk E X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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: Fri, 05 Sep 2014 10:33:47 -0000 Hello, 2014-09-04 17:50 GMT+04:00, Matthias Apitz : > El d=EDa Tuesday, September 02, 2014 a las 09:13:10PM -0700, hiren pancha= sara > escribi=F3: > >> On Aug 30, 2014 9:39 AM, "Dirk E" wrote: >> > >> > ... >> > >> > I propose the following: create a wiki with a list of known working >> > wireless products. Each product should note which chipset it uses, wha= t >> > driver it connects to, what features are suported (i.e. HOSTAP), what >> > FreeBSD versions are supported, whether it is open source / binary blo= b, >> > any license requirements (like Realtek) and a dmesg snippet where the >> > driver is detected. It can be managed by a maintainer that accepts ema= il >> > reports from users who provide the required information. That way, we >> > get a >> > list of hardware that is known to work with FreeBSD that people can >> > actually buy. Even a NewEgg-link or something to that effect can be >> > provided. >> > >> > This website was a lot of help to me in figuring out what chipset a >> > wireless product uses: https://wikidevi.com/wiki/Main_Page >> > I propose something simpler for FreeBSD; just a single wiki page that >> > lists products that either work or do not work. > > I fully agree with that we need more structured documentation about what > is working, in which versions and with which details. I'm editing in the > FreeBSD Wiki the webcam compatibility list and I know that editing Wiki > pages can be a mess and is not what every user who got something to > work, or to know, is wanting to do. What we do need is somekind of > database with a webform by which everybody could insert (or even edit) > exsisting data, ofc with somekind of creation of account and an anti-SPAM > capcha. Without this, the data actualization depends on the time and > availibility of the maintainer(s) of the page and information tends to be > outdated. > Maybe it would easier to maintain a list of supported chipsets and provide a link to a website with a hardware database (e.g. wikidevi.com)? There are not so many chips as compared with the amount of different devices. Also wikidevi and similar projects are not depend on OS and have a wider auditory. Just my 2 cents. --=20 BR, Sergey