Ticket Navigation

Ticket #1679 (closed enhancement: invalid)

Opened 3 years ago

Last modified 6 months ago

Patch for AR2425 (AR5007EG) chipset

Reported by:	madwifi@atheros.com	Assigned to:	proski
Priority:	minor	Milestone:
Component:	madwifi: HAL	Version:	v0.9.3.3
Keywords:		Cc:
Patch is attached:	0	Pending:	0

Attachments

2425-mad-trace-all-modes.tgz (1.1 MB) - added by anonymous on 01/12/08 17:35:02.: madwifi-trace trace on Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter [168c:001c]
dmesg.txt (15.7 kB) - added by beechhorn@gmail.com on 01/30/08 08:45:54.: DMESG dump from kernel 2.6.24.
I-did-not-read-the-ticket_madwifi-ng-r3365.ar2425.20080227.i386.patch (0.7 MB) - added by mentor on 06/22/08 02:30:45.: Atheros' AR2425 patch modified for SVN head (r3365)
I-did-not-read-the-ticket_madwifi-ng-0933.ar2425.20071130.i386.patch (0.7 MB) - added by mentor on 06/22/08 02:32:54.: Support AR5007EG (AR2425) chipset (32-bits x86 only)
I-did-not-read-the-ticket_madwifi-eee-2.6.24.patch (11.2 kB) - added by mentor on 06/22/08 02:35:44.: Changesets 2759, 2795, 2796, 2814, 2815, 2981, 3317, 3318 and 3319

Change History

12/01/07 23:28:43 changed by madwifi@atheros.com

This patch is for 32-bits x86 platforms including i686 and AMD CPUs (Thanks strasak!). This patch does not work for 64-bits x86 platforms.

This patch is for the Madwifi driver snapshot r2756 only. Sorry about the wrong information in the original posting.

To apply the patch

1. Download the Madwifi driver snapshot r2756 using the following link and save the file.

snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz

2. Extract this driver source and change into the driver directory.

prompt> tar -xvzf madwifi-ng-r2756-20071018.tar.gz
prompt> cd madwifi-ng-r2756-20071018/

3. Download the patch using the following link and save the file.

madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw

4. Patch the Madwifi driver.

prompt> patch -p0 < madwifi-ng-0933.ar2425.20071130.i386.patch

5. Make and install this updated driver according the instructions in the "INSTALL" file from the madwifi package.

(follow-up: ↓ 14 ) 12/02/07 10:50:18 changed by kelmo

patch_attached deleted.

Hi,

Sorry to be the party pooper, but I am removing the patch from this ticket until we know the origin of it, and the patch submitter has contacted the developers of this project to co-ordinate the availability of this new code for public consumption.

Scott Raynel has attempted to contact the two mail addresses from Atheros on this ticket in order to receive more information about the situation.

It is, in our opinion, not very responsible to allow an unknown blob to be made available like this. We have no way of knowing what this blob does, and we never will, because its not transparent. But we do _need_ to be informed by the blob vendor what changes it brings.

Hope for understanding.

(in reply to: ↑ 13 ) 12/02/07 12:40:20 changed by mrenzmann

Replying to kelmo:

It is, in our opinion, not very responsible to allow an unknown blob to be made available like this. We have no way of knowing what this blob does, and we never will, because its not transparent. But we do _need_ to be informed by the blob vendor what changes it brings.

Not only that. If we apply patches to the HAL blob we got from our original HAL upstream, we divert from it and make it harder (if not impossible) to incorporate future updates from upstream (read: Sam). It's a similar issue as with the question of whether or not we should try to incorporate the HAL that comes with Asus' variant of MadWifi.

Bottom line: I second the objections to this practice. The only way to get AR5007 support into MadWifi is to make sure that our HAL upstream implements support for these chipsets in his sources and provides us with a updated binary.

(in reply to: ↑ 15 ) 12/03/07 13:36:29 changed by mrenzmann

Replying to genneth _at_ gmail.com:

It seems unnecessary to actually remove the patch... Could the patch not stay up...

The origin of the patch in question was doubtful, it didn't came through the channels we usually receive HAL updates from. The fact that the patch removes Sam's copyright notices from the patched files didn't help to make it look less suspicious.

In the past we had several incidents where users attached leaked HAL sources or other work that made use of illegally distributed files. Since we are responsible for stuff that is offered for download from our server and thus could probably be called to account for the distribution of "illegal files" it was necessary to remove the file. A big fat warning across the file obviously wouldn't have helped us if it turned out that the stuff was not kosher.

We have received feedback from other users stating that the removal of the file seems to them like an over-reaction. I hope the above helps to understand our rationales. We certainly would love to see AR5007 support in MadWifi rather sooner than later, but we have to make sure that this is done "the right way", without exposing ourselves to yet another series of claims about copyright infringements and thelike (even more now that we are working hard on ath5k). This should also be in the best interest of the users of our drivers, even if it means that AR5007 support gets delayed.

Last but not least: meanwhile it was approved that the patch was contributed by Atheros. We are currently talking to them about how to proceed in order to get AR5007 support into MadWifi properly (means: not just for i386, but for all platforms, to prevent ABI breakage). Please stay tuned, we will keep you updated.

12/09/07 16:49:07 changed by cogumbreiro@gmail.com

I tried installing by downloading (1) and applying patch (2) to the source as specified in the description of the bug.

The driver loads up (by calling "modprobe ath_pci"), and then an interface 'wlan0' and an interface 'wifi0' are created. However, no AP are discovered.

Any idea how can I find out what's wrong? Do you want me to send the log.

One interesting fact is that this is the second laptop I have with this wireless card, both laptops are of the same model. The first one I configured wireless with ndiswrapper, this one I cannot get it to work neither with ndiswrapper nor with madwifi.

(1) snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz

(2) madwifi.org/attachment/ticket/1679/madwifi-ng-0933.ar2425.20071130.i386.patch?format=raw

02/01/08 05:40:57 changed by anonymous

After some trouble initially manually patching a newer release, I uninstalled all madwifi builds and used the prepatched snapshot in the ticket description which worked perfectly with no issues (bye bye old cisco PCMCIA card :D :D). Please note that as explained in the ticket the ath5k module (if installed - it is on Fedora 8 and newer kernels I believe) needs to be blacklisted. Simply add blacklist ath5k to /etc/modprobe.conf

I do however have a question which I hope is classed as being in scope for this ticket (as per mrenzmann's coment above!) - can this patch be used with the latest snapshot and would there be any point in doing so? If so, would someone be able to create a prepatched version? I'd try it but after the trouble I have had I don't want to risk killing my config unless its worked for other people first!

Thanks.

(in reply to: ↑ 84 ; follow-up: ↓ 87 ) 02/23/08 05:46:14 changed by anonymous

Replying to mrenzmann:

Note that neither the patch nor the prepatched snapshot tarball compile against kernel 2.6.24. This is a known issue, so no need to report this here. As soon as an update is available, it will be announced here.

I haven't found this to be the case. It's compiled and installed without problem for me in in Fedora's Rawhide, running various versions of 2.6.24 and 2.6.25. (However, an update tonight, to their kernel 2.6.25-0.54.rc2.fc9 doesn't work with it. It compiles and installs, but doing modprobe ath_pci hangs the system.)

The one I had before that, 2.25-0.48.rc1.git2.fc9 worked without problem.

It's also worked without issue in the Ubuntu alphas, 2.6.24.5-generic and 2.6.24-8.generic.

Lastly, it's worked without issue in Arch, kernel 2.6.24-ARCH.

(in reply to: ↑ 86 ) 02/23/08 14:29:31 changed by anonymous

Replying to anonymous:

Replying to mrenzmann:

Note that neither the patch nor the prepatched snapshot tarball compile against kernel 2.6.24. This is a known issue, so no need to report this here. As soon as an update is available, it will be announced here.

I haven't found this to be the case. It's compiled and installed without problem for me in in Fedora's Rawhide, running various versions of 2.6.24 and 2.6.25. (However, an update tonight, to their kernel 2.6.25-0.54.rc2.fc9 doesn't work with it. It compiles and installs, but doing modprobe ath_pci hangs the system.) The one I had before that, 2.25-0.48.rc1.git2.fc9 worked without problem. It's also worked without issue in the Ubuntu alphas, 2.6.24.5-generic and 2.6.24-8.generic. Lastly, it's worked without issue in Arch, kernel 2.6.24-ARCH.

To add to this, the next day's Fedora update, to 2.6.25-0.64.rc2.git5.fc9 works again.

02/24/08 21:31:53 changed by ilredil@yahoo.com

The patch couldn't be cleanly applied to 0.9.4, however the tarball compiled and worked fine. I'm using an acer 5050-3785 with the AR5BXB63 card. I'm using the linux 2.6.24 kernel, and have 64-bit support enabled (Processor type and features -> 64 bit Memory and IO resources). Also, this tarball seems to include injection support (which is awesome) for those who were wondering.

I did, however, get a lot of stacktraces in the logs from dmesg.

sysctl table check failed: /net/ath0/monitor_phy_errors .3.-2.-2 Unknown sysctl binary path
...
sysctl table check failed: /net/ath0/monitor_crc_errors .3.-2.-2 Missing strategy
...
sysctl table check failed: /net/ath0/monitor_crc_errors .3.-2.-2 Unknown sysctl binary path
...
sysctl table check failed: /net/ath0/%parent .3.-2.-2 Missing strategy
...
sysctl table check failed: /net/ath0/%parent .3.-2.-2 Unknown sysctl binary path
...
ath0: failed to register sysctls!
wifi0: Atheros 5424/2424: mem=0xb0200000, irq=11
sysctl table check failed: /dev/ath .7.9 Unknown sysctl binary path
...

If anyone is concerned with the above error message, you'll probably was to know this: grep -i sysctl /usr/src/linux-2.6.24/.config

CONFIG_SYSVIPC_SYSCTL=y
CONFIG_SYSCTL=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_PROC_SYSCTL=y

Personally, I'm not worried about the error messages; the card works, and that's what's most important to me. Thanks for your hard work guys! If you think the errors are worth tracking down, e-mail me and I'll get you whatever information you need.

(in reply to: ↑ 91 ) 02/27/08 05:48:25 changed by simmons.jimmy@gmail.com

Replying to anonymous:

I'm not really sure where this goes, but after a lot of trial and error with other posts, I got the patched version working with my Compaq Presario f750US, Fedora Core 7-i386. As mentioned before lspci listed my card as AR5006EG.

Sorry as a followup: This worked before I installed the nvidia driver, but failed after words. I think it had to do with the new kernel. I had to make a symlink for the new /build file for the new kernel as I was getting a KERNELPATH error:

ln -s /usr/src/kernels/`uname -r`-i686 /lib/modules/`uname -r`/build

This allowed me to make / make install the patched source again. My module still didn't show up so I blacklisted the ath5k module:

echo "blacklist ath5k" >> /etc/modprobe.d/blacklist

Then I rebooted and iwconfig recognized it. Woohoo!

(in reply to: ↑ description ) 03/05/08 07:56:36 changed by b4u68k

Hello,

I get a Segmentation fault when removing the module 'ath_pci', by using either 'rmmod' or 'modprobe -r'. The interface ath0 is first brought down before unloading 'ath_pci'.

Then the system hangs on shutdown after the following messages:

'Killing all remaining processes...Failed.' 'Deconfiguring network interfaces...'

The OS is Debian sid with kernel 2.6.24 running on Asus EEE PC, and r2756 patched with madwifi-ng-0933.ar2425.20071130.i386.patch.

I'd like to post the segfault log (which only shows when 'modprobe -r ath_pci' is done in the "root terminal" before starting X, not in terminal emulators) but I can't record it (even with /usr/bin/script). I didn't find anything in /var/log/* neither.

Here's a testcase which leads to the segfault:

1) boot with wifi led turned of ('echo 0 > /proc/acpi/asus/wlan' before reboot) 2) login root without starting X 3) load pciehp module with option pciehp_force=1 ('modprobe pcihep pciehp_force=1') 4) turn on wifi: 'echo 1 > /proc/acpi/asus/wlan' 5) load ath_pci module: 'modprobe ath_pci' 6) remove ath_pci module: 'modprobe -r ath_pci' (Segmentation fault)

I can provide more if needed, thanks in advance for any help

04/03/08 02:34:08 changed by jebba

This on a 4G asus eeepc. This is using the ath5k driver, not madwifi, HAL, OpenHAL, etc. I hope this info helps you in your development.

2.6.24 kernel as a base (along with a number of other unrelated patches)

(spam prevents urls below...)

Updated wireless:

2008-04-02
linuxwireless dot org download compat-wireless-2.6 compat-wireless-2.6.tar.bz2

Then built ath5k from Nick Kossifidis tarball:

kernel dot org pub linux kernel people mickflemm ath5k-2425-test2.tar.bz2

I had to disable PM in kernel:

CONFIG_PM=no

With the driver loaded dmesg

ath5k phy0: Atheros AR5418 chip found (MAC: 0xe2, PHY: 0x70)

More info with module loaded.

# lspci -d 168c:001c
01:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)

# lspci -vvv
01:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
        Subsystem: Unknown device 1a3b:1026
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 16 bytes
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at fbef0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [60] Express (v1) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
                        ClockPM- Suprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
                Vector table: BAR=0 offset=00000000
                PBA: BAR=0 offset=00000000
        Kernel driver in use: ath5k_pci
        Kernel modules: ath5k

# `lspci -vvv -d 168c:001c | grep Memory`
"Region 0: Memory at fbef0000"
# setpci -s 01:00.0 command=0x41f cache_line_size=0x10

From madwifi-nr-r3366+ar5007/tools/ath_info

# ath_info 0xfbef0000

Warning: Invalid EEPROM Magic number!
 -==Device Information==-
MAC Version:  2425  (0xe0)
MAC Revision: 2425  (0xe2)
PHY Revision: 5110  (0x00)
 -==EEPROM Information==-
EEPROM Version:     5.3
EEPROM Size:        4K
Regulatory Domain:  0x60
 -==== Capabilities ====-
|  802.11a Support: no   |
|  802.11b Support: no   |
|  802.11g Support: yes  |
|  RFKill  Support: yes  |
|  32KHz   Crystal: no   |
 ========================
GPIO registers: CR 00000000 DO 00000000 DI 00000003

I can see the device with iwconfig fine:

# iwconfig ath0
ath0      IEEE 802.11  ESSID:""  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=0 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Encryption key:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

I can change the ESSID:

# iwconfig ath0 essid foo && iwconfig ath0 | grep ESSID && iwconfig ath0 essid bar && iwconfig ath0 | grep ESSID
ath0      IEEE 802.11  ESSID:"foo"  
ath0      IEEE 802.11  ESSID:"bar"

I can change the channel:

# iwconfig ath0 channel 1 && iwconfig ath0 | grep Frequency && iwconfig ath0 channel 6 && iwconfig ath0 | grep Frequency
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated

I can NOT change the mode, garr garr garr:

# iwconfig ath0 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
    SET failed on device ath0 ; Device or resource busy.

Scanning doesn't see anything (there is an open/advertised network here):

# iwlist ath0 scan
ath0      No scan results

04/21/08 17:48:05 changed by alain57

well i don't know if this is normal, but lspci -v give me this

06:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
	Subsystem: AMBIT Microsystem Corp. Unknown device 0428
	Flags: bus master, fast devsel, latency 0, IRQ 19
	Memory at d4100000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] Power Management version 2
	Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [60] Express Legacy Endpoint IRQ 0
	Capabilities: [90] MSI-X: Enable- Mask- TabSize=1

and ath_info 0x4100000 this

Warning: Invalid EEPROM Magic number !
 -==Device Information==-
MAC Version:  5311A(0x20) 
MAC Revision: 5311A(0xe12b) 
PHY Revision: 5110 (0x0) 
 -==EEPROM Information==-
EEPROM Version:     9.6c8 
EEPROM Size:        8K
Regulatory Domain:  0x96C8 
 -==== Capabilities ====-
|  802.11a Support: no   |
|  802.11b Support: no   |
|  802.11g Support: no   |
|  RFKill  Support: no   |
|  32KHz   Crystal: no   |
 ========================
GPIO registers: CR f3fd2aa8 DO 4078376f DI f08e87f3

strange... there are "no" on each lines, but i currently use my wifi with r2756 + patch on ubuntu hardy

ps: last comment in reply to wocis was me too

(follow-up: ↓ 141 ) 04/22/08 00:02:14 changed by Martin

I tried to download the snapshot snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz but unfortunately the link is broker So I tried with the readily-patched snapshot (which link works), I tried with "make", at the beginning the program was unable to detect kernel version, so I replaced line

KERNELRELEASE := $(shell $(CC) -I $(KERNELPATH)/include -E $(TOP)/kernelversion.c | grep uts_release | cut -f2 -d'"') with KERNELRELEASE := /usr/src/linux-2.6.22.17-0.1 at that point exucuting again the program with "make" command I am having the following message:

Checking requirements... ok. Checking kernel configuration... FAILED Only kernel versions 2.4.x and above are supported. You have /usr/src/linux-2.6.22.17-0.1. make: *** [configcheck] Error 1

What can I do?

05/14/08 16:37:42 changed by anonymous

Hi.

I have a "TP-Link WN310G Cardbus Card" here and have no luck to make it work with the patches from this trac entry.

MadWifi: unable to attach hardware: 'No hardware present or device not yet supported' (HAL status 1)

My output from ath_info:

 -==Device Information==-
MAC Version:  2425  (0xf0)
MAC Revision: 2425  (0xf0)
PHY Revision: 5110  (0x00)
 -==EEPROM Information==-
EEPROM Version:     5.3
EEPROM Size:        16K
Regulatory Domain:  0x809C
 -==== Capabilities ====-
|  802.11a Support: no   |
|  802.11b Support: no   |
|  802.11g Support: yes  |
|  RFKill  Support: no   |
|  32KHz   Crystal: no   |
 ========================
GPIO registers: CR 00000000 DO 00000000 DI 00000014

lspci -vvnn:

03:00.0 Ethernet controller [0200]: Atheros Communications Inc. Device [168c:001d] (rev 01)
        Subsystem: Atheros Communications Inc. Device [168c:1055]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0 (2500ns min, 7000ns max), Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at 90000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=2 PME-

Any hints? Thanks in advance.

(follow-up: ↓ 242 ) 07/09/08 12:48:29 changed by anonymous

It worked !
My notebook is Fujitsu Siemens Amilo Pa2548
with Atheros AR5007EG:

03:00.0 Ethernet controller [0200]:
Atheros Communications Inc. AR242x 802.11aless PCI Express Adapter [168c:001c] (rev 01)
Subsystem: Atheros Communications Inc. Unknown device [168c:3067]

Dmesg:

ath_hal: 0.10.2.2-ATHEROS (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425)
ath_pci: 0.9.4.5 (svn r2756)
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LK1E] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:03:00.0 to 64
ath_pci: switching rfkill capability off
ath_rate_sample: 1.2 (svn r2756)
ath_pci: switching per-packet transmit power control off
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP

Kernel 2.6.23-gentoo-r8
Kernel is built with full set of modules ieee80211 (without debug)

"madwifi-ng-r2756-20071018.tar.gz" patched with "I-did-not-read-the-ticket_madwifi-ng-0933.ar2425.20071130.i386.patch"

Download in other formats:

Ticket Navigation

Ticket #1679 (closed enhancement: invalid)

Patch for AR2425 (AR5007EG) chipset

Description (Last modified by mentor)

Attachments

Change History

(follow-up: ↓ 5 ) 12/01/07 03:34:43 changed by madwifi@atheros.com

12/01/07 06:23:53 changed by quagga

12/01/07 11:50:37 changed by nbd

(in reply to: ↑ 1 ) 12/01/07 17:29:48 changed by anonymous

12/01/07 20:10:56 changed by ilj

12/01/07 20:14:00 changed by strasak@bubakov.net

12/01/07 21:10:27 changed by kelmo

12/01/07 22:08:34 changed by ilj

12/01/07 22:20:12 changed by anonymous

12/01/07 23:28:43 changed by madwifi@atheros.com

To apply the patch

12/02/07 08:26:07 changed by kinaeng@gmail.com

(follow-up: ↓ 14 ) 12/02/07 10:50:18 changed by kelmo

(in reply to: ↑ 13 ) 12/02/07 12:40:20 changed by mrenzmann

(follow-up: ↓ 16 ) 12/03/07 12:50:52 changed by genneth _at_ gmail.com

(in reply to: ↑ 15 ) 12/03/07 13:36:29 changed by mrenzmann

12/03/07 15:09:58 changed by AR5007EG user =)

12/03/07 21:58:16 changed by mentor

12/04/07 22:50:51 changed by madwifi@atheros.com

12/05/07 01:20:24 changed by mentor

(in reply to: ↑ description ; follow-up: ↓ 24 ) 12/05/07 15:06:21 changed by anakin

(in reply to: ↑ 23 ) 12/05/07 15:11:53 changed by anonymous

(follow-up: ↓ 28 ) 12/06/07 00:49:56 changed by anonymous

(follow-up: ↓ 27 ) 12/06/07 23:20:36 changed by anonymous

(in reply to: ↑ 26 ) 12/08/07 10:55:32 changed by anonymous

(in reply to: ↑ 25 ) 12/09/07 00:11:53 changed by anonymous

12/09/07 16:49:07 changed by cogumbreiro@gmail.com

12/13/07 00:31:31 changed by anonymous

12/14/07 07:07:21 changed by anonymous

12/14/07 14:58:36 changed by anonymous

12/14/07 15:18:07 changed by strasak@bubakov.net

12/16/07 03:05:03 changed by mrenzmann

(follow-up: ↓ 57 ) 12/18/07 04:43:22 changed by mentor

(in reply to: ↑ 56 ) 12/22/07 01:45:38 changed by anonymous

12/25/07 17:34:54 changed by anonymous

(follow-up: ↓ 60 ) 01/11/08 09:31:54 changed by anonymous

(in reply to: ↑ 59 ; follow-up: ↓ 61 ) 01/11/08 10:00:58 changed by mrenzmann

(in reply to: ↑ 60 ; follow-up: ↓ 62 ) 01/11/08 11:44:15 changed by anonymous

(in reply to: ↑ 61 ) 01/11/08 12:21:20 changed by mrenzmann

01/12/08 17:35:02 changed by anonymous

01/12/08 17:49:12 changed by anonymous

(follow-up: ↓ 68 ) 01/23/08 01:30:39 changed by Need64bitSupport

(in reply to: ↑ 67 ) 01/23/08 05:56:49 changed by mrenzmann

01/23/08 11:15:27 changed by mrenzmann

01/28/08 16:53:12 changed by anonymous

01/30/08 08:45:54 changed by beechhorn@gmail.com

01/30/08 08:49:47 changed by beechhorn@gmail.com

01/31/08 06:03:10 changed by mrenzmann

02/01/08 05:40:57 changed by anonymous

02/03/08 16:47:22 changed by beechhorn@gmail.com

02/06/08 12:48:05 changed by mrenzmann

02/12/08 20:53:39 changed by mentor

02/14/08 22:10:49 changed by migatxu

02/15/08 09:56:15 changed by beechhorn@gmail.com

02/15/08 11:45:23 changed by beechhorn@gmail.com

02/15/08 12:17:02 changed by mrenzmann

02/17/08 01:12:06 changed by dodyrw@gmail.com

(follow-up: ↓ 86 ) 02/20/08 06:04:00 changed by mrenzmann

02/21/08 04:21:04 changed by zhenyu.z.wang@intel.com

(in reply to: ↑ 84 ; follow-up: ↓ 87 ) 02/23/08 05:46:14 changed by anonymous

(in reply to: ↑ 86 ) 02/23/08 14:29:31 changed by anonymous

02/24/08 21:31:53 changed by ilredil@yahoo.com

02/25/08 10:04:41 changed by anonymous

02/25/08 21:25:58 changed by Darksurf

(follow-up: ↓ 92 ) 02/27/08 03:22:12 changed by anonymous

(in reply to: ↑ 91 ) 02/27/08 05:48:25 changed by simmons.jimmy@gmail.com

02/28/08 04:34:26 changed by kevmif@yahoo.com

02/28/08 08:22:22 changed by beechhorn@gmail.com

02/28/08 22:30:21 changed by lukassoftwares a t gmail.com

02/29/08 07:35:21 changed by mrenzmann

02/29/08 09:48:21 changed by beechhorn@gmail.com

02/29/08 10:37:28 changed by beechhorn@gmail.com

02/29/08 14:31:12 changed by kevmif

02/29/08 23:29:02 changed by anonymous