barebox state is not fixed up into kernel-device-tree

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