From owner-freebsd-net@FreeBSD.ORG Sun Sep 5 17:21:09 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D29A10656A8 for ; Sun, 5 Sep 2010 17:21:09 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id DD3F68FC0A for ; Sun, 5 Sep 2010 17:21:08 +0000 (UTC) Received: by fxm4 with SMTP id 4so2512376fxm.13 for ; Sun, 05 Sep 2010 10:21:08 -0700 (PDT) Received: by 10.223.125.131 with SMTP id y3mr741730far.9.1283705598330; Sun, 05 Sep 2010 09:53:18 -0700 (PDT) Received: from julie.lab.techwires.net (dslb-088-065-215-079.pools.arcor-ip.net [88.65.215.79]) by mx.google.com with ESMTPS id m17sm723971fag.2.2010.09.05.09.53.16 (version=SSLv3 cipher=RC4-MD5); Sun, 05 Sep 2010 09:53:16 -0700 (PDT) From: Bernhard Schmidt To: freebsd-net@freebsd.org Date: Sun, 5 Sep 2010 18:52:05 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-RELEASE; KDE/4.5.1; amd64; ; ) References: <20100905165308.00000d99@unknown> In-Reply-To: <20100905165308.00000d99@unknown> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201009051852.05469.bschmidt@techwires.net> Cc: Bruce Cran Subject: Re: mwl(4) depends on non-existant mwlfw_fw (mwlfw doesn't implement mwlfw_fw) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2010 17:21:09 -0000 On Sunday 05 September 2010 17:53:08 Bruce Cran wrote: > Hi, > > I was trying to help someone on IRC with a card that should be > supported by the mwl(4) driver, but it seems it's broken: mwlfw(4) > doesn't implement mwlfw_fw which if_mwl depends on > ("MODULE_DEPEND(mwl, mwlfw_fw, 1, 1, 1);"). This is wrong. It should depend on firmware(9), which also takes care of loading the adequate firmware modules. > Should it be trying to load mw88W8363fw dynamically instead? Yes, firmware(9) does that. > The same error appears to be in malo(4) too - and neither mwlfw(4) or > malofw(4) are installed during an installkernel despite mwl(4) and > malo(4) being installed. Seems like there is a MFC missing those get installed on HEAD. > malo(4) should also be updated to list "device malofw" in the top > section. malofw(4) doesn't exist yet. -- Bernhard