Date: Thu, 07 Oct 2004 17:50:39 +0300 From: Evren Yurtesen <yurtesen@ispro.net.tr> To: "Marcos Biscaysaqu - ThePacific.net" <marcos@ThePacific.Net> Cc: freebsd-current@freebsd.org Subject: Re: atheros frecuencies limited Message-ID: <416557BF.7050008@ispro.net.tr> In-Reply-To: <41642590.1090402@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <yurtesen@ispro.net.tr> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?416557BF.7050008>