From mboxrd@z Thu Jan 1 00:00:00 1970 From: Li Ye-B37916 Date: Tue, 9 Sep 2014 11:35:21 +0800 Subject: [U-Boot] [PATCH 4/5] iMX6Solo:SABRESD: Add the i.MX6Solo SABRESD board support In-Reply-To: References: <1409638316-22012-1-git-send-email-B37916@freescale.com> <1409638316-22012-4-git-send-email-B37916@freescale.com> <5406C1EE.1000900@freescale.com> Message-ID: <540E7579.3070708@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 9/9/2014 7:41 AM, Otavio Salvador wrote: > On Wed, Sep 3, 2014 at 4:23 AM, Li Ye-B37916 wrote: >> On 9/2/2014 10:06 PM, Fabio Estevam wrote: >>> On Tue, Sep 2, 2014 at 3:11 AM, Ye.Li wrote: >>> >>>> #ifdef CONFIG_SUPPORT_EMMC_BOOT >>>> #define EMMC_ENV \ >>>> "emmcdev=2\0" \ >>>> @@ -146,7 +155,8 @@ >>>> "fi; " \ >>>> "fi\0" \ >>>> EMMC_ENV \ >>>> - "mmcargs=setenv bootargs console=${console},${baudrate} " \ >>>> + "smp=" CONFIG_SYS_NOSMP "\0"\ >>> Why do we need this 'smp' string? >> This "nosmp" is intended for imx6solo on a SMP kernel, which asks SMP kernel to act as UP kernel. If kernel supports to detect the uni-processor or multi-processor with cores number from SCU, this parameter is not necessary . But it is nice to have. How do you think? > is this a real mx6solo processor on this board, or is it a dual-lite > that you only wants to use a single core to 'simulate' a solo? > This is a real mx6solo processor on this board. Your question reminders me this bootarg is indeed for simulation. In fsl release, we provide a feature to simulate the mx6dl for mx6solo. But on a real mx6solo board, this bootarg is unnecessary. Best regards, Ye Li