From: Baruch Siach <baruch@tkos.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/6] mvebu: select boot device at SoC level
Date: Mon, 06 Aug 2018 13:12:12 +0300 [thread overview]
Message-ID: <871sbbdcsj.fsf@tkos.co.il> (raw)
In-Reply-To: <e220e3e659ae8e6e3404c61a9287824448aab5e3.camel@ausil.us>
Hi Dennis,
Thanks for taking the time to look into this series.
Dennis Gilmore writes:
> this patch needs to be rebased on git master as it does not apply.
The conflict is trivial for git to handle automatically on rebase
(remove, remove). I assume 'git am -3' can do the same. Would you like
me to send v2 of this series for that?
baruch
> El lun, 18-06-2018 a las 21:56 +0300, Baruch Siach escribió:
>> Move the gdsys Controlcenter DC specific build time kwbimage.cfg
>> generation code into the mach-mvebu/ directory to be shared by all
>> 32bit
>> mvebu platforms.
>>
>> Remove board specific kwbimage.cfg files, and use the generated one
>> instead. These files are all identical, with two exceptions. Clearfog
>> and Helios4 use the sdio boot device, whereas all others use spi.
>> Update
>> the defconfigs for the exceptional boards to generate the same
>> kwbimage.cfg as before.
>>
>> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>> ---
[...]
>> diff --git a/configs/helios4_defconfig b/configs/helios4_defconfig
>> index b72428555d37..27e661debe0b 100644
>> --- a/configs/helios4_defconfig
>> +++ b/configs/helios4_defconfig
>> @@ -5,9 +5,9 @@ CONFIG_SPL_LIBCOMMON_SUPPORT=y
>> CONFIG_SPL_LIBGENERIC_SUPPORT=y
>> CONFIG_SYS_MALLOC_F_LEN=0x2000
>> CONFIG_TARGET_HELIOS4=y
>> +CONFIG_MVEBU_SPL_BOOT_DEVICE_MMC=y
>> CONFIG_SPL_MMC_SUPPORT=y
>> CONFIG_SPL_SERIAL_SUPPORT=y
>> -CONFIG_SPL_LIBDISK_SUPPORT=y
>> CONFIG_SPL=y
>> CONFIG_DEFAULT_DEVICE_TREE="armada-388-helios4"
>> CONFIG_DEBUG_UART=y
--
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 -
next prev parent reply other threads:[~2018-08-06 10:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 18:56 [U-Boot] [PATCH 0/6] mvebu: allow selection of boot device Baruch Siach
2018-06-18 18:56 ` [U-Boot] [PATCH 1/6] mvebu: turris_omnia: use u-boot-spl-dtb.bin Baruch Siach
2018-06-18 18:56 ` [U-Boot] [PATCH 2/6] mvebu: a38x: drop duplicate platform id symbols Baruch Siach
2018-06-18 18:56 ` [U-Boot] [PATCH 3/6] mvebu: consolidate SPL boot device config symbols Baruch Siach
2018-06-18 18:56 ` [U-Boot] [PATCH 4/6] mvebu: select boot device at SoC level Baruch Siach
2018-07-31 17:27 ` Dennis Gilmore
2018-08-06 10:12 ` Baruch Siach [this message]
2018-08-06 12:13 ` Stefan Roese
2018-08-06 20:34 ` Dennis Gilmore
2018-06-18 18:56 ` [U-Boot] [PATCH 5/6] mvebu: support UART boot image Baruch Siach
2018-06-18 18:56 ` [U-Boot] [PATCH 6/6] mvebu: clearfog: use kconfig symbols to select boot device Baruch Siach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871sbbdcsj.fsf@tkos.co.il \
--to=baruch@tkos.co.il \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox