mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jan Remmet <J.Remmetl@phytec.de>
To: barebox@lists.infradead.org
Subject: Re: state: access from linux
Date: Thu, 18 Jun 2015 08:40:16 +0200	[thread overview]
Message-ID: <20150618064016.GA2723@lws-weitzel2@phytec.de> (raw)
In-Reply-To: <55817B96.6040703@pengutronix.de>

On Wed, Jun 17, 2015 at 03:52:22PM +0200, Marc Kleine-Budde wrote:
> On 06/17/2015 11:06 AM, Sascha Hauer wrote:
> > On Wed, Jun 17, 2015 at 08:42:50AM +0200, Jan Remmet wrote:
> >> Hello,
> >> I'm working with barebox states and wonder if there is already a tool to access
> >> states in eeprom from linux?
> >> The states from a dtb backend should be easy to read. For raw there must be
> >> looked under /proc/devicetree or a state kernel driver.
> > 
> > Yes, there is such a tool here:
> > 
> > git://git.pengutronix.de/git/tools/dt-utils.git
> 
> BTW: Release tarballs can be found here:
> 
> http://www.pengutronix.de/software/dt-utils/download/

Thank you for pointing me to this tool. I have some trouble to get it working
with an eeprom backend. Just to be sure if the barebox side is ok:

of_dump /state
state {
        magic = <0x7074000a>;
        compatible = "barebox,state";
	        backend-type = "raw";
	        backend = "/soc/aips-bus@02100000/i2c@021a0000/eeprom@50";
		linux,phandle = <0x2f>;
		phandle = <0x2f>;


The documentation shows also "partname:" in the backend property, but for
eeprom this is not valid.

Jan

> 
> Marc
> 
> -- 
> Pengutronix e.K.                  | Marc Kleine-Budde           |
> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
> 



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


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

  reply	other threads:[~2015-06-18  6:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  6:42 Jan Remmet
2015-06-17  9:06 ` Sascha Hauer
2015-06-17 13:52   ` Marc Kleine-Budde
2015-06-18  6:40     ` Jan Remmet [this message]
2016-04-04 21:44   ` barebox-state (dt-utils): dump-shell broken for state@0 Andreas Pretzsch
2016-04-05  6:49     ` Sascha Hauer
2016-04-06  9:38       ` Marc Kleine-Budde

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=20150618064016.GA2723@lws-weitzel2@phytec.de \
    --to=j.remmetl@phytec.de \
    --cc=J.Remmet@phytec.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