From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] odroid DTB support
Date: Tue, 13 Oct 2015 08:55:22 -0400 [thread overview]
Message-ID: <20151013125522.GS23893@bill-the-cat> (raw)
In-Reply-To: <561CB4A0.9020204@free.fr>
On Tue, Oct 13, 2015 at 09:37:04AM +0200, Guillaume Gardet wrote:
>
>
> 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?
Ah, good point, OK, thanks. Yes, instead of introducing more changes,
all of these boards should be migrated to config_distro_bootcmd so that
they just work in openSUSE or Arch or Ubuntu or Fedora or whatever.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151013/a2fd2d27/attachment.sig>
prev parent reply other threads:[~2015-10-13 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 12:11 [U-Boot] [RFC] odroid DTB support Guillaume Gardet
2015-10-09 12:23 ` Przemyslaw Marczak
2015-10-09 12:35 ` Guillaume Gardet
2015-10-11 23:45 ` Tom Rini
2015-10-12 8:54 ` Guillaume Gardet
2015-10-12 11:12 ` Przemyslaw Marczak
2015-10-12 14:24 ` Tom Rini
2015-10-13 7:37 ` Guillaume Gardet
2015-10-13 9:11 ` Przemyslaw Marczak
2015-10-13 9:33 ` Guillaume Gardet
2015-10-13 10:15 ` Przemyslaw Marczak
2015-10-13 12:55 ` Tom Rini [this message]
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=20151013125522.GS23893@bill-the-cat \
--to=trini@konsulko.com \
--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