From owner-freebsd-stable@FreeBSD.ORG Thu Jul 2 05:28:56 2009 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAA181065670; Thu, 2 Jul 2009 05:28:56 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) by mx1.freebsd.org (Postfix) with ESMTP id 350C38FC15; Thu, 2 Jul 2009 05:28:56 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from mail3.siemens.de (localhost [127.0.0.1]) by thoth.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id n6252CMG022883; Thu, 2 Jul 2009 07:02:12 +0200 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail3.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id n6252C2U003315; Thu, 2 Jul 2009 07:02:12 +0200 Received: (from localhost) by curry.mchp.siemens.de (8.14.3/8.14.3) id n6252CGX006437; Date: Thu, 2 Jul 2009 07:02:12 +0200 From: Andre Albsmeier To: Sam Leffler Message-ID: <20090702050212.GA21954@curry.mchp.siemens.de> References: <20090701193410.GA19202@curry.mchp.siemens.de> <4A4BC709.6060709@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A4BC709.6060709@freebsd.org> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.19 (2009-01-05) Cc: stable@freebsd.org, Andre Albsmeier Subject: Re: net/iwi-firmware refuses to build on 7.2-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2009 05:28:57 -0000 On Wed, 01-Jul-2009 at 13:28:57 -0700, Sam Leffler wrote: > Andre Albsmeier wrote: > > Today I wanted to build net/iwi-firmware on 7.2-STABLE and I got > > > > ===> iwi-firmware-2.4_8 is configured with iwicontrol(8) which you don't need, use 'make rmconfig' and uncheck CONTROL. > > > > While the firmware itself is in the base system, iwicontrol(8) > > is not. The port should be modified to cope with this but I > > have no idea in what way. Some ideas: > > > > 1. Remove the build restrictions > > 2. Just build iwicontrol on systems where the fw is not needed > > 3. Make an extra port just to build iwicontrol > > 4. ??? > > > > Any suggestions? Thanks, > > man iwi; the firmware is automatically loaded by the driver Yes, I know. I don't want to load the firmware, I want to query the state of the hardware switch which enables the transmitter (iwicontrol iwi0 -r). Thanks, -Andre -- Never argue with an idiot. They drag you down to their level, then beat you with their experience.