From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans de Goede Date: Mon, 06 Oct 2014 16:23:36 +0200 Subject: [U-Boot] [PATCH 4/6] sunxi: When we've both mmc0 and mmc2, detect from which one we're booting In-Reply-To: <1412584414.12695.48.camel@hellion.org.uk> References: <1412348759-4599-1-git-send-email-hdegoede@redhat.com> <1412348759-4599-5-git-send-email-hdegoede@redhat.com> <1412411754.17796.60.camel@hellion.org.uk> <54315F71.7070609@redhat.com> <1412584414.12695.48.camel@hellion.org.uk> Message-ID: <5432A5E8.3040706@redhat.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, On 10/06/2014 10:33 AM, Ian Campbell wrote: > On Sun, 2014-10-05 at 17:10 +0200, Hans de Goede wrote: >> >> On 10/04/2014 10:35 AM, Ian Campbell wrote: >>> On Fri, 2014-10-03 at 17:05 +0200, Hans de Goede wrote: >>>> sunxi SOCs can boot from both mmc0 and mmc2, detect from which one we're >>>> booting, and make that one "mmc dev 0" so that a single u-boot binary can >>>> be used for both the onboard eMMC and for external sdcards. >>> >>> Where does the dependency on dev 0 being the boot device come from? Is >>> it just the env via CONFIG_SYS_MMC_ENV_DEV? >> >> No, the main reason why we need dev 0 to be the mmc we're actually booting >> from is because that is where the SPL will load the tertiary payload >> (the actual u-boot binary in our case) from, see: >> >> common/spl/spl_mmc.c >> >> Which has dev 0 hardcoded everywhere. > > I see. Could you paste this bit of reasoning into the commit log please? > (pretty much s/No, t/T/ on the above would do IMHO) Done for v2. Regards, Hans