From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 64A4BE00809; Tue, 26 Aug 2014 07:37:53 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.220.46 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B1816E007F6 for ; Tue, 26 Aug 2014 07:37:46 -0700 (PDT) Received: by mail-pa0-f46.google.com with SMTP id lj1so23400404pab.33 for ; Tue, 26 Aug 2014 07:37:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9CX1fNGqyLZbKl5DiDoUwZGdODC88IrBmF9FJlyIvf4=; b=IcsOFZc4rf6i6NkTUVYDz96B3eZJcwmYoAcu06U/edzjQWniAIOIPYu0lbH5n9rGjd njnNMveVHIDkr0cOOF1/QmYczopM2xAQP/QYpphNTr0LXMhayfBy7ZaOdKrxRnQcMBbR h1I4CjkFq+jsHJD5wlFZT3hVO4zq+eA1HPvYt8XsxbNl1mfFfuxKVFCQt7y37cDvoALj NCo/rEGTnIM3mrt6HrOHaMqAXg2eNJ2Wv97n5Xgmm3k2DmAwzRSpeOszvKUVSAc1PHEL +JfEIC4vqBbB/ThIPs0T1juImimtKB3kXhPrSu7rYLTAsNNmlU6S6Bp/V7hYDDW8o7hm ni0A== X-Gm-Message-State: ALoCoQkDNuzgmtXAtBrWVQQkYHEWHboVaTfUEo9viar35Y8PGhxocWFguK0mVpl56+I66z377OhO X-Received: by 10.70.49.2 with SMTP id q2mr37987482pdn.28.1409063864900; Tue, 26 Aug 2014 07:37:44 -0700 (PDT) Received: from [192.168.1.7] (ip98-165-98-97.ph.ph.cox.net. [98.165.98.97]) by mx.google.com with ESMTPSA id i8sm3413416pbq.17.2014.08.26.07.37.43 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Aug 2014 07:37:43 -0700 (PDT) Message-ID: <53FC9BB5.80201@boundarydevices.com> Date: Tue, 26 Aug 2014 07:37:41 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Mobile Dev , "meta-freescale@yoctoproject.org" References: , <53FB5D72.2060408@boundarydevices.com> In-Reply-To: Subject: Re: WL12xx Wi-Fi on 3.10.17_1.0.0_ga release X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2014 14:37:53 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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. >> >> > >> > >> > >> > 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 > 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