From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 11EFAE0099B; Wed, 26 Nov 2014 11:27:01 -0800 (PST) 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.192.177 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B4EF3E0082F for ; Wed, 26 Nov 2014 11:26:57 -0800 (PST) Received: by mail-pd0-f177.google.com with SMTP id ft15so3345192pdb.36 for ; Wed, 26 Nov 2014 11:26:57 -0800 (PST) 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=zhlvKNLhRFdEY3MzfYUf2JWWrGOODFtV02xjYhQuAAo=; b=fMNGBzKSdIcS+zZWFQkXAaDpaq74pSmm+2BbwHqkP5i6Ueeo5wvPfpE5CAMDfvbT3j fZ2mtVnsIKOAnpSbZs67o5PpK9dv0yb8FtO8Tk7zSyHFsWE5EY6tt9JZEwPRJnHNBQ0N aMs80X/bzOXxgFkwU6MswxrCAZ88YSt2p60p1YEglhR6yEDj/a5FJaN8CmLhX1eohA3v kF3AKWq2bsSK/3NoK/El+ohhgcwZZbWkc2VuW/SCz/FRV2O8CFmrujpqFFxbQ0Xuen8O kMw+OpwN5lMMNlHcl54lV1VnJPoKEytuI0FbDwkfFRkJ5sKYLcMy4TVCPm1amDnAmu5l A2cA== X-Gm-Message-State: ALoCoQlmcD9Rsvg2zDtjxmqRLzAQpL2X/0eUkfv1HBtDiE5RXwTjWqh+afFz9PYlp84QHJlywb+R X-Received: by 10.66.248.36 with SMTP id yj4mr56333114pac.51.1417030017576; Wed, 26 Nov 2014 11:26:57 -0800 (PST) Received: from [192.168.0.139] (wsip-70-184-93-199.ph.ph.cox.net. [70.184.93.199]) by mx.google.com with ESMTPSA id ir2sm5010309pbc.57.2014.11.26.11.26.55 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Nov 2014 11:26:56 -0800 (PST) Message-ID: <5476297E.2080200@boundarydevices.com> Date: Wed, 26 Nov 2014 12:26:54 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Gary Thomas , meta-freescale@yoctoproject.org References: <1412971768-1162-1-git-send-email-eric.nelson@boundarydevices.com> <1416794255-17482-1-git-send-email-eric.nelson@boundarydevices.com> <547616A8.9070908@mlbassoc.com> <547617B1.2090603@mlbassoc.com> In-Reply-To: <547617B1.2090603@mlbassoc.com> Subject: Re: [meta-fsl-arm-extra][PATCH V2] linux-boundary: Add support for kernel 3.10.31_1.1.0_beta 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: Wed, 26 Nov 2014 19:27:01 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi Gary, On 11/26/2014 11:10 AM, Gary Thomas wrote: > On 2014-11-26 11:06, Gary Thomas wrote: >> On 2014-11-23 18:57, Eric Nelson wrote: >>> This patch adds support for the 3.10.31_1.1.0_beta kernelfor Boundary >>> Devices BD-SL-i.MX6 (built to SABRE Lite), Nitrogen6X, Nitrogen6_Max >>> and and Nitrogen6_Lite boards. >>> >>> To try it out, set PREFERRED_VERSION_linux-boundary = "3.10.31" in your >>> local.conf file. >>> >>> Minimal testing has been performed at this point, so don't expect it >>> to be production-ready. >>> >>> Note that the 3.10.31 kernel contains an update to provide fixed >>> numbering for /dev/mmcblk devices instead of numbering them by >>> order of initialization. >>> >>> Support has been added into the boot script, but requires setting >>> a variable in U-Boot: >>> >>> U-Boot > setenv sdphys 1 >>> U-Boot > saveenv >>> U-Boot > boot >>> >>> See this post for some additional commentary: >>> http://boundarydevices.com/root-equals >>> >>> Signed-off-by: Eric Nelson >> >> When I tried this patchset, it fails to boot my SabreLite. The >> important bits seem to be the MMC device numbering. From the boot log: >> >> mmc3: new high speed SDHC card at address aaaa >> mmcblk3: mmc3:aaaa SU04G 3.69 GiB >> mmcblk3: p1 p2 >> >> ALSA device list: >> #0: imx6q-sabrelite-sgtl5000 >> Waiting for root device /dev/mmcblk0p2... >> >> I see no difference when setting 'sdphys' or not. Perhaps I missed some >> other patch (like to the boot scripts)? > > BTW, I'm building the scripts from > u-boot-script-boundary/v2014.07+gitAUTOINC+f870252376 > and there seems to be nothing in there about sdphys > You need this patch to support the 'sdphys' thing in the boot script: http://patches.openembedded.org/patch/83731/ Regards, Eric