From: Marcel Holtmann <marcel@holtmann.org>
To: Tim Schneider <schneid5@cs.uni-bonn.de>
Cc: netdev <netdev@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Using Wireless Extensions in a Kernel Module
Date: Fri, 10 Jul 2009 09:39:24 -0700 [thread overview]
Message-ID: <1247243964.9709.71.camel@localhost.localdomain> (raw)
In-Reply-To: <A353FA76-7D71-425F-BD67-FEE6DC26EF6F@cs.uni-bonn.de>
Hi Tim,
> I am trying to write a Kernel Module with an implementation of a new
> TCP-Algorithm. Since I need to know the RSSI-Value (Received Signal
> Strength indication) of the sent package, I extended the Pluggable
> Congestion Control Mechanism by a new function which is called right
> after the package is send. At that point, I need to read the RSSI-Value.
>
> I'm now trying to somehow access that value, but I can't figure out
> how. I've come as far, that I found out about the Wirelless
> Extensions, which seem to be very promising. In the header file the
> author states, that this mechanism can be used by both user-space apps
> and kernel modules. Unfortunately nobody seems to ever have used it in
> kernel space, since I can't find any documentations about it.
>
> I would be very glad, if somebody could give me link to a page
> containing informations about this topic, or even just a hint that
> could help me.
we are in the process of killing Wireless Extensions (WEXT) and
replacing it with a netlink based cfg80211/nl80211 interface. The better
mailing list is linux-wireless@vger.kernel.org for such questions.
Regards
Marcel
next prev parent reply other threads:[~2009-07-10 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 9:23 Using Wireless Extensions in a Kernel Module Tim Schneider
2009-07-10 16:39 ` Marcel Holtmann [this message]
[not found] ` <4A5850E7.5020708@gdt.id.au>
2009-07-13 6:24 ` Tim Schneider
2009-07-15 9:17 ` why some packets lost during transmission? jon_zhou
2009-07-15 17:17 ` Jesper Dangaard Brouer
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=1247243964.9709.71.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=schneid5@cs.uni-bonn.de \
/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