From: Nikolai ZHUBR <zhubr@mail.ru>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Senthil Balasubramanian <senthilkumar@atheros.com>,
Gaurav Jauhar <gaurav.jauhar@atheros.com>
Subject: Re[2]: 2.6.25 kernel & compat-wireless-2009-09-14
Date: Thu, 17 Sep 2009 19:29:12 +0300 [thread overview]
Message-ID: <2815684212.20090917192912@mail.ru> (raw)
In-Reply-To: <43e72e890909170557nf991a02n3e268f5c0e416fb0@mail.gmail.com>
Thursday, September 17, 2009, 3:57:10 PM, Luis R. Rodriguez wrote:
> On Thu, Sep 17, 2009 at 6:22 AM, Nikolai ZHUBR <zhubr@mail.ru> wrote:
>> Hello people,
>>
>> So finally I got it mostly working and usable as AP:
>>
>> Hardware:
>> * ASUS WL-500gP (mips) with stock wireless card removed (broadcom).
>> * New shining Ralink RT2600 Mini-PCI card
>> Software:
>> * kernel 2.6.25.20 (openwrt 8.09.1)
>> * compat-wireless-2009-09-14 (without rfkill_backport and with ugly bus_id fix)
>> libnl-1.1
>> hostapd 0.6.9
>>
>> The led is now even blinking nicely.
>> Strange though that selecting static IP in the client didn't work,
>> but using DHCP works fine (it's ok for me now).
> That's great! Care to send some patches for this?
Well, it appears the only thing that really needs fixing is dev_set_name()
compatability function, but fixing it properly without making things worse
is a bit beyond my capability at this point. I think someone more familiar
with the code should have a look (a hint is below).
Regarding rfkill_backport, the issue is probably openwrt-specific, becase
there seems to be no way to load modules with circular dependencies without
modprobe (as far as I understand it). Commenting out CONFIG_RFKILL_BACKPORT
in config.mk "fixes" this and I think this issue can not be easily solved
inside compat-wireless package.
Nikolai
--- 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
next prev parent reply other threads:[~2009-09-17 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 13:22 2.6.25 kernel & compat-wireless-2009-09-14 Nikolai ZHUBR
2009-09-17 12:57 ` Luis R. Rodriguez
2009-09-17 16:29 ` Nikolai ZHUBR [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-17 0:56 Nikolai ZHUBR
2009-09-16 23:54 ` Luis R. Rodriguez
2009-09-17 3:01 ` Re[2]: " Nikolai ZHUBR
2009-09-17 2:04 ` Johannes Berg
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=2815684212.20090917192912@mail.ru \
--to=zhubr@mail.ru \
--cc=gaurav.jauhar@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=senthilkumar@atheros.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).