From owner-freebsd-current@FreeBSD.ORG Thu Oct 7 14:49:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D57C316A4CE for ; Thu, 7 Oct 2004 14:49:32 +0000 (GMT) Received: from supermail.ispro.net.tr (supermail.ispro.net.tr [217.21.68.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DC7143D3F for ; Thu, 7 Oct 2004 14:49:30 +0000 (GMT) (envelope-from yurtesen-dated-1098024564.8237af@ispro.net.tr) Received: (qmail 97816 invoked by uid 89); 7 Oct 2004 14:49:24 -0000 Received: from [130.232.138.155] (perpetual.yok.utu.fi [130.232.138.155]) by supermail.ispro.net.tr (tmda-ofmipd) with ESMTP; Thu, 07 Oct 2004 17:49:17 +0300 (EEST) Message-ID: <416557BF.7050008@ispro.net.tr> Date: Thu, 07 Oct 2004 17:50:39 +0300 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Marcos Biscaysaqu - ThePacific.net" References: <4161C4D8.4040308@ispro.net.tr> <416313F0.2000508@ispro.net.tr> <20041005.100800.111987973.imp@bsdimp.com> <200410050953.58739.sam@errno.com> <416459A1.7020208@ispro.net.tr> <41642590.1090402@ThePacific.Net> In-Reply-To: <41642590.1090402@ThePacific.Net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.0.2 (Bold Forbes) From: Evren Yurtesen X-Primary-Address: yurtesen@ispro.net.tr cc: freebsd-current@freebsd.org Subject: Re: atheros frecuencies limited X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2004 14:49:33 -0000 Marcos Biscaysaqu - ThePacific.net wrote: > Evren Yurtesen wrote: > >> >> >> Sam Leffler wrote: >> >>> On Tuesday 05 October 2004 09:08 am, M. Warner Losh wrote: >>> >>>> In message: <416313F0.2000508@ispro.net.tr> >>>> >>>> Evren Yurtesen writes: >>>> : For one thing, why shouldnt FreeBSD able to do that? >>>> >>>> Because the HAL layer is a binary glob. >>>> >>>> : The other thing is that I thought atheros doesnt have firmware and >>>> the >>>> : driver handles the regulatory domain settings. Thats why atheros >>>> is not >>>> : giving out the source code for their drivers (I think there was such >>>> : problem) >>>> >>>> The driver handles the regulatory domain, but it always uses what is >>>> in the falsh on the part. >>>> >>>> : Anyhow. I am not a pro in this so I better shut up :) But it is >>>> possible >>>> : to enable all the channels etc. available in atheros chip from the >>>> : driver. At least StarOS is able to do it so... >>>> >>>> I'm hoping that ath driver author would reply. >>> >>> >>> >>> >>> And I was hoping the "ath driver author" could stay out of this topic >>> because it has been discussed repeatedly. >>> >>> The issue is that the ath driver supports ap operation. As such you >>> are not permitted to change the regulatory domain from what is set in >>> the eeprom to insure compliance with local regulatory agencies. >>> Drivers that let you set the regulatory domain--that I know >>> about--support only station operation so this is not an issue (e.g. >>> you are not normally broadcasting beacons). I have considered ways >>> to support ap and non-ap operation in a single driver and still allow >>> the regulatory domain to be changed but haven't implemented them. >>> >>> Sam >> >> >> >> That can't be true. There is at least StarOS product which can work as >> an AP and can support every channel. Even the ones which is not in any >> regulatory domain (I think?!) >> >> Actually as a matter of fact I have few Senao APs which has Atheros >> minipci cards inside and they also allow regulatory domain setting so >> that some channels become activated and some are disabled etc. >> depending on the domain you choose. >> >> http://www.staros.com/downloads.php >> ------------ >> New: Special country code '##' can be used to unlock all channels >> supported by the Atheros hardware (2312-2732, 4920-6100). It is up to >> the end user to ensure they stay within their region's regulatory >> channel ranges. >> ------------ >> >> Evren >> >> > You right, another OS is Mikrotik which is linux base, support all the > frecuencies > Actually I was gonna write about MikroTik but thats not true. I also use MikroTik and it doesnt support all the frequencies. It doesnt even have country selection. I think StarOS is able to unlock the cards somehow. But MikroTik shows only the frequencies that the card can support. For example in MikroTik, I am not able to use channel 14 of 802.11b but in StarOS its visible with the same card. I never tried if it works though. Evren