MacCentral (and Yahoo) is reporting that Apple has confirmed what we already know: The AE driver intentionally now works with 3rd party Broadcom-based PCI and CardBus cards.
Apple released AirPort update 3.1 today, and it appears that in addition to final 802.11g standards compliance that Apple has decided to allow their drivers to work with any Broadcom based 802.11g card, be it CardBus or PCI.
Evidence of this can be seen in the stock Info.plist file that comes with the AppleAirPort2.kext. If you look in the <IONameMatch> section, you'll see that it matches Apple's own AE module, and also now pci14e4,4320, which is the chip ID for the Broadcom 802.11g device.
Huzzah! And many thanks to Apple for this unexpected gift!
The XMPCR is the cheapest way to experience XM radio. It's just a box with an XM antenna, a headphone (actually it's line-out) jack, and a USB jack. You plug the USB jack into a PC and run their software to control it.
There's a whole community of XM radio hackers and enthusiasts, and much has been learned about how the XMPCR works.
The XMPCR is nothing more than an XM radio module with it's serial control pins hooked up to an FTDI USB-to-serial adapter.
This is extremely good news! It means that if you install the MacOS X driver, you'll wind up with a /dev/tty.usbserial-mumble device. There are perl scripts that can talk to this device to run the XMPCR from the command line. Huzzah!
In my copious spare time, I am working on a native MacOS X GUI application to replace the Windows software. More info as it becomes available.....
People are starting to post questions to multiple stories, so here's a place you can use as an impromptu forum for getting help.
Some of the most frequent recent questions and their answers:
If the script says that it isn't finding the correct version of the driver, then you need to uncomment one of the other definitions of $patchloc. This number changes every time Apple recompiles the kext. If you have come across a driver that requires a $patchloc not present in the script, let me know so I can add it. You can determine $patchloc for yourself by carefully examining an ASCII dump of the driver file and looking for pci106b in it somewhere.
When you plug any CardBus or PCCard card into your powerbook, you'll see a card menu show up in the menu bar with the option "Power off card" and the name of the card greyed out. This is normal behavior and has no bearing on whether or not a driver is talking to the card.
If you have an old AirPort card installed in your machine and you use the hack to enable a CardBus or PCI 802.11g card, your network preferences will become confused, as you'll have two "AirPort" cards. You should disable the original AirPort driver by renaming /System/Library/Extensions/AppleAirPort.kext and AppleAirPortFW.kext to ....kext.disabled. Then remove the kext cache files and reboot. You'll be back to just one AirPort interface. It would be really nice if Apple would open up its 802.11 configuration interface so that 3rd party 802.11 cards could be configured the same way as Apple's own. It's sort of sickening to realize that in this area Windows XP is more open than OS X.
Make very, very sure that your 802.11g card is based on the Broadcom 802.11g chipset. If it isn't, it's not going to work. Combo A/G cards won't work either.