From: Pascal Huerst <pascal.huerst@gmail.com>
To: sgruszka@redhat.com
Cc: linux-wireless@vger.kernel.org
Subject: rt2x00: Firmware loading vs. udev rules
Date: Tue, 29 Sep 2015 18:38:19 +0200 [thread overview]
Message-ID: <560ABE7B.1080109@gmail.com> (raw)
Hey Stanislaw, all,
on rt2x00 devices, firmware gets loaded in:
int rt2x00lib_start(struct rt2x00_dev *rt2x00dev)
which is called, when we start the interface by:
ifconfig wlan0 up
I need to lower tx power of the device and created a udev rule for that:
KERNEL=="wlan0", RUN+="/usr/sbin/iw dev wlan0 set txpower fixed 1800"
Obviously this does not work, since the firmware is not loaded, yet.
Is there a reason, why the firmware is loaded so late and not earlier in
probe or so?
Can this be done in any other proper way I don't know about?
I think the device should be ready for any operation, when the udev rule
triggers, right?
regards
Pascal
next reply other threads:[~2015-09-29 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 16:38 Pascal Huerst [this message]
2015-10-02 8:43 ` rt2x00: Firmware loading vs. udev rules Stanislaw Gruszka
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=560ABE7B.1080109@gmail.com \
--to=pascal.huerst@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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).