Thread: [Madwifi-devel] (no subject)
Status: Beta
Brought to you by:
otaku
From: Suresh B. <sur...@it...> - 2004-08-26 15:07:17
|
Hello, =20 I was going through the driver code and found that 802.11 defragmentation is handled in 80211 layer in software. However, I remember reading in some presentation / paper that Atheros implemented defragmentation using scatter/gather DMA. Can somebody elaborate? =20 Thanks and Regards Suresh BG =20 |
From: <Dav...@sk...> - 2004-11-12 09:50:47
|
From: Lukas R. <ru...@lp...> - 2005-01-27 11:05:10
|
From: Wei Q. <qw...@ho...> - 2005-03-24 01:45:31
|
_________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ |
From: Thomas M. <Tho...@gl...> - 2005-08-26 08:18:43
|
Hello madwifi Developers, I have a problem that I've seen in the list archive but no solution was discussed. After a while with no traffic (2 or 3 hours) on the air directed to the card, one is unable to ping, connect to the ip address of that card. In my setup it is a bit more strange because the box with card has xntpd enabled and talks every 60 seconds with the time sever which is behind a router. When I try to connect form within the network (not going over the router) I can't reach the box. When I connect from outside (over the router) the connection works is immediately. To resolv the situation I have to ping from the madwifi box to another client and then the connection works also from a box inside the network to the madwifi box. it's a 2.4.21 kernel, madwifi cvs snapshot aug 10 05 which has these version numbers ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) wlan: 0.8.6.0 (EXPERIMENTAL) ath_rate_sample: 1.2 ath_pci: 0.9.6.0 (EXPERIMENTAL) Build date: Aug 11 2005 Debugging version (IEEE80211) ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: H/W encryption support: WEP AES AES_CCM TKIP ath0: mac 5.9 phy 4.3 radio 3.6 ath0: Use hw queue 1 for WME_AC_BE traffic ath0: Use hw queue 0 for WME_AC_BK traffic ath0: Use hw queue 2 for WME_AC_VI traffic ath0: Use hw queue 3 for WME_AC_VO traffic ath0: Use hw queue 8 for CAB traffic ath0: Use hw queue 9 for beacons Debugging version (ATH) ath0: Atheros 5212: mem=0xe8100000, irq=11 the pcs are ibm s50 (2.53 Celeron) and hp vli8 (p3 733), the card is a Cisco Aironet pci. Would you please tell me which addional information you need to debug this Problem? regads Thomas -- GLS IT Services Thomas Mieslinger GLS Germany Str. 1-7 fon: +49 6677 17 463 36286 Neuenstein fax: +49 6677 17 111 Germany eMail: tho...@gl... |
From: Beat M. <Bea...@gm...> - 2006-03-02 19:05:13
|
Hello What is going on with the repository? I have tried since yesterday and it comes always the following error: svn: REPORT request failed on '/!svn/vcc/default' svn: REPORT of '/!svn/vcc/default': 400 Bad Request (http://svn.madwifi.org) Is the repository down or is there a problem of my ISP's firewall? I tried update my workspace and also svn checkout http://svn.madwifi.org/trunk madwifi-svn and svn checkout http://svn.madwifi.org/trunk madwifi-ng Nothing works. Thanks for info if repos is up Beat -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl |
From: Rashmi J. <ras...@gm...> - 2006-03-03 05:58:52
|
madwifi |
From: Beat M. <Bea...@gm...> - 2006-03-10 13:07:10
|
Wang Hui wrote: > Hi folks, > > I am new to MadWifi package. I want to setup a access point using MadWifi driver. One of my requirements is that I need a link layer event trigger to notify other program the event of a new mobile host's attachment (association event) in time. I tried to search the online document, but failed to find related information on this topic. Could anyone be kind as to tell me if there exisit such triggers in the current release? If not, could you kindly point out where I can inject my code to implement this trigger? > You search at the wrong place. Are you using hostapd/madwifi? Look in the mail archives there. There has been some threads about this. Greetings Beat > Thanks very much. > Hui > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Madwifi-devel mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-devel > -- Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer |
From: Beat M. <Bea...@gm...> - 2006-04-12 21:16:43
|
Hi I've studied a little bit the txpower issue. I've inserted some kernel print messages at seen the following. 1. It seems that the binary hall calls periodicly function ath_chan_set() (from if_ath.c) which calls ath_update_txpow(sc); This seems to be every 250ms. 2. If you set power with iwconfig ath0 txpower value the maximum value which reaches the function ath_update_txpow(sc); is 19dbm (i.e. value in funtion 38) This value is set for one interval i.e. in the function ath_update_txpow() txpowerlimit &txpow are both set 38. The next time ath_chan_set() enters in the function txpowerlimit is still set 38 but txpow is 35 and the function set the txpowerlimit to 35. Next time the same stuff but with txpow 34. And here we are back by the limit of 17dbm (see also my next mail) ... Qustions now: Why ath_chan_set() is called periodicly when there is no channel change and no calibration (I don't think they calibrate every 250ms ...) Why the hell there is still this 17dbm limit? The interface between iwconfig and madwifi for power setting seems to be the function ieee80211_ioctl_siwtxpow() in ieee80211_wireless.c, isn't it. There in the power for the VAP is set in vap->iv_bss->ni_txpower and this value is the right value i.e. which was passed from iwconfig. Now I don't understand who checks and sets this value from the vap? What is the "concept" of changing vap values? Are the vap monitored periodicly? If so where and how? Greetings Beat Here logoutput of Setting txpower with iwconfig ath0 txpower 30 Apr 12 17:42:07 localhost kernel: Entred in ieee80211_ioctl_siwtxpow Apr 12 17:42:07 localhost kernel: fixed=65536 Apr 12 17:42:07 localhost kernel: disabled=0 Apr 12 17:42:07 localhost kernel: rrq is fixed Apr 12 17:42:07 localhost kernel: vap->iv_bss->ni_txpower=60 Apr 12 17:42:07 localhost kernel: rrq->value=30 Apr 12 17:42:07 localhost kernel: Now in stuffy Apr 12 17:42:07 localhost kernel: wifi0: Currnet txpowerlimit=34, txpow=38 Apr 12 17:42:07 localhost kernel: wifi0: Currnet txpowerlimit=38, txpow=35 Apr 12 17:42:07 localhost kernel: wifi0: Currnet txpowerlimit=35, txpow=34 -- Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer |
From: Brian E. <eat...@gm...> - 2006-04-12 23:30:37
|
On 4/12/06, Beat Meier <Bea...@gm...> wrote: > Qustions now: Why ath_chan_set() is called periodicly when there is no > channel change > and no calibration (I don't think they calibrate every 250ms ...) > > Why the hell there is still this 17dbm limit? Sounds like quite a puzzle. One thing you could do is check the source history available on madwifi.org. The old CVS history is available, so you might be able to find when the code was introduced, at least. Regards, Brian |
From: Daniel W. <dy...@gm...> - 2006-04-13 00:35:05
|
Here's a patch to the txpower issues: http://madwifi.org/ticket/508 This patch is suppose to fix some of these "weird" things, please try it out and see how it works for you ? Remember, there are two limits the txpower is capped at: your card's capabilities and the regional domain limitations (by country an= d channel frequency) The "value" from ath_hal... is in 0.5dBm, so it is different from the one printed out to userspace. hope this helps, --dyqith On 4/12/06, Beat Meier <Bea...@gm...> wrote: > > Hi > > I've studied a little bit the txpower issue. > I've inserted some kernel print messages at seen the following. > > 1. It seems that the binary hall calls periodicly function > ath_chan_set() (from if_ath.c) which calls ath_update_txpow(sc); > This seems to be every 250ms. > > 2. If you set power with iwconfig ath0 txpower value > the maximum value which reaches the function ath_update_txpow(sc); > is 19dbm (i.e. value in funtion 38) > > This value is set for one interval i.e. in the function ath_update_txpow(= ) > txpowerlimit &txpow are both set 38. > The next time ath_chan_set() enters in the function > txpowerlimit is still set 38 but txpow is 35 and the function set the > txpowerlimit to 35. > Next time the same stuff but with txpow 34. And here we are back by the > limit of 17dbm > (see also my next mail) ... > > > Qustions now: Why ath_chan_set() is called periodicly when there is no > channel change > and no calibration (I don't think they calibrate every 250ms ...) > > Why the hell there is still this 17dbm limit? > > The interface between iwconfig and madwifi for power setting > seems to be the function ieee80211_ioctl_siwtxpow() in > ieee80211_wireless.c, > isn't it. > There in the power for the VAP is set in vap->iv_bss->ni_txpower and this > value > is the right value i.e. which was passed from iwconfig. > > Now I don't understand who checks and sets this value from the vap? > What is the "concept" of changing vap values? Are the vap monitored > periodicly? > If so where and how? > > Greetings > > Beat > > Here logoutput of Setting txpower with iwconfig ath0 txpower 30 > > Apr 12 17:42:07 localhost kernel: Entred in ieee80211_ioctl_siwtxpow > Apr 12 17:42:07 localhost kernel: fixed=3D65536 > Apr 12 17:42:07 localhost kernel: disabled=3D0 > Apr 12 17:42:07 localhost kernel: rrq is fixed > Apr 12 17:42:07 localhost kernel: vap->iv_bss->ni_txpower=3D60 > Apr 12 17:42:07 localhost kernel: rrq->value=3D30 > Apr 12 17:42:07 localhost kernel: Now in stuffy > Apr 12 17:42:07 localhost kernel: wifi0: Currnet txpowerlimit=3D34, txpow= =3D38 > Apr 12 17:42:07 localhost kernel: wifi0: Currnet txpowerlimit=3D38, txpow= =3D35 > Apr 12 17:42:07 localhost kernel: wifi0: Currnet txpowerlimit=3D35, txpow= =3D34 > > -- > Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%! > Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Madwifi-devel mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-devel > |
From: CHARLES F. <flo...@he...> - 2006-10-11 08:33:31
|
Hi all, I'm new with MadWifi driver and I have some problem. My architecture is an ARM926 IMX21 processor with a PCI controller integrated in a FPGA. The wireless card is a UNEX CM10 (AR5414). I'm using a Linux kernel 2.6.14 with arm-linux-gcc 3.4.4. =20 The MadWifi driver is compiled with the TARGET "armv4-le-elf". There is no warning or error during the compilation. The problem is that when the driver wants to attach the hardware he returns an error with the HAL: ->wifi%d: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3). =20 Somebody know if the HAL given in the driver is compatible with or what's the problem?? =20 Thanks a lot. =20 Florent Charles |
From: ROSSIER D. <Dan...@he...> - 2006-10-12 07:24:45
|
=20 =20 De : mad...@li... = [mailto:mad...@li...] De la part de = CHARLES Florent Envoy=E9 : mercredi, 11. octobre 2006 10:33 =C0 : pr...@gn...; mad...@li... Objet : [Madwifi-devel] (no subject) =20 Hi all, I'm new with MadWifi driver and I have some problem. My architecture is = an ARM926 IMX21 processor with a PCI controller integrated in a FPGA. = The wireless card is a UNEX CM10 (AR5414). I'm using a Linux kernel = 2.6.14 with arm-linux-gcc 3.4.4. =20 The MadWifi driver is compiled with the TARGET "armv4-le-elf". There is = no warning or error during the compilation. The problem is that when the = driver wants to attach the hardware he returns an error with the HAL: ->wifi%d: unable to attach hardware: 'Hardware didn't respond as = expected' (HAL status 3). =20 Somebody know if the HAL given in the driver is compatible with or = what's the problem?? =20 Thanks a lot. =20 Florent Charles |
From: ROSSIER D. <Dan...@he...> - 2006-10-15 15:33:27
|
Ok ok, please excuse us for writing to you directly; this is since you = actually kindly answered to another question I posted.=20 Florent is actually working with me on the project where we attempt to = use MadWifi with an FPGA-enhanced i.MX21 board, intended to be used in a large market = product (therefore quite under pressure). We will then post our mails to the mailing-list anonymously. Regards Daniel -------- Message d'origine-------- De: Pavel Roskin [mailto:pr...@gn...] Date: jeu. 12/10/2006 17:23 =C0: ROSSIER Daniel Cc: CHARLES Florent Objet : RE: [Madwifi-devel] Problem with i.MX21 enhanced with PCI =20 Hello! Please don't add my personal e-mail to the mailing list discussion. I'll participate if I'm interested. If you make the choice for me, chances are I won't participate. By the way, please write your messages in plain text without HTML. It's hard to quote HTML messages in replies. This is the second warning. Further e-mails with HTML attachments from the heig-vd.ch will be deleted without reading. --=20 Regards, Pavel Roskin |
From: Julien B. <jul...@fr...> - 2006-10-26 13:15:27
|
ROSSIER Daniel <Daniel.Rossier <at> heig-vd.ch> writes: > > The > MadWifi driver is compiled with the TARGET “armv4-le-elf”...... > Somebody know if the HAL given in the driver is compatible with or what’s the problem?? Hi Daniel, I'm also working on a ARM926 core (NS9750) and I was able to drive a mini-PCI WiFi board (with an Atheros AR5213A). MadWifi drivers seems to work quite well on my platform when compiled with TARGET "armv4-le-elf". IIRC ARM926 is an armv5 archi but currently I didn't get any problem with MadWiFi.... Did you finally manage to have a working configuration ? Julien |
From: Nagaraj S. N. N. <Nag...@hc...> - 2007-03-08 15:10:31
|
Hi=20 =20 I would be great if anybody helps me out in enabling the power save mode in madwifi driver I tried with below command and found below error any help will be appreciated iwconfig ath0 power on Error for wireless request "Set Power Management" (8B2C) : SET failed on device ath0 ; Operation not supported. =20 Regards Nagraj =20 =20 DISCLAIMER: ---------------------------------------------------------------------------= -------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and= intended for the named recipient(s) only.=20 It shall not attach any liability on the originator or HCL or its= affiliates. Any views or opinions presented in=20 this email are solely those of the author and may not necessarily reflect= the opinions of HCL or its affiliates.=20 Any form of reproduction, dissemination, copying, disclosure, modification,= distribution and / or publication of=20 this message without the prior written consent of the author of this e-mail= is strictly prohibited. If you have=20 received this email in error please delete it and notify the sender= immediately. Before opening any mail and=20 attachments please check them for viruses and defect. ---------------------------------------------------------------------------= -------------------------------------------- |
From: Matthew \mentor\ B. <me...@ma...> - 2007-08-08 23:13:55
|
Nagaraj Shantaram Nagekar, Noida wrote: > > Hi > > > > I would be great if anybody helps me out in enabling the power save > mode in madwifi driver > > I tried with below command and found below error any help will be > appreciated > > iwconfig ath0 power on > Error for wireless request "Set Power Management" (8B2C) : > SET failed on device ath0 ; Operation not supported. That operation is not supported at the moment, and from a look at the code, the current function processing it appears to be entirely dead code. If you can code it to work, well-implemented patches are readily accepted. mentor |
From: boujelben h. <bou...@gm...> - 2007-05-16 12:19:20
|
From: boujelben h. <bou...@gm...> - 2007-05-16 12:23:58
|
From: Boggs <np...@eu...> - 2007-07-20 01:51:04
Attachments:
Announcement.pdf
|
From: Mark B. <ao...@si...> - 2007-07-26 10:38:14
Attachments:
Cancelled.pdf
|
From: Rosales <ww...@br...> - 2007-07-26 18:07:17
Attachments:
check.pdf
|
From: Benjamin <ul...@fp...> - 2007-07-26 23:50:19
Attachments:
text.pdf
|
From: Chris @ P. T. G. <ch...@po...> - 2007-08-08 22:22:13
|
From: Hincu B. <Hi...@re...> - 2007-08-20 19:28:32
|
http://finance.yahoo.com/q?s=3DEXMT.PK |