mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: barebox@lists.infradead.org
Subject: of_state_fixup / different path in barebox and kernel
Date: Wed, 17 Feb 2016 19:14:56 +0100	[thread overview]
Message-ID: <20160217181456.GZ5868@nataraja> (raw)

Dear List,

I have a custom board with an AM335x on it.  We used to have an I2C
EEPROM for keeping the boot state, but moved that to SPI in a subsequent
version.

The SPI EEPROM uses gpio-based chip select, which is supported by linux
kernel spi-omap2-mcspi.c.  However, it is not supported by barebox.

My "solution" was to simply use the gpio-bitbang in barebox, which also
works fine for those few bytes that need to be read, performance doesn't
matter.

Now however I can no longer boot any kernel image, as of_state_fixup
fails in

	backend_node = of_find_node_by_path_from(root, state->backend->of_path);

due to the fact that the of-path of the EEPROM is different in the
barebox device tree (/spi_gpio/m95m02@0) than in the kernel device tree
(/ocp/spi@481a0000/m95m02@0)

Is there any designated solution for this situation?

Thanks in advance,
	Harald
-- 
- Harald Welte <laforge@gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)

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

             reply	other threads:[~2016-02-17 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 18:14 Harald Welte [this message]
2016-02-18 11:57 ` 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=20160217181456.GZ5868@nataraja \
    --to=laforge@gnumonks.org \
    --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