Implementing 802.11 with Microcontrollers: Wireless Networking for Embedded Systems Designers

Thus far this 802.11b stuff has been an easy ride and believe it or not, it won't get any more difficult. This chapter will show you what's behind the 802.11b functional building blocks that form the basis of the AirDrop-A and AirDrop-P 802.11b drivers.
When I was a kid (a loooong time ago), Legos were made from wood and instead of constructing plastic motorized robots, I constructed luxurious miniature log cabins. The trick to learning to build little log cabins with Legos was knowing which logs to use on a particular part of the cabin. The same idea holds true for being successful with the components of the AirDrop embedded 802.11b driver. You've already been exposed to some of the AirDrop 802.11b driver "wood" by way of the CompactFlash I/O routines. The AirDrop 802.11b driver concepts that will be presented in this chapter will complete your 802.11b CompactFlash NIC I/O education and leave you with a big pile of 802.11b "wood" to work with.
When you're finished with this chapter, understanding the rest of the AirDrop 802.11b driver code will be like building Lego log cabins, child's play. With that, let's begin with some definitions of terms you'll see all over the AirDrop 802.11b code and any Linux 802.11b driver code you care to study.
A BAP, or Buffer Access Path, is the sole method of microcontroller, and ultimately, human interaction with the internal memory management subsystems of the PRISM chipset. Without a BAP, you would have to know...