All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolai ZHUBR <zhubr@mail.ru>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re[2]: 2.6.25 kernel & compat-wireless-2009-09-14
Date: Thu, 17 Sep 2009 06:01:19 +0300	[thread overview]
Message-ID: <142272111.20090917060119@mail.ru> (raw)
In-Reply-To: <43e72e890909161654x141f48e4q54f0526bf6c04ea3@mail.gmail.com>

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



  reply	other threads:[~2009-09-17  1:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  0:56 2.6.25 kernel & compat-wireless-2009-09-14 Nikolai ZHUBR
2009-09-16 23:54 ` Luis R. Rodriguez
2009-09-17  3:01   ` Nikolai ZHUBR [this message]
2009-09-17  2:04     ` Re[2]: " Johannes Berg
2009-09-17  3:38       ` Re[4]: " Nikolai ZHUBR
  -- strict thread matches above, loose matches on Subject: below --
2009-09-17 13:22 Nikolai ZHUBR
2009-09-17 12:57 ` Luis R. Rodriguez
2009-09-17 16:29   ` Re[2]: " Nikolai ZHUBR

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=142272111.20090917060119@mail.ru \
    --to=zhubr@mail.ru \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.