atheros frecuencies limited
yurtesen at ispro.net.tr
Wed Oct 6 03:46:57 PDT 2004
Sam Leffler wrote:
> On Tuesday 05 October 2004 09:08 am, M. Warner Losh wrote:
>>In message: <416313F0.2000508 at ispro.net.tr>
>> Evren Yurtesen <yurtesen at 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
>>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
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.
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
More information about the freebsd-current