From: Roland Hieber <r.hieber@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH] platform-v7a: barebox: version bump 2018.03.0 -> 2018.05.0
Date: Fri, 18 May 2018 11:26:28 +0200 [thread overview]
Message-ID: <20180518092628.fmsnv4nmqyo7zhgk@pengutronix.de> (raw)
In-Reply-To: <20180516162722.nlim3pwtpyd32usg@pengutronix.de>
On Wed, May 16, 2018 at 06:27:22PM +0200, Robert Schwebel wrote:
> On Wed, May 16, 2018 at 06:26:32PM +0200, Robert Schwebel wrote:
> > On Wed, May 16, 2018 at 12:15:15AM +0200, Roland Hieber wrote:
> > > Bump all barebox variants, followed by oldconfig. Consistently enable
> > > CONSOLE_ALLOW_COLOR, otherwise use default values.
> >
> > I'm not sure if this error is new:
That's not new, but I'll send a patch for NETCONSOLE nevertheless :-)
> And later on booting:
>
> Loading ARM Linux zImage '/mnt/disk0.0//boot/zImage'
> Loading devicetree from '/mnt/disk0.0//boot/vexpress-v2p-ca9.dtb'
> WARNING: Failed to fixup node in of_state_fixup+0x0/0x2d8: No such device <-----------------
> commandline: root=PARTUUID=74823abf-01 rootwait rootfstype=ext4 console=ttyAMA0,115200 loglevel=5 systemd.log_level=warning systemd.show_status=auto
That also happened already on 2018.03.0. Apparently this warning is
caused because the NOR image is readonly inside qemu, so barebox cannot
initialize the state, and fixupping the state entry fails. Looks like
stuff for the techweek.
--
Roland Hieber | r.hieber@pengutronix.de |
Pengutronix e.K. | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2018-05-18 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 22:15 Roland Hieber
2018-05-16 16:26 ` Robert Schwebel
2018-05-16 16:27 ` Robert Schwebel
2018-05-18 9:26 ` Roland Hieber [this message]
2018-05-18 14:29 ` Robert Schwebel
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=20180518092628.fmsnv4nmqyo7zhgk@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=r.schwebel@pengutronix.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