On Thu, 2009-09-17 at 06:01 +0300, Nikolai ZHUBR wrote: > Thursday, September 17, 2009, 2:54:28 AM, Luis R. Rodriguez wrote: > >> device_add in 2.6.25.20 wants some bus_id, but bus_id seems to not > >> be assigned anymore, so device_add fails. Therefore, wiphy_register > >> fails, and then clearly ieee80211_register_hw fails too. > >> > >> Any ideas how to properly fix this? > > > FIgure out what the bus_id is used for first. > > Hmm, don't know, but the following helps and wlan0 appears: > > --- everything.orig/net/wireless/core.c 2009-09-16 23:45:40.000000000 +0400 > +++ everything/net/wireless/core.c 2009-09-16 23:48:22.000000000 +0400 > @@ -350,6 +350,7 @@ > > /* give it a proper name */ > dev_set_name(&rdev->wiphy.dev, PHY_NAME "%d", rdev->wiphy_idx); > + snprintf(rdev->wiphy.dev.bus_id, BUS_ID_SIZE, PHY_NAME "%d", rdev->wiphy_idx); Isn't that exactly what dev_set_name() is/was supposed to do? johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
