2009-09-16 23:49:57

by Nikolai ZHUBR

Subject: 2.6.25 kernel & compat-wireless-2009-09-14

Hello all,

After some more digging I think I've found an incompatibility.

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?


Thank you,
Nikolai

2009-09-16 23:54:44

by Luis R. Rodriguez

Subject: Re: 2.6.25 kernel & compat-wireless-2009-09-14

On Wed, Sep 16, 2009 at 5:56 PM, Nikolai ZHUBR <[email protected]> wrote:
> Hello all,
>
> After some more digging I think I've found an incompatibility.
>
> 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.

Luis

2009-09-17 01:54:25

by Nikolai ZHUBR

Subject: Re[2]: 2.6.25 kernel & compat-wireless-2009-09-14

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);

mutex_init(&rdev->mtx);
mutex_init(&rdev->devlist_mtx);


> Luis