Bugzilla Bug 129894

Added --retain-monitor cmdline option on request
Added setting madwifi-ng to radiotap mode
Fixed several crashes due to not checking noise/junk packet params
Added zd1211 capture source (with warnings)
Fixed madwifi-ng fcs bytes
Fixed madwifi-ng not shutting down rfmon vap
Fixed madwifi_ag with madwifi-ng drivers
Moved ipw3945parasite to ipwlivetap
Moved madwifing support into madwifi standard as an auto-detect
Lots of little tweaks to handle moving sources
Added the initial ipw3945 support.You'll need a current (read: latest) ipw3945
driver.If it doesn't work, let me know.There are no doc entries for this until
I get it officially tested.
Switched ACX100 capture to not expect the FCS bytes.
Added memset 0 to gpsd code to explicity zero the gps data buffer on startup
Added a fix to ringbuf from Shane Schisler
Added extremely experimental support for broadcom 43xx devices (yes, you read
right, broadcom.Look at the README file.)
Changed prism2 header conversion to ignore a broken length field in the
header.Recent versions of madwifi-ng return a garbage length value
(brokenly!).Basic madwifi-ng support restored for now, still very experimental.
Added madwifi-ng support
Fixed off-by-one in packet.cc for terminating null in netbios string, missing
format element in gpsmap error (thanks, David)
Fixed SSID being trimmed sometimes in network protocol
Fixed SSID munging more

Added to portage.

In the future, please do not file enhancement requests for a simple version
bump this soon after release.