Glossary for all words
Hey guys,
first of all I want to tell you all my commendation for your fine work.= =20
Right now I'm reading your source code to understand your code. In the=20 future I'm interested in extending (may be I would have to hack somehow= )=20
your code. Currently I'm most familiar with upper level usage of WLAN -= =20
especially Ad Hoc mode. Now I got a possibility to dig into the linux=20 kernel and into the maclayer of WLAN for the next years / month during=20 my phd thesis. During reading I got some problems understanding some of= =20
the abbreviations in your code.
Thereby I was thinking a glossary for your framework could be helpful=20 for future newbies.
Would you like to help me withit?
Abbrev: English / German
If: Interface / Schnittstelle
Tx: Transmitter / Sender
Rx: Receiver / Empf=E4nger
STA: State / Status
skb: ?
wiphy: Wireless physical
ops:
vif: ? virtual interface
hw: Hardware?
rtnl:
pid: Process id
When I will have understood the code, I'm interested in sending Beacon=20 frames 'manually' and during this step reconfigure the Beacon data=20 regularly...
=46or now all the Best
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
A few corrections:
Quoted 4 lines · Joe
Hey guys,
first of all I want to tell you all my commendation for your fine wor=
k. Right now I'm reading your source code to understand your code. In t= he future I'm interested in extending (may be I would have to hack some= how) your code. Currently I'm most familiar with upper level usage of W= LAN - especially Ad Hoc mode. Now I got a possibility to dig into the l= inux kernel and into the maclayer of WLAN for the next years / month du= ring my phd thesis. During reading I got some problems understanding so= me of the abbreviations in your code.
Quoted 1 line
Thereby I was thinking a glossary for your framework could be helpful=
for future newbies.
Quoted 5 lines
Would you like to help me withit?
Abbrev: English / German
If: Interface / Schnittstelle
Correct.
Quoted 1 line
Tx: Transmitter / Sender
It can also be just "Transmit".
Quoted 1 line
Rx: Receiver / Empf=E4nger
Again, can be "Receive.
Quoted 1 line
STA: State / Status
No. STA=3DStation. AP=3DAccess point, IBSS=3DAd-hoc, and finally MON an= d
MNTR stand for Monitor. These are interface types.
Quoted 1 line
skb: ?
That's something I can't decipher, either...
Quoted 1 line
wiphy: Wireless physical
Not exactly, it's Wireless PHY. A PHY is a physical-layer controller.
Quoted 1 line
ops:
I don't know this either, maybe operations or output sequence...
Quoted 1 line
vif: ? virtual interface
Exactly.
Quoted 1 line
hw: Hardware?
Yes.
Quoted 1 line
rtnl:
Hmm... maybe real-time netlink?
Quoted 1 line
pid: Process id
No, proportional-integral-derivative.
Quoted 3 lines
When I will have understood the code, I'm interested in sending Beaco=
n frames 'manually' and during this step reconfigure the Beacon data re= gularly...
Quoted 7 lines
For now all the Best
Sebastian--
To unsubscribe from this list: send the line "unsubscribe linux-wirel=
ess" in
Quoted 2 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) --
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 6 lines · On Thu, 2008-06-05 at 23:21 +0200, Stefanik G=C3=A1bor wrote:
A few corrections:
Quoted 4 lines · Joe
Hey guys,
first of all I want to tell you all my commendation for your fine w=
ork. Right now I'm reading your source code to understand your code. In=
the future I'm interested in extending (may be I would have to hack so=
mehow) your code. Currently I'm most familiar with upper level usage of=
WLAN - especially Ad Hoc mode. Now I got a possibility to dig into the= linux kernel and into the maclayer of WLAN for the next years / month =
during my phd thesis. During reading I got some problems understanding = some of the abbreviations in your code.
Quoted 1 line
Quoted 1 line
Thereby I was thinking a glossary for your framework could be helpf=
ul for future newbies.
Quoted 5 lines
Quoted 5 lines
Would you like to help me withit?
Abbrev: English / German
If: Interface / Schnittstelle
Quoted 7 lines
Correct.
Quoted 1 line
Tx: Transmitter / Sender
It can also be just "Transmit".
Quoted 1 line
Rx: Receiver / Empf=C3=A4nger
Again, can be "Receive.
Quoted 1 line
STA: State / Status
No. STA=3DStation. AP=3DAccess point, IBSS=3DAd-hoc, and finally MON =
and
Quoted 3 lines
MNTR stand for Monitor. These are interface types.
Quoted 1 line
skb: ?
That's something I can't decipher, either...
Socket buffer, according to
=EF=BB=BFhttp://vger.kernel.org/~davem/skb.html
Quoted 2 lines
Quoted 1 line
ops:
I don't know this either, maybe operations or output sequence...
operations
Quoted 2 lines
Quoted 1 line
rtnl:
Hmm... maybe real-time netlink?
routing netlink, according to net/core/rtnetlink.c
Quoted 2 lines
Quoted 1 line
pid: Process id
No, proportional-integral-derivative.
http://en.wikipedia.org/wiki/PID_controller
It's the default rate control algorithm in mac80211
--=20
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hey Stefanik, Hi Pavel thank you for this unbelievable fast reaction. This would then be the new state ( I decided to skip German for the beginning to keep everything inline) :
Abbrev: English
If: Interface Tx: Transmitter|Transmit Rx: Receiver|Receive skb: Socket buffer (http://vger.kernel.org/~davem/skb.html)
ops: operations
pid: proportional-integral-derivative (http://en.wikipedia.org/wiki/PID_controller- default rate control algorithm in mac80211)
wiPhy: Wireless PHY. A PHY is a physical-layer controller
hw: Hardware
vif: virtual interface
rtnl: routing netlink (net/core/rtnetlink.c)
[Interface types]:
STA: Station
AP: Access point
IBSS: Ad-hoc
MON|MNTR: Monitor
I will ask for more input in the next days :)
Have a nice time till then
Sebastian
Maybe you want to make yourself an account at the wiki at
http://wireless.kernel.org and start your page there?
Re: [english 97%] *** GMX Spamverdacht *** Re: [english 93%] Re: Glossary for all words
Good idea Holger,
Is it fine for you, if I extend the given Glossary in there? Sebastian
Quoted 7 lines · Holger Schurig
Maybe you want to make yourself an account at the wiki at http://wireless.kernel.org and start your page there? --
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [english 97%] *** GMX Spamverdacht *** Re: [english 93%] Re: Glossary for all words
Quoted 3 lines · Sebastian Fudickar
Good idea Holger,
Is it fine for you, if I extend the given Glossary in there?
Let's actually not do that at all. All of the terms you have tried to collect
* can be decoded by looking at the code
* or by trying to understand the code
* or by looking at other code like the normal networking stack
* or by looking at the 802.11 specs
* are normal abbreviations used everywhere in the kernel
johannes