From: Hauke Mehrtens <hauke@hauke-m.de>
To: Bing Zhao <bzhao@marvell.com>
Cc: "mcgrof@gmail.com" <mcgrof@gmail.com>,
"lrodriguez@atheros.com" <lrodriguez@atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Frank Huang <frankh@marvell.com>,
Kiran Divekar <dkiran@marvell.com>,
Marc Yang <yangyang@marvell.com>
Subject: Re: [PATCH 1/5] compat-wireless: add support for mwifiex
Date: Fri, 01 Apr 2011 00:01:44 +0200 [thread overview]
Message-ID: <4D94F9C8.9060804@hauke-m.de> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F704307FA844A89@SC-VEXCH1.marvell.com>
Hi Bing,
On 03/31/2011 11:34 PM, Bing Zhao wrote:
>> Subject: [PATCH 1/5] compat-wireless: add support for mwifiex
>>
>> This adds support for mwifiex into compat-wireless.
>>
>> This is only compile tested as I do not have such a device.
>
> Hi Hauke and Luis,
>
> I'm getting an error in "compat-wireless-2.6.39-rc1-3-s/net/wireless/util.c:799" while compiling compat-wireless-2.6.39-rc1-3-s.tar.bz2.
mwifiex is not integrated in the last compat-wireless release from today
it will be in compat-wireless-2011-04-01.
The kernel version number in the compat-wireless release is the version
the code is from. So compat-wireless-2.6.39-rc1-3-s is based on the
source code from kernel version 2.6.39-rc1, it should compile and work
with every kernel from 2.6.24 to 2.6.39.
You could build your own version based on the latest version of
linux-next. It is described at:
http://wireless.kernel.org/en/users/Download/hacking
I created a self made version with the lasted fixes for compat-wireless
and and mwifiex at:
http://hauke-m.de/fileadmin/openwrt/compat-wireless-2011-03-31-1.tar.bz2
> /home/bzhao/git-10.80.114.125/mwifiex-devel/compat-wireless-2.6.39-rc1-3-s/config.mk:204: "WARNING: CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface like iwconfig will not work. To activate it build your kernel e.g. with CONFIG_LIBIPW=m."
This just says that the wext interface will not work, because your
kernel was compiled with CONFIG_WIRELESS_EXT=n, if you do not need wext
just ignore it otherwise compile your kernel with CONFIG_WIRELESS_EXT
enabled.
> /home/bzhao/git-10.80.114.125/mwifiex-devel/compat-wireless-2.6.39-rc1-3-s/net/wireless/util.c: In function 'cfg80211_change_iface':
> /home/bzhao/git-10.80.114.125/mwifiex-devel/compat-wireless-2.6.39-rc1-3-s/net/wireless/util.c:799: error: implicit declaration of function 'br_port_exists'
> make[3]: *** [/home/bzhao/git-10.80.114.125/mwifiex-devel/compat-wireless-2.6.39-rc1-3-s/net/wireless/util.o] Error 1
> make[2]: *** [/home/bzhao/git-10.80.114.125/mwifiex-devel/compat-wireless-2.6.39-rc1-3-s/net/wireless] Error 2
> make[1]: *** [_module_/home/bzhao/git-10.80.114.125/mwifiex-devel/compat-wireless-2.6.39-rc1-3-s] Error 2
> make: *** [modules] Error 2
This is a bug which will be fixed in the next release. ;-)
Build your own compat-wireless version from git, wait till tomorrow or
use my version at this will be fixed.
Hauke
next prev parent reply other threads:[~2011-03-31 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 16:22 [PATCH 1/5] compat-wireless: add support for mwifiex Hauke Mehrtens
2011-03-31 16:22 ` [PATCH 2/5] compat-wireless: backport threaded irq for wl12xx_spi Hauke Mehrtens
2011-03-31 16:22 ` [PATCH 3/5] compat-wirless: deactivate PM support for libertas_spi for kernel < 2.6.29 Hauke Mehrtens
2011-03-31 16:22 ` [PATCH 4/5] compat-wireless: fix compile warning for wl12xx Hauke Mehrtens
2011-03-31 16:22 ` [PATCH 5/5] compat-wireless: clean up the config file Hauke Mehrtens
2011-03-31 19:23 ` [PATCH 1/5] compat-wireless: add support for mwifiex Luis R. Rodriguez
2011-03-31 19:28 ` Bing Zhao
2011-03-31 21:34 ` Bing Zhao
2011-03-31 22:01 ` Hauke Mehrtens [this message]
2011-03-31 22:53 ` Bing Zhao
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=4D94F9C8.9060804@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=bzhao@marvell.com \
--cc=dkiran@marvell.com \
--cc=frankh@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mcgrof@gmail.com \
--cc=yangyang@marvell.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.