From: Tom Rini Date: Sun, 11 Oct 2015 19:45:53 -0400 Subject: [U-Boot] [RFC] odroid DTB support In-Reply-To: <5617B48C.8010603@free.fr> References: <5617AF06.9030908@free.fr> <5617B1C0.4010002@samsung.com> <5617B48C.8010603@free.fr> Message-ID: <20151011234553.GA23893@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: