mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: "Stefan Riedmüller" <S.Riedmueller@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: master breaks phytec-phycore-imx6ul
Date: Tue, 09 May 2017 18:25:37 +0200	[thread overview]
Message-ID: <1494347137.2322.32.camel@pengutronix.de> (raw)
In-Reply-To: <OF7204A8B9.F7D47FA3-ONC125811B.00533563-C125811B.00533568@phytec.de>

Am Dienstag, den 09.05.2017, 17:08 +0200 schrieb Stefan Riedmüller:
> Hi guys,
> 
> after applying the latest master patches barebox does not boot anymore on my PHYTEC-phyCORE-i.MX6UL. It doesn't show any output. I was able to identify the commit which seems to be responsible for this behavior.
> 
> It's 2c506afbadcd546dcc54a0e8599e454fd4aecfdc (ARM: i.MX50: Add support for i.MX50 based Amazon Kindle e-book readers).
> 
> It is possible to make the board boot again by disabling System Type --> CONFIG_MACH_KINDLE_MX50 (i.MX50 based Amazon Kindle 4 and 5) in the menuconfig. This deactivates ARCH_IMX50. I also tested it on the PHYTEC-phyCORE-i.MX6-Quad board and the Fresscale SabreSD board with i.MX6 Quad and found the same behavior. I could not find an explanation yet for this so I hope you can help me.

The kindle initcalls are missing the compatibility checks, so they will
be executed on every machine on a multi-image build, which is wrong.

Regards,
Lucas


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2017-05-09 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 15:08 Stefan Riedmüller
2017-05-09 16:25 ` Lucas Stach [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=1494347137.2322.32.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=S.Riedmueller@phytec.de \
    --cc=barebox@lists.infradead.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