From: mabbas <mabbas@linux.intel.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/7] d80211: add SIOCSIWTXPOW, SIOCGIWTXPOW, SIOCSIWPOWER and SIOCGIWPOWER
Date: Thu, 21 Sep 2006 15:39:40 -0700 [thread overview]
Message-ID: <451314AC.3070103@linux.intel.com> (raw)
In-Reply-To: <20060922001332.7ea0d30a@logostar.upir.cz>
Jiri Benc wrote:
> On Thu, 21 Sep 2006 12:57:01 -0700, mabbas wrote:
>
>> if the user set txpoer using iwconfig command, the driver will clap all
>> txpower to this
>> value for all available channels if channels original txpower is higher
>> than txpower value.
>>
>
> Looks like a job for the stack.
>
> If the stack takes care about that and always pass the correct value to a
> driver, is there still a reason for the driver to know where the request
> originated from?
>
> Jiri
>
>
if the stack handle it then no need to know. When I call
ieee80211_register_hw with driver's channel, rate and txpower info. the
txpower values are overwritten by ieee80211_init_client. I get all the
txpower info from EEPROMin the NIC and they are different that what
d80211 default to. Is there is away to keep the value the driver passed
in ieee80211_register_hw?
Mohamed
next prev parent reply other threads:[~2006-09-21 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 20:45 [PATCH 1/7] d80211: add SIOCSIWTXPOW, SIOCGIWTXPOW, SIOCSIWPOWER and SIOCGIWPOWER mabbas
2006-09-21 16:30 ` Jiri Benc
2006-09-21 16:43 ` mabbas
2006-09-21 18:33 ` Jiri Benc
2006-09-21 19:57 ` mabbas
2006-09-21 22:13 ` Jiri Benc
2006-09-21 22:39 ` mabbas [this message]
2006-09-22 11:16 ` Jiri Benc
2006-09-22 13:24 ` Larry Finger
2006-09-22 13:30 ` Johannes Berg
2006-09-22 13:54 ` Larry Finger
2006-09-25 8:42 ` Johannes Berg
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=451314AC.3070103@linux.intel.com \
--to=mabbas@linux.intel.com \
--cc=jbenc@suse.cz \
--cc=netdev@vger.kernel.org \
/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).