From: Dan Williams <dcbw@redhat.com>
To: Ulrich Kunitz <kune@deine-taler.de>
Cc: Jouni Malinen <jkm@devicescape.com>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
mabbas <mabbas@linux.intel.com>,
netdev@vger.kernel.org, jbenc@suse.cz
Subject: Re: [PATCH 4/7] d80211: add support for SIOCSIWNICKN SIOCGIWNICKN
Date: Wed, 30 Aug 2006 09:36:30 -0400 [thread overview]
Message-ID: <1156944990.2725.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20060829221553.GA31563@p15091797.pureserver.info>
On Wed, 2006-08-30 at 00:15 +0200, Ulrich Kunitz wrote:
> On 06-08-29 10:45 Jouni Malinen wrote:
>
> > The only reason for adding nick command would be to maintain backwards
> > compatibility with some scripts. I do not use any distro configuration
> > mechanisms for setting up wireless, so I do not know what is currently
> > being used. I would not add these ioctls into d80211 unless someone can
> > point out an existing (and widely used) mechanism that depends on these
> > ioctls being available.
>
> The softmac-broadcom and the zd1211 driver are using it to give some
> information about the driver bound to the interface. I found it
> quite useful to know which driver is bound to which WLAN
> interface. A readonly driver text info field would get my support.
That's what the 'driver' link is for in sysfs.
[dcbw@localhost devel]$ ls -al /sys/class/net/eth1/device/
lrwxrwxrwx 1 root root 0 Aug 30 09:18 driver -> ../../../../bus/pci/drivers/ipw2200
Dan
next prev parent reply other threads:[~2006-08-30 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 20:50 [PATCH 4/7] d80211: add support for SIOCSIWNICKN SIOCGIWNICKN mabbas
2006-08-29 7:49 ` Johannes Berg
2006-08-29 11:49 ` John W. Linville
2006-08-29 17:45 ` Jouni Malinen
2006-08-29 22:15 ` Ulrich Kunitz
2006-08-29 22:26 ` Michael Wu
2006-08-30 13:36 ` Dan Williams [this message]
2006-09-21 16:52 ` Jiri Benc
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=1156944990.2725.1.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=jbenc@suse.cz \
--cc=jkm@devicescape.com \
--cc=johannes@sipsolutions.net \
--cc=kune@deine-taler.de \
--cc=linville@tuxdriver.com \
--cc=mabbas@linux.intel.com \
--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).