Re: WL12xx Wi-Fi on 3.10.17_1.0.0_ga release

[Eric Nelson <eric.nelson@boundarydevices.com>]

Hello Barry,

On 08/26/2014 05:10 AM, Mobile Dev wrote:
> 
> 
>> Date: Mon, 25 Aug 2014 08:59:46 -0700
>> From: eric.nelson@boundarydevices.com
>> To: mobiledev@msn.com; meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] WL12xx Wi-Fi on 3.10.17_1.0.0_ga release
>>
>> Hello, ummm... mdev.
>>
>> On 08/22/2014 04:18 PM, Mobile Dev wrote:
>> > Apologies for the length...
>> >
>> > I see that [Eric's] nitrogen6x boundary tree has some devicetree patches
>> > to enable the TI Wi-Fi module. I am trying to bring it up on our custom
>> > board and I have a few questions:
>> >
>>
>> Since you're asking for support, do you mind identifying yourself?
> 
> My name is Barry.
> 
>>
>> > 1. Where did you get the 'calibrate' utility? There are several repos
>> > out there for it.
>>
>> In general, we've found the calibrate utility to be more or less
>> useless, and since it's a pretty big pain to get and compile,
>> we haven't used it in quite a while.
>>
>> > 2. Did you just use the wlcore/wlcore_sdio/wl12xx drivers in the
>> > 3.10.17 kernel tree or did you pull anything from
>> > backports/compat-wireless/TI?
>>
>> You can answer that question by checking the log.
> 
> Which log?
> 

	~/linux-imx6$ git log boundary-imx_3.10.17_1.0.0_ga drivers/net/wireless

...

> 
> I diffed the two trees again and pulled in the rest of the patches that
> looked applicable (http://pastebin.com/2dELkd4z).  The rest appear to be
> video, hdmi, and rfkill related.  The rfkill looked like it was just for
> Bluetooth so I left it out for the moment.
> 

That's like drinking from a fire hose...

>>
>>
>>
>> Are you using our kernel? Have you validated your source
>> tree against a Nitrogen6x or Nitrogen6_Max board?
>>
>> If so, then you should start looking for what's different.
> 
> I am using the freescale kernel and trying to pull Boundary's changes
> in.  Our board is based on the SabreSD and I don't have a Nitrogen board.
> 

That makes life more difficult.

>>
>> >
>> > <snip>
>> >
>> > The second issue is that I can't successfully cycle the wlan0 interface
>> > more than once (ifconfig up, down, up). When I try to bring it up the
>> > second time, I get this:
>> >
>> >
>> > root@custom_board:/lib/firmware/ti-connectivity# ifconfig wlan0 up
>> > wlcore: ERROR timeout waiting for the hardware to complete
>> > initialization
>> > wlcore: ERROR timeout waiting for the hardware to complete
>> > initialization
>> > wlcore: ERROR timeout waiting for the hardware to complete
>> > initialization
>> > wlcore: ERROR firmware boot failed despite 3 retries
>> > ifconfig: SIOCSIFFLAGS: Input/output error
>> > root@custom_board:/lib/firmware/ti-connectivity#
>> >
>> >
>> > I thought it was caused by this
>> > (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258174) so I
>> > changed the SD clock to add a pullup but it didn't work.
>> >
>>
>> This is the primary symptom of not having our patches in place.
> 
> After applying my new patch, I can usually bring the interface up and
> down without issue.  Sometimes I still get this
> <http://pastebin.com/2iLPgUHt> crash/recovery though.  If I just run 'iw
> wlan0 scan' I get no results.
> 

This is really not the kind of thing that can or should
be addressed in this list.

Regards,


Eric