On Monday 15 May 2006 15:35, you wrote: > [removed some people from Cc: list as this is probably not much > interesting for them] > > On Mon, 15 May 2006 14:04:44 +0200, Johannes Berg wrote: > > On Mon, 2006-05-15 at 13:37 +0200, Jiri Benc wrote: > > > bcm43xx does that. If I understand it correctly, bcm43xx driver doesn't > > > know allowed modes until it loads firmware. And the firmware is not > > > loaded until the device is opened (they probably have a reason for > > > this). > > > > No, that's not right, the firmware has nothing to do with it. At least > > not that we know of, so we treat it as all doing the same :) > > Hm, so your calls to ieee80211_update_hw are probably unnecessary.
No, We must allocate the ieee80211_hw, before we can attach the board. But before we attached the board, we don't know what hardware it is. Sure, this can be worked around by some very ugly hack (It was done in an early version of the dscape port, because there was no ieee80211_update_hw), but I am not very happy to add the hack again. (I am not sure anymore _what_ we actually did to workaround it. I would have to look up the SVN repository ;) ) - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
