From: Ian Schram <ischram@telenet.be>
To: Norbert Preining <preining@logic.at>
Cc: linux-wireless@vger.kernel.org,
ipw3945-devel <ipw3945-devel@lists.sourceforge.net>
Subject: Re: [ipw3945-devel] [RFC][PATCH] iwlwifi using mac80211_leds
Date: Tue, 23 Oct 2007 13:41:04 +0200 [thread overview]
Message-ID: <471DDDD0.4060007@telenet.be> (raw)
In-Reply-To: <loom.20071023T104428-443@post.gmane.org>
Norbert Preining wrote:
> Zhu Yi <yi.zhu@...> writes:
> aven't have enough time to review this patch these days. Will
>> try to do it next week. But any test are always welcome!
>
> I would like to, is there a way to patch this into the git sources?
the intellinuxwireless.org gits? to make it work it would require an update
of the mac80211 package, and compatibility with older kernels is probably
pretty nasty.
>
> I am running 2.6.23 with latest iwlwifi git sources.
>
> I patched the git sources and started compiling with -DCONFIG_IWLWIFI_LEDS=y but
> the compile boiled out with:
> /src/wlan/iwlwifi/foo/compatible/iwl3945-base.c:6218: error: implicit
> declaration of function 'ieee80211_get_assoc_led_name'
> (and some more warnings).
>
the association led is only in the very latest git sources, i'm guessing only
wireless-2.6 for now.
(also i have learned that i forgot to ifdef the INIT_DELAYED_WORK, I must really try to
beat this inability of sending a patch right the first time round)
i bet an iwl_is_ready(priv) call in the delayed work wouldn't hurt either,
anyway. It works for me feel free to improve it. Or wait until one of
seasoned developers, has no higher priority items on their list.
> Is there anything I can do to test it?
>
> Best wishes
>
> Norbert
>
I'll try to send a patch a bit later today to fix a few of the outstanding issues.
next prev parent reply other threads:[~2007-10-23 11:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 18:00 [RFC][PATCH] iwlwifi using mac80211_leds Ian Schram
2007-10-17 23:21 ` [ipw3945-devel] " Tomas Winkler
2007-10-18 1:45 ` Ian Schram
2007-10-23 6:11 ` Jerone Young
2007-10-23 6:15 ` Zhu Yi
2007-10-23 10:46 ` Norbert Preining
2007-10-23 11:41 ` Ian Schram [this message]
2007-10-23 11:43 ` Norbert Preining
2007-10-23 12:36 ` maximilian attems
2007-10-24 0:34 ` Ian Schram
2007-10-25 13:09 ` Norbert Preining
2007-11-08 6:10 ` Norbert Preining
-- strict thread matches above, loose matches on Subject: below --
2007-10-27 0:22 Ian Schram
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=471DDDD0.4060007@telenet.be \
--to=ischram@telenet.be \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=preining@logic.at \
/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).