public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Oliver Graute <oliver.graute@gmail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: s.hauer@pengutronix.de, linux-imx@nxp.com, kernel@pengutronix.de,
	fabio.estevam@nxp.com, shawnguo@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Re: [PATCHv2] ARM: dts: Add support for Variscite DART-6UL board
Date: Tue, 8 Jan 2019 19:18:10 +0100	[thread overview]
Message-ID: <20190108181810.GA24239@ripley> (raw)
In-Reply-To: <413a63ce-618e-4edc-ab1a-cd3071543a84@baylibre.com>

Hello,

i've splitted the Board and the SoM part into two different dts/dtb files:

imx6ul-var-6ulcustomboard.dts 
imx6ul-var-dart-nand-wifi.dts

What is the right way to boot my Board and the SoM from u-boot?

currently my u-boot just load the SoM file and I see only:

Kernel image @ 0x82000000 [ 0x000000 - 0x839980 ]
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
      Using Device Tree in place at 83000000, end 83009509

      Starting kernel ...

Best regards,

Oliver

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2019-01-08 18:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 13:26 [PATCHv2] ARM: dts: Add support for Variscite DART-6UL board Oliver Graute
2019-01-04 13:26 ` [PATCHv2] ARM: dts: Add support for i.MX6 UltraLite DART NAND/WIFI Oliver Graute
2019-01-04 13:26 ` [PATCHv2] ARM: dts: add imx6ul-var-dart-nand-wifi.dtb Oliver Graute
2019-01-04 13:30 ` [PATCHv2] ARM: dts: Add support for Variscite DART-6UL board Neil Armstrong
2019-01-04 13:52   ` Oliver Graute
2019-01-08 18:18   ` Oliver Graute [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=20190108181810.GA24239@ripley \
    --to=oliver.graute@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=narmstrong@baylibre.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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