Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-28 Thread Jouni Malinen
On Wed, Apr 26, 2006 at 07:54:31PM -0500, Larry Finger wrote: > I don't think it would make that much difference as the user could easily > lie about their locality and get any set of parameters that they wanted. Well, not any set.. One of the configured countries, yes, but that is not same as

Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-28 Thread Harald Welte
On Wed, Apr 26, 2006 at 07:54:31PM -0500, Larry Finger wrote: > I am leaning toward putting the geographical information into a > userland daemon. I like that idea very much. This is all control metadate that doesn't really need to be in the kernel. > That way we won't have to patch the kernel

Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-26 Thread Larry Finger
Rick Jones wrote: Christoph Hellwig wrote: On Thu, Apr 13, 2006 at 07:59:21PM -0500, Larry Finger wrote: I am planning on writing a new routine to be added to net/ieee80211/ieee80211_geo.c that will populate an ieee80211_geo object given a country code. The new routine will eliminate the need

Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-17 Thread Rick Jones
Christoph Hellwig wrote: On Thu, Apr 13, 2006 at 07:59:21PM -0500, Larry Finger wrote: I am planning on writing a new routine to be added to net/ieee80211/ieee80211_geo.c that will populate an ieee80211_geo object given a country code. The new routine will eliminate the need for each driver t

Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-15 Thread Christoph Hellwig
On Thu, Apr 13, 2006 at 07:59:21PM -0500, Larry Finger wrote: > I am planning on writing a new routine to be added to > net/ieee80211/ieee80211_geo.c that will populate an ieee80211_geo object > given a country code. The new routine will eliminate the need for each > driver to do their own. Thi

Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-15 Thread Faidon Liambotis
Jouni Malinen wrote: > The maximum power would be quite useful--I would say required--part of > regulatory domain information.. In other words, I would like to see the > groups created in a way that would take differences in power limits into > account. Without this, the groups will need to be re-c

Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-14 Thread Larry Finger
Jouni Malinen wrote: The maximum power would be quite useful--I would say required--part of regulatory domain information.. In other words, I would like to see the groups created in a way that would take differences in power limits into account. Without this, the groups will need to be re-created

Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-14 Thread Jouni Malinen
On Thu, Apr 13, 2006 at 07:59:21PM -0500, Larry Finger wrote: > I am planning on writing a new routine to be added to > net/ieee80211/ieee80211_geo.c that will populate an ieee80211_geo object > given a country code. The new routine will eliminate the need for each > driver to do their own. >

Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-14 Thread Faidon Liambotis
Ulrich Kunitz wrote: > For the 802.11a frequencies, there are three bands: > > Annex 3 Band B 5150-5250 MHz for indoor use (36-48) > Annex 3 Band C 5250-5350 MHz for indoor use (52-64) > Annex 3 Band D 5470-5725 MHz for outdoor use (100-140) > > However these bands are not available in all Europ

Re: [RFC] Geographical/regulatory information for ieee80211

2006-04-14 Thread Ulrich Kunitz
Larry, the CISCO list is not correct. For Europe the detailed information can be found in the recommendation ERC/REC 70-03 of the European Radiocommunications Office. It is downloadable from this page: http://www.ero.dk/documentation/docs/doccategory.asp?catid=2&catname=ECC/ERC/ECTRA%20Recommenda

[RFC] Geographical/regulatory information for ieee80211

2006-04-13 Thread Larry Finger
I am planning on writing a new routine to be added to net/ieee80211/ieee80211_geo.c that will populate an ieee80211_geo object given a country code. The new routine will eliminate the need for each driver to do their own. Finding the allowable channels, etc. for various countries has not been e