Project: Camphor

Testing still remains, but the coding part is done.

Some statistics:

• Lines of Code — Total: 2736, VoodooWireless only: 2200, VoodooWireless Ciphers only: 536 (WEP encryption only right now, decryption and WPA to be added later)

• Time taken: 58 hr 45 min

• Lines of code / hour = about 46

The API is basically finalized and I don’t envision any changes immediately, except of course when new features like WPA, hardware crypto, .11n or Ad-Hoc mode are added. For a first version I decided to only implement .11b/g (.11a will come soon) connections with WEP in Infrastructure mode. This should cover a lot of users already.

A clipping of the eight (8) hardware-specific functions that HAL writers will need to implement —

Next in line are:

1. Port over the existing 2200BG driver to VoodooWireless and make sure no bugs remain in it. Now I know people will be up in arms about this, but there is no other way to test that the VoodooWireless code actually works. This might take a day or two.

2. When I’m convinced the code works, I’ll port over the FreeBSD wpi driver for the 3945ABG card. This will probably take 4 or 5 days.

Looking for 3945 testers

Now, something important. The inevitable has happened and I no longer have access to the 3945 card anymore. That means I’ll need to code it blind and rely on external testers. Coding part shouldn’t be that difficult anymore (I hope), but the testing probably will be so.

I’m looking for 2 or 3 experienced testers for 3945. The criterion is that you should have a good understanding of how OS X works, how wireless networks work, and how to debug driver issues (e.g. I will not tell you how to load the test drivers, or what to do when you get a kernel panic, or how to change your router settings). The second criterion is that you must be available and able to respond to emails and send test results fast. I’m talking 10 test versions of the driver a day, or something in its vicinity. I usually test drivers 20 times a day! If I rely on external testers, I don’t want to be waiting all day for a test report.

If you think you fit the criteria, and want to help with testing, write me an email at voodoo@mercurysquad.com. I am expecting a lot of messages; so to help me pick, please include any past testing/coding experience or similar information.

NOTE: Just to stay clear, there is NO alpha or beta driver for 3945 yet! The coding/testing will run in parallel all this week.