Atmel has made the drivers completely opensource using the Gnu Public Licence :) This of course is great news. The replacement file as it stands here will not be updated anymore. If people want to use the binary driver they can still pick it up here, but I will not make changes or bugfixes for it.
Go to the project page on sourceforge to get the latest opensource driver. There are already several other bugfixes in there.

I bought myself two Linksys WUSB11 wireless adapters. They are nice little things that connect to a USB port and give me free range of the house with my laptop. So yes I like them a lot.

The Linux drivers are mostly binary only and can be picked up here. You will need Linux kernel 2.4.19-rc3 at least to get them running. Furthermore I had some problems with the two different UHCI drivers that exist in the Linux kernel. On my desktop I can use either of them, on my IBM thinkpad I can only use the uhci.o driver.

The other thing that I did not like was the configuration had to be set using a GUI program (curses controlled or Xwindows). Both interfaces looked good and worked fine. But I wanted something that I could control from a script. Jean Tourrilhes invented the Wireless Extensions for Linux. This is a common API into wireless appliances.
The part of the driver that handles the ioctl calls for the ATMEL device luckily was supplied as source and already had some hooks for the wireless tools. Alas, they were incorrect. I started hacking into them and made part of it working (the part I needed first).

The modified file vnetusba.c is a drop-in replacement for the original file. Just replace the original file with this one and recompile. All the functionality from the two GUI programs (lvnet and xvnet) is still there.

In the coming day I will start playing with the WEP settings and see if I can get them to work with the wireless tools too. Watch this space or join the atmel maillinglist. DONE, They are now partly working.
Still to do:

• make the rest of the wepsettings work (switching keys by index)
• check the other wireless extensions options like power, txpower, rate
• look into the setup.sh script