linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: "Richard Schütz" <r.schtz@t-online.de>
Cc: Stevie Trujillo <stevie.trujillo@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: is tx_power_device_lmt a regulatory limit or a hardware limit?
Date: Fri, 10 Jun 2011 10:31:23 -0700	[thread overview]
Message-ID: <1307727083.13397.57.camel@wwguy-huron> (raw)
In-Reply-To: <4DF246D1.9000107@t-online.de>

On Fri, 2011-06-10 at 09:31 -0700, Richard Schütz wrote:
> On 26.05.2011 16:11, wwguy wrote:
> > On Thu, 2011-05-26 at 01:50 -0700, Richard Schütz wrote:
> >>> On Wed, 2011-05-25 at 12:54 -0700, Stevie Trujillo wrote:
> >>>> On Wednesday 25 May 2011 21:42:40 wwguy wrote:
> >>>>> On Wed, 2011-05-25 at 09:13 -0700, Stevie Trujillo wrote:
> >>>>>> Hello,
> >>>>>>
> >>>>>> I have a "Intel(R) Centrino(R) 1030 BGN" card. tx_power_device_lmt is 15
> >>>>>> and I was wondering if the card could do more than that.
> >>>>>
> >>>>> the card should not and will not do more than what required by
> >>>>> regulatory
> >>>>
> >>>> I'm allowed to do 20dBm here and was wondering if I could make the card do
> >>>> that.
> >>>>
> >>> the tx power in Intel WiFi device is regulated by uCode to make sure we
> >>> are within regulatory limits. What country you are in?
> >>>
> >>> Thanks
> >>> Wey
> >>
> >> I am also having the same issue with my Intel PRO/Wireless 5100 AGN.
> >> Here in Germany I'm allowed to use 20 dBm (in the 2.4 GHz band), but the
> >> card is limited to 15 dBm. So in some situations other cards are working
> >> fine (as they use 20 dBm) and the Intel can't establish a connection.
> >>
> > We do not have different SKUs for different regions of the world. Now I
> > understand your problem. Thank you very much for reporting. I will raise
> > the issue and see how we should fix it.
> >
> > Sorry, I don't have a solution for you today. But it is very important
> > for us and we need to result it.
> >
> > Thanks
> > Wey
> 
> Is there any news?
> 
Hi, I talk to the marketing and since we are providing single SKU
solution, the maximum allowed tx power is programmed in EEPROM, so
currently there is no method to allow use the higher limitation.

Thanks
Wey



  reply	other threads:[~2011-06-10 18:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 16:13 iwlagn: is tx_power_device_lmt a regulatory limit or a hardware limit? Stevie Trujillo
2011-05-25 19:42 ` wwguy
2011-05-25 19:54   ` Stevie Trujillo
2011-05-26  2:28     ` wwguy
2011-05-26  6:22       ` Stevie Trujillo
2011-05-26  8:50       ` Richard Schütz
2011-05-26 14:11         ` wwguy
2011-06-10 16:31           ` Richard Schütz
2011-06-10 17:31             ` Guy, Wey-Yi [this message]
2011-06-10 18:24               ` Richard Schütz
     [not found]                 ` <BANLkTimjLdr2Qb+yfUx84p4k2Oq8iumDhg@mail.gmail.com>
2011-06-10 18:42                   ` Fwd: " Daniel Halperin
2011-06-10 19:19                     ` Richard Schütz

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=1307727083.13397.57.camel@wwguy-huron \
    --to=wey-yi.w.guy@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=r.schtz@t-online.de \
    --cc=stevie.trujillo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).