mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Patrick Boettcher <patrick.boettcher@posteo.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: barebox state is not fixed up into kernel-device-tree
Date: Sun, 4 Nov 2018 23:39:08 +0100	[thread overview]
Message-ID: <20181104233908.48ce2577@yaise-pc1> (raw)

Hi,

I'm using a device-state (for bootchooser) which is stored in an eeprom.

Works fine from within barebox - read and write.

Userspace does not see the state:

  Neither /aliases/state nor /state found

The displayed device-tree when booting with 'boot -v -v <name>' does
not contain the state-entry.

However, there is a warning of a failed fixup:

  Failed to fixup node in of_state_fixup+0x1/0x1ac: No such device

Could it be that the eeprom-alias is missing? I'm still learning
device-tree and stuff and I'm not yet entirely sure how everything is
related.

The partition is created within a 

  &eeprom {
     [..]
  }

section and eeprom is defined as 

  eeprom: eeprom@52 {

  }

(I added the 'eeprom: '- name/alias)

Where am I missing the link?

best regards,
--
Patrick.

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

             reply	other threads:[~2018-11-04 22:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-04 22:39 Patrick Boettcher [this message]
2018-11-05  8:28 ` Ulrich Ölmann
2018-11-05  8:41   ` Patrick Boettcher
2018-11-05  9:20     ` Patrick Boettcher
2018-11-06  5:42       ` Ulrich Ölmann
2018-11-05  9:26     ` Ulrich Ölmann
2018-11-05 18:21       ` Patrick Boettcher

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=20181104233908.48ce2577@yaise-pc1 \
    --to=patrick.boettcher@posteo.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