From owner-freebsd-mobile@FreeBSD.ORG Tue Sep 20 11:31:25 2005 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A598816A41F for ; Tue, 20 Sep 2005 11:31:25 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D92443D45 for ; Tue, 20 Sep 2005 11:31:24 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from 217-13-2-82.dd.nextgentel.com ([217.13.2.82] helo=lapdance.yazzy.net) by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1EHgKs-0001sa-E6; Tue, 20 Sep 2005 13:30:55 +0200 Date: Tue, 20 Sep 2005 11:31:05 +0000 From: Marcin Jessa To: Tobias Roth Message-Id: <20050920113105.1afb8d7d.lists@yazzy.org> In-Reply-To: <20050920082740.GA29652@droopy.unibe.ch> References: <200509142146.42969.plosher@plosh.net> <200509191617.49953.plosher@plosh.net> <20050920091648.41e2bf16.lists@yazzy.org> <20050920082740.GA29652@droopy.unibe.ch> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.1 (GTK+ 2.6.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) Cc: plosher-keyword-freebsd.a36e57@plosh.net, freebsd-mobile@freebsd.org Subject: Re: Best way to load iwi firmware for wpa_supplicant? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2005 11:31:25 -0000 On Tue, 20 Sep 2005 10:27:40 +0200 Tobias Roth wrote: > On Tue, Sep 20, 2005 at 09:16:48AM +0200, Marcin Jessa wrote: > > > > Why are you loading the module at all and not compile it into your kernel? > > The firmware has to be loaded in addition of the module. When and how > to load the firmware is the problem, not when and how to load the > kernel module.o > I just load it within an rc.d script and iwi is compiled into my kernel, but I don't use WEP/WPA encryption. I'd just add a function to /etc/rc which is the first thing /sbin/init executes or add a custom script to rc.d which executes before wpa_supplicant. The only thing you'd have to remember is you have the script there performing mergemaster. There are really so many possibilities. Marcin.