From: Dan Williams <dcbw@redhat.com>
To: linux-wireless@vger.kernel.org
Subject: hostap: handling device renames better
Date: Tue, 05 Aug 2008 16:23:41 -0400 [thread overview]
Message-ID: <1217967821.29886.4.camel@localhost.localdomain> (raw)
Hi,
While trying to flash my Prism 2.5 card today, I ran into a problem
that'll probably hit quite a few drivers (mostly older ones).
udev renames the interface after probing, but anything the driver set up
manually at probe/init time (in this case /proc/net/hostap/wifi0/pda)
will still be using the old device name. Thus the prism2_srec tool
refused to work because it needs both the PDA from /proc/net/hostap/...
as well as some ioctls on the device. Unfortunately, the device names
are different due to udev's renaming.
How are drivers made aware that their device's name has changed so they
could potentially update things they stick in /proc or wherever? hostap
and airo come to mind as current users of /proc.
Dan
(ideally this stuff should be migrated to the device's sysfs directory,
not live in /proc/net)
next reply other threads:[~2008-08-05 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 20:23 Dan Williams [this message]
2008-08-05 20:23 ` hostap: handling device renames better Johannes Berg
2008-08-05 20:27 ` Dan Williams
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=1217967821.29886.4.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=linux-wireless@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