From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 17 04:43:39 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 1C0221065706 for ; Mon, 17 Nov 2008 04:43:39 +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 DF2A68FC08 for ; Mon, 17 Nov 2008 04:43:38 +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 mAH4hcgt086599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Nov 2008 20:43:38 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <4920F67A.1010103@freebsd.org> Date: Sun, 16 Nov 2008 20:43:38 -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> <4920E8BE.7080208@freebsd.org> <9f8af95f0811162027g41c4460fq89cf106ad64cf505@mail.gmail.com> In-Reply-To: <9f8af95f0811162027g41c4460fq89cf106ad64cf505@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 04:43:39 -0000 The 4965 firmware license does not require an ack via the loader tunable. This used to be true but was changed recently as I was mistaken about the license (only iwi and ipw firmware requires the end user acknowledge the EULA). Everything else that was said seemed spot on. Sam jT wrote: > Sam, > I know you are busy, but can you explain what about my response was > wrong when you say doesn't require sysctl ack -- you mean > acknowledgment? I just would like to know for my future reference and > Steve sorry for my misinformation. > > >> iwn firmware does not require a sysctl ack. >> >> Sam >> >> >> > > > >