From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Gardet Date: Tue, 13 Oct 2015 09:37:04 +0200 Subject: [U-Boot] [RFC] odroid DTB support In-Reply-To: <20151012142416.GB23893@bill-the-cat> References: <5617AF06.9030908@free.fr> <5617B1C0.4010002@samsung.com> <5617B48C.8010603@free.fr> <20151011234553.GA23893@bill-the-cat> <561B752C.4010208@free.fr> <20151012142416.GB23893@bill-the-cat> Message-ID: <561CB4A0.9020204@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Le 12/10/2015 16:24, Tom Rini a ?crit : > On Mon, Oct 12, 2015 at 10:54:04AM +0200, Guillaume Gardet wrote: >> Hi, >> >> >> Le 12/10/2015 01:45, Tom Rini a ?crit : >>> On Fri, Oct 09, 2015 at 02:35:24PM +0200, Guillaume Gardet wrote: >>>> Le 09/10/2015 14:23, Przemyslaw Marczak a ?crit : >>>>> Hello Guillaume, >>>>> >>>>> On 10/09/2015 02:11 PM, Guillaume Gardet wrote: >>>>>> Hi Przemyslaw, >>>>>> >>>>>> I would like to add DTB support for odroid board to be able to boot >>>>>> upstream kernel easily. >>>>>> >>>>>> I see 2 ways to do it: >>>>>> * Add CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG support to set 'board_rev' >>>>>> and 'board_name' env vars. Then, you need a 'findfdt' script to check >>>>>> 'board_rev' and set fdtfile accordingly (as done for OMAP4 panda board) >>>>>> * Set fdtfile name directly (as done for rpi or igep00x0). >>>>>> >>>>>> What would you prefer? >>>>>> >>>>>> >>>>>> Guillaume >>>>>> >>>>>> >>>>> Is, that the reason of adding the boot script by your last patches? >>>> No, we need a boot script, because this is the way we boot our >>>> openSUSE images (we boot with an initrd and some special bootargs). >>> Hang on, exynos stuff uses the generic distro hooks. Can you take a >>> look at doc/README.distro and see what openSUSE can hook into / provide >>> some feedback on what needs doing? Thanks! >> This is true for odroid XU3 (Exynos5 based) but Odroid U3/X2 (Exynos4 >> based) has no generic distro hooks at the moment. > No, exynos-common pulls in generic distro. And in the event of boards > that do not the answer is to pull in the generic distro framework. It seems that exynos-common includes only "config_distro_defaults.h", not "config_distro_bootcmd.h". And "config_distro_bootcmd.h" is needed for generic distro boot flow. Am I missing something? Guillaume