From owner-freebsd-stable@FreeBSD.ORG Sat Oct 3 21:40:59 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F84B1065672 for ; Sat, 3 Oct 2009 21:40:59 +0000 (UTC) (envelope-from matt@chronos.org.uk) Received: from chronos.org.uk (chronos-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:12b::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7778B8FC15 for ; Sat, 3 Oct 2009 21:40:58 +0000 (UTC) Received: from workstation1.localnet (workstation1.local.chronos.org.uk [IPv6:2001:470:1f09:12b::20]) (authenticated bits=0) by chronos.org.uk (8.14.3/8.14.3) with ESMTP id n93Lej7X082163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Oct 2009 22:40:46 +0100 (BST) (envelope-from matt@chronos.org.uk) X-DKIM: Sendmail DKIM Filter v2.8.3 chronos.org.uk n93Lej7X082163 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=chronos.org.uk; s=mail; t=1254606046; bh=ixP1kxb9yaK4lXp32Kbjr496IVlEN3YJ7YLWvTCXzEQ=; h=From:To:Subject:Date:References:In-Reply-To:Cc:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=eZ0qKC+g9upWH6EZrBK3JtFgejDdiRdL1VFxQgO/UGwF1ZPb5hfvYxgywJWljMrdA rETx4GxuFzixzDW6R9QaD/X+ZIzfzMcthpv/Iz6HqAGZooqdLYittbgUucQt4OLh4m ije1e4VTRSAAaaBpC7hM8+CBw/dnUSH7t0rdDxnc= From: Matt Dawson To: Sam Leffler Date: Sat, 3 Oct 2009 22:40:45 +0100 User-Agent: KMail/1.12.1 (FreeBSD/7.2-RELEASE-p4; KDE/4.3.1; amd64; ; ) References: <200910021726.33663.matt@chronos.org.uk> <4AC797E2.2050709@errno.com> In-Reply-To: <4AC797E2.2050709@errno.com> X-Face: Uq{{&_!oO{M&ydj?-f%{D]bN7/|/]a+utod35[+IyH#R>F~YPffK,=?utf-8?q?=25=60=7D=25=0A?=FTMbmzo,]0X3K:N&{h7],FI{?EkORzB; f:V3"vKXsUNw5Yh`}ef4MZ*a4,=?utf-8?q?ObuJ=5F=26=5B1S=27zP=5CK0wcKZP=0A?==?utf-8?q?_=60=23L=25=5Dq*OUPQ-4T=3FHZ=7EAKX0=7D3W=25o=3DP?= X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (chronos.org.uk [IPv6:2001:470:1f09:12b::1]); Sat, 03 Oct 2009 22:40:46 +0100 (BST) X-Virus-Scanned: clamav-milter 0.95.2 at central.local.chronos.org.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.8 required=3.0 tests=AWL,BAYES_00, DATE_IN_FUTURE_12_24,NO_RELAYS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on central.local.chronos.org.uk Cc: freebsd-stable@freebsd.org Subject: Re: ral(4) on 8-RC1 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: Sat, 03 Oct 2009 21:40:59 -0000 On Saturday 03 Oct 2009 19:28:50 you wrote: > ral probably does not populate it's initial channel list according to > the device capabilities. I'm guessing it falls back on the system code > to do that and it fills in only channels 1-11. This means future > changes to regulatory cannot setup the channels you want--it's not > allowed to add channels that are not listed in the "device > capabilities". That makes sense. Given that my 2561 card has "ETSI" stamped on its label, one would think it's the card's job to report to the driver what it supports. If the driver doesn't request this, the safest bet is the lowest common denominator that should be legal everywhere, 11 channels at FCC spec. Got it. Just a quick question, if I may: Are the maxpower specs of regdomain.xml in dBm? ETSI is max 20dBm ERP at 2.4GHz. Euro spec cards are only capable of ~100mW anyway, most more like 60mW and your average foot of RG-174 will knock nearly a dB off at 2.4GHz, so it hardly matters, but I'm curious. The manpage doesn't specify what the fields mean. > You can hack ral to setup a proper channel list at attach or you can > make a private hack to net80211 to populate the channel list w/ those > channels you want. Either is simple. Thank you. I'll probably try the local hack for now, but hacking ral (and probably iwi now I finally have that working, which does exactly the same thing) to do the right thing would be a better long-term solution. To the list: Does anyone have any idea why the iwi firmware modules build by default on i386 and not on amd64? I know from experience that manually building them on 7.1 amd64 didn't work, but it now works well on 8 except for the messages about mcast/promisc update separation. -- Matt Dawson MTD15-RIPE