mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Seraphim Dolbilov <s.dlblv@ya.ru>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [HELP] DT isues
Date: Tue, 5 Feb 2019 12:52:38 +0100	[thread overview]
Message-ID: <20190205115238.jep3ych42bz5licz@pengutronix.de> (raw)
In-Reply-To: <5044551549275222@myt3-2475c4d2af83.qloud-c.yandex.net>

On Mon, Feb 04, 2019 at 01:13:42PM +0300, Seraphim Dolbilov wrote:
> Hello friends,
> 
> I'm trying to modify DT dynamically while Barebox is running, but it
> doesn't work the way I expect. E.g. I use of_delete_node(), but `of_dump`
> shows all nodes that are expected to be deleted, so the corresponding 
> devices are available both from Barebox and Linux.

I have no indication that of_delete_node() doesn't work. Are you sure
you are deleting nodes from the same tree that you actually show with
of_dump?

Note that of_delete_node() only deletes from the current barebox device
tree. When you start Linux with another devicetree then the node will
be there again of course. If you want to delete a node from the Linux
Device tree then have a look at the -f option to the of_node command.

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

  reply	other threads:[~2019-02-05 11:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 12:34 [HELP] Barebox porting Seraphim Dolbilov
2019-01-21 14:28 ` Seraphim Dolbilov
2019-01-21 15:12 ` Sascha Hauer
2019-01-21 15:35   ` Seraphim Dolbilov
2019-01-21 16:35   ` Sam Ravnborg
2019-01-21 16:43     ` Seraphim Dolbilov
2019-01-22  6:33     ` Sascha Hauer
2019-01-22 14:07       ` Seraphim Dolbilov
2019-01-22 14:42         ` Sascha Hauer
2019-01-22 16:12           ` Seraphim Dolbilov
2019-01-23  9:11             ` Sascha Hauer
2019-01-23 10:01               ` Seraphim Dolbilov
2019-01-23 10:17                 ` Sascha Hauer
2019-01-25 12:18                   ` Seraphim Dolbilov
2019-01-25 14:11                     ` Seraphim Dolbilov
2019-01-28  8:46                       ` Sascha Hauer
2019-02-04 10:13                         ` [HELP] DT isues Seraphim Dolbilov
2019-02-05 11:52                           ` Sascha Hauer [this message]
2019-02-05 13:45                             ` Seraphim Dolbilov
2019-01-28  8:44                     ` [HELP] Barebox porting 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=20190205115238.jep3ych42bz5licz@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.dlblv@ya.ru \
    /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