From mboxrd@z Thu Jan 1 00:00:00 1970 From: Baruch Siach Date: Sun, 12 Jan 2020 18:34:55 +0200 Subject: [PATCH 10/10] arm: mvebu: clearfog: don't assume MMC booting In-Reply-To: <4524882422e2f769b54f3c4b6cd847ad@lixil.net> References: <20200111193639.19022-1-mrjoel@lixil.net> <20200111193639.19022-10-mrjoel@lixil.net> <87lfqdymnv.fsf@tarshish> <4524882422e2f769b54f3c4b6cd847ad@lixil.net> Message-ID: <87blr8zl8w.fsf@tarshish> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Joel, On Sun, Jan 12 2020, Joel Johnson wrote: > On 2020-01-12 03:49, Baruch Siach wrote: >> On Sat, Jan 11 2020, Joel Johnson wrote: >>> +config SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR >>> + hex "Address on the MMC to load U-Boot from" >>> + default 0x141 >>> + depends on MVEBU_SPL_BOOT_DEVICE_MMC >> >> You might want to take a look at the series linked below, which >> conflicts with this patch: >> >> https://patchwork.ozlabs.org/project/uboot/list/?series=121894 > > Indeed, the dynamic runtime approach seems much nicer for handling the MMCSD > offset business, including relative vs. absolute device offset. I only have > non-eMMC units so can't test it, but I'm all for dropping the > SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR portion of this patch in favor of that patch, > in which leaving the defconfig entry does no harm. Any indication of when that > patch will be included? It seems to have been stagnant for a while. Indeed. I'm waiting patiently. baruch -- http://baruch.siach.name/blog/ ~. .~ Tk Open Systems =}------------------------------------------------ooO--U--Ooo------------{= - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -