Luis R. Rodriguez wrote: > On 9/20/07, Stephen Hemminger <shemminger@xxxxxxxxxxxxxxxxxxxx> wrote: >> On Thu, 20 Sep 2007 11:34:29 -0400 >> "Luis R. Rodriguez" <mcgrof@xxxxxxxxx> wrote: >> >>> On 9/20/07, Stephen Hemminger <shemminger@xxxxxxxxxxxxxxxxxxxx> wrote: >>>> On Thu, 20 Sep 2007 15:11:23 +0200 >>>> Michael Buesch <mb@xxxxxxxxx> wrote: >>>> >>>>> On Thursday 20 September 2007, Luis R. Rodriguez wrote: >>>>>> On 9/20/07, Stephen Hemminger <shemminger@xxxxxxxxxxxxxxxxxxxx> wrote: >>>>>>> Network manager doesn't seem to detect ath5k. Perhaps it is because >>>>>>> it is name "ath0". I think device should follow the convention of using >>>>>>> name "wifi0" rather than BSD convention of putting driver name in device name. >>>>>> I couldn't agree anymore. But my ath5k kicks out a wlan%d name as with >>>>>> any other mac80211 driver. Is yours coming out to ath%d ? >>>>>> >>>>>> ieee80211_register_hw(): >>>>>> >>>>>> /* add one default STA interface */ >>>>>> result = ieee80211_if_add(local->mdev, "wlan%d", NULL, >>>>>> IEEE80211_IF_TYPE_STA); >>>>>> >>>>> >>>>> Probably udev renames it. >>>> It was udev, don't know why Ubuntu was adding a rule for it (and getting wrong) >>>> value. >>>> >>> CC' TIm >>> >>> Was it a rule by PCI ID? If so then perhaps its based on the old >>> madwifi rules of sticking to ath%d notation as well. This can be >>> removed for ath5k but not too sure how this works. >>> >> It was by PCI ID > > Then I guess that rule should be removed from udev because of ath5k, > if we let the driver pick the name then we'd get ath%d for madwifi > driver and wlan%d for ath5k. Would help with troubleshooting too. Tim? > :-) > > Luis Keeping the names unique makes sense to me, especially in the case where both drivers are present in the distro, as will likely be the case until ath5k fully matures. I'll research the udev rule... rtg -- Tim Gardner tim.gardner@xxxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
