From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Çağlar Kilimci" <ckilimci@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: State Framework and dtb
Date: Tue, 4 Apr 2017 08:22:31 +0200 [thread overview]
Message-ID: <20170404062231.xltos7rjqf6bjjvb@pengutronix.de> (raw)
In-Reply-To: <CAGUZs0=zmi+GciKgtSRUe8sT=_SXNBGH4p5jXqk8MogyQ5MMwA@mail.gmail.com>
On Mon, Apr 03, 2017 at 11:59:50PM +0300, Çağlar Kilimci wrote:
> Hello,
>
> 2017-03-31 16:00 GMT+03:00 Sascha Hauer <s.hauer@pengutronix.de>:
> > On Fri, Mar 31, 2017 at 02:41:19PM +0300, Çağlar Kilimci wrote:
> >> Hey,
> >>
> >>
> >> I tried but got the same result and then I would like to apply your
> >> serious patch series of the state framework but release that our
> >> working branch is 2016.07 so could not apply patches. Let me update
> >> barebox and apply those patches. Are those based on master branch
> >> right? Or, which branch do you recommend to work on?
> >
> > The patches are based on master, yes. Anyway, you seem to have a problem
> > in getting your changes in the dts file to the running barebox. Please
> > try to add some nodes/properties to your dts file and verify that a
> > of_dump shows these nodes. Before that is the case it's not worth to
> > look any further.
>
> Finally, I updated and patched the code and now I can see state@0
> device in the of_dump:
Ok, looks good. How does the boot log look like? Still the same?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-04-04 6:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 13:24 Çağlar Kilimci
2017-03-30 6:31 ` Sascha Hauer
2017-03-30 10:33 ` Çağlar Kilimci
2017-03-31 6:21 ` Sascha Hauer
2017-03-31 6:54 ` Çağlar Kilimci
2017-03-31 7:02 ` Sascha Hauer
2017-03-31 7:18 ` Çağlar Kilimci
2017-03-31 7:23 ` Sascha Hauer
2017-03-31 11:41 ` Çağlar Kilimci
2017-03-31 13:00 ` Sascha Hauer
2017-04-03 20:59 ` Çağlar Kilimci
2017-04-04 6:22 ` Sascha Hauer [this message]
2017-04-04 6:49 ` Çağlar Kilimci
2017-04-04 8:04 ` Jan Remmet
[not found] ` <58e3539f.0582540a.1e64d.751fSMTPIN_ADDED_BROKEN@mx.google.com>
2017-04-04 10:27 ` Çağlar Kilimci
2017-04-04 10:48 ` Ian Abbott
2017-04-05 6:01 ` Sascha Hauer
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=20170404062231.xltos7rjqf6bjjvb@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ckilimci@gmail.com \
/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