From: "raghunath" <raghunath@airvod.com>
To: "'Levi, Shahar'" <shahar_levi@ti.com>,
"'Luciano Coelho'" <luciano.coelho@nokia.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: RE: Ti's WL1271 on OMAP3EVM board with kernel version 2.6.36
Date: Fri, 12 Nov 2010 14:32:29 +0530 [thread overview]
Message-ID: <000101cb8248$579d3d90$06d7b8b0$@com> (raw)
In-Reply-To: <AC090B9732AB2B4DB7FF476E907FE6600113BB263C@dnce02.ent.ti.com>
Hi Shahar/Luca,
Its constantly coming, I am building wl1271 sdio driver statically and I am running on OMAP3EVM board from Mistral
And running 2.6.36 kernel and wl1271 sits on MMC2 I have modified code to set PIN MUX and clock for MMC2 and WLAN_EN(GPIO 150)
And WLAN_IRQ(GPIO-149). I am able to download firmare successfully and get Static data from firmware and Chip ID after firmware
Download. With this I am assuming that code I modified for MMC2 on EVM is proper(correct me if I am worng) after that ware is
Failing ,in ELP wake up.
[ 2.603698] wl1271: acx ac cfg 1 cw_ming 31 cw_max 1023 aifs 7 txop 0
[ 2.603698] wl1271: cmd configure
[ 2.604125] wl1271: acx tid config
[ 2.604156] wl1271: cmd configure
[ 2.604583] wl1271: mac80211 bss info changed
[ 2.604644] wl1271: mac80211 configure filter
[ 2.604644] wl1271: mac80211 configure filter Airvod 1
[ 2.604675] wl1271: acx group address tbl
[ 2.604675] wl1271: cmd configure
[ 2.605133] wl1271: mac80211 configure filter Airvod 2
[ 2.605224] AIRVOD __dev_change_flags net/core/dev.c ret = 0
[ 2.611450] wl1271: elp work
[ 2.611480] wl1271: chip to elp
[ 2.611541] wl1271: mac80211 configure filter
[ 2.611541] wl1271: waking up chip from elp
[ 3.108551] wl1271: ERROR ELP wakeup timeout!
Raghu
-----Original Message-----
From: linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-owner@vger.kernel.org] On Behalf Of Levi, Shahar
Sent: Friday, November 12, 2010 12:47 PM
To: raghunath; 'Luciano Coelho'
Cc: linux-wireless@vger.kernel.org
Subject: RE: Ti's WL1271 on OMAP3EVM board with kernel version 2.6.36
> -----Original Message-----
> From: linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-
> owner@vger.kernel.org] On Behalf Of raghunath
> Sent: Friday, November 12, 2010 7:47 AM
> To: 'Luciano Coelho'
> Cc: linux-wireless@vger.kernel.org
> Subject: RE: Ti's WL1271 on OMAP3EVM board with kernel version 2.6.36
>
> I am using firmware version "wl1271: firmware booted (Rev 6.1.0.0.343)"
>
> Raghu
do you get it constantly or randomly?
Regards,
Shahar
N�����r��y���b�X��ǧv�^�){.n�+����{��*ޕ�,�{ay�\x1dʇڙ�,j
��f���h���z�\x1e�w���
���j:+v���w�j�m����
����zZ+�����ݢj"��!
next prev parent reply other threads:[~2010-11-12 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 11:16 Ti's WL1271 on OMAP3EVM board with kernel version 2.6.36 raghunath
[not found] ` <AANLkTikZD_1DUqkxQyGSLdaQS01Qg15+_TDkW3QuRuOt@mail.gmail.com>
2010-11-11 11:56 ` Luciano Coelho
2010-11-11 14:51 ` raghunath
2010-11-11 15:09 ` Luciano Coelho
2010-11-12 5:46 ` raghunath
2010-11-12 7:16 ` Levi, Shahar
2010-11-12 9:02 ` raghunath [this message]
2010-11-12 10:58 ` Arik Nemtsov
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='000101cb8248$579d3d90$06d7b8b0$@com' \
--to=raghunath@airvod.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@nokia.com \
--cc=shahar_levi@ti.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).