This issue appears to have been resolved with the upgrade to 2.6.27. The ath5k now identifies the wireless card as ath0 when it used to identify as wlan0 with 2.6.26.
This issue appears to have been resolved with the upgrade to 2.6.27. The ath5k now identifies the wireless card as ath0 when it used to identify as wlan0 with 2.6.26.