From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 17 03:45:02 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F32F7106564A for ; Mon, 17 Nov 2008 03:45:02 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id CA02C8FC0C for ; Mon, 17 Nov 2008 03:45:02 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id mAH3j2VQ086340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Nov 2008 19:45:02 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <4920E8BE.7080208@freebsd.org> Date: Sun, 16 Nov 2008 19:45:02 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: jT References: <9f8af95f0811161819i58e3f8bep851ca9ae25c2a43f@mail.gmail.com> In-Reply-To: <9f8af95f0811161819i58e3f8bep851ca9ae25c2a43f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: freebsd-hackers , Steve Tremblett Subject: Re: Intel 5100 WiFi X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2008 03:45:03 -0000 jT wrote: > Steve, > A few Iwn drivers *are* supported, mine being iwn 4965 -- is > supported and has been committed to 8.0-CURRENT. You can find more > information about development on this hardware here : > http://www.clearchain.com/blog/posts/iwn. I'm pretty sure that there > is not that much work done on your model yet. > > Yes it will require a firmware blob as the 4965 one does. You are > required to take notice to the legal aspects of the blob via setting a > key in loader.conf. In terms of FreeBSD aligning with OpenBSD, I have > no idea -- i have only run BSD. We *always* prefer Free as in Freedom > -- hence FreeBSD -- again not sure what the OBSD policies are. > > In addition this is probably a better question for freebsd-mobile or > freebsd-questions > > iwn firmware does not require a sysctl ack. Sam