From: Marcel Holtmann <holtmann@linux.intel.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
Johannes Berg <johannes@sipsolutions.net>,
John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Zhu, Yi" <yi.zhu@intel.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: RE: [PATCH] wireless: add regulatory_struct_hint
Date: Thu, 23 Oct 2008 21:54:44 +0200 [thread overview]
Message-ID: <1224791684.9386.194.camel@californication> (raw)
In-Reply-To: <8F0C2E89B9AA20448D482EB589641EB306B6390D@orsmsx507.amr.corp.intel.com>
Hi Luis,
> >Since this is only for wiphys this seems reasonable. I just keep in the
> >back of my mind leaving open the possibility for other wireless
> >subsystems to be able to make use of the currently set regulatory domain
> >and its regulatory rules, but this is in keeping with that as our
> >current requests are not changing the regulatory definitions, and just
> >as we have a wiphy for last_request we can add later struct
> >foo_new_wireless_type there too. I am curious if band definitions
> >should be shared between Bluetooth and 802.11 though. I don't think
> >BT devices have any notion of regulatory though nor are they capable of
> >exporting it though. Marcel is this correct? Inaky -- how about uwb, or
> >WiMax?
>
> UWB swipes over all the bands (from 3.1 to 10.6G), but keeping emission below FCCp15 limits (-41dBm, if memory serves) so it looks as interference to others. All the channel assignments are fixed and known, so in theory,
> it'd be possible to coordinate.
and Bluetooth uses the full 2.4 GHz band (split into 79 channels) and it
uses the full band equally and is allowed to. The regulatory efforts of
the Bluetooth SIG made it possible to use this world-wide. No regulatory
stuff is needed here.
Bluetooth will also use UWB in the future in the range of 6 GHz and it
will get the same world-wide regulatory effort.
The only part I am not sure is Bluetooth over 802.11 since they have
some weird stuff in there and the specification is not final yet.
Regards
Marcel
next prev parent reply other threads:[~2008-10-23 19:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 10:31 [PATCH] wireless: add regulatory_struct_hint Johannes Berg
2008-10-22 12:21 ` Luis R. Rodriguez
2008-10-22 19:30 ` Johannes Berg
2008-10-23 19:40 ` Perez-Gonzalez, Inaky
2008-10-23 19:51 ` Luis R. Rodriguez
2008-10-23 19:53 ` Perez-Gonzalez, Inaky
2008-10-23 19:54 ` Marcel Holtmann [this message]
2008-10-23 21:21 ` Tomas Winkler
2008-10-22 12:27 ` Luis R. Rodriguez
2008-10-22 19:31 ` Johannes Berg
2008-10-24 2:43 ` Zhu Yi
2008-10-24 9:39 ` Johannes Berg
2008-10-24 10:15 ` Luis R. Rodriguez
2008-10-24 18:26 ` Johannes Berg
2008-10-24 18:33 ` Luis R. Rodriguez
2008-10-24 18:35 ` Johannes Berg
2008-10-24 18:18 ` Marcel Holtmann
2008-10-24 18:24 ` Luis R. Rodriguez
2008-10-27 3:08 ` Zhu Yi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1224791684.9386.194.camel@californication \
--to=holtmann@linux.intel.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=mcgrof@gmail.com \
--cc=yi.zhu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.