On Fri, Nov 14, 2008 at 3:13 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: > On Fri, Nov 14, 2008 at 12:41 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: >> On Fri, Nov 14, 2008 at 12:33 PM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: >>> On Fri, Nov 14, 2008 at 2:33 PM, Dan McGee <dpmcgee@xxxxxxxxx> wrote: >>>> On Fri, Nov 14, 2008 at 12:37 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: >>>>> On Fri, Nov 14, 2008 at 10:33 AM, Sujith <m.sujith@xxxxxxxxx> wrote: >>>>>> Luis R. Rodriguez wrote: >>>>>>> > From the original log: >>>>>>> > ath5k_pci 0000:01:00.0: registered as '' >>>>>>> >>>>>>> That comes from >>>>>>> >>>>>>> dev_info(&pdev->dev, "registered as '%s'\n", wiphy_name(hw->wiphy)); >>>>>>> >>>>>>> which means that may be buggy too as wiphy_name() gets >>>>>>> >>>>>>> return wiphy->dev.bus_id; >>>>>>> >>>>>>> and we only have set at that point wiphy->dev.parent IIRC. >>>>>>> >>>>>> >>>>>> Nope, parent is set after that call in SET_IEEE80211_DEV() >>>>>> phy[x] gets assigned in alloc_hw(). >>>>>> >>>>>> So why is it NULL even if alloc_hw() succeeds ? >>>>> >>>>> Parent is wiphy->dev.parent not wiphy->dev though >>> >>> Sujith is right, wiphy->dev.bus_id should be set by the time that's printed, >>> since wiphy_new in alloc_hw fills it in. >> >> Ah, I see, yes, oh man. Well this is good :) > > OK then try the patch in the other thread. If that doesn't fix it then > it has to be another issue. Can someone point me to the "other thread"? I don't think I was CCed on it since I came late to the party. Someone also inquired about versions. I'm using stable kernel 2.6.27.6 and compat-wireless-2008-11-13 (10-28 was doing the same thing however). -Dan -- 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
