mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: barebox state alias with same name as node doesn't work
Date: Fri, 18 Jan 2019 15:58:56 +0000	[thread overview]
Message-ID: <1ea7152b-ac26-33aa-37db-6407a96d4381@mev.co.uk> (raw)
In-Reply-To: <CAHQ1cqGmLGkHQXDOQgasp0naeX5NomG9iODJrx0veAb_ByNGzQ@mail.gmail.com>

On 17/01/2019 21:10, Andrey Smirnov wrote:
> On Thu, Jan 17, 2019 at 8:16 AM Ian Abbott <abbotti@mev.co.uk> wrote:
>>
>> Hi,
>>
>> All the examples of "barebox,state" compatible nodes I can find in
>> Barebox seem to follow this basic pattern:
>>
>> / {
>>     /* ... */
>>     aliases {
>>       /* ... */
>>       state = &state;
>>     };
>>     /* ... */
>>     state: state {
>>       magic = <0xdeadbeef>; /* or whatever */
>>       compatible = "barebox,state";
>>       /* ... */
>>     };
>>     /* ... */
>> };
>>
>> Note that the alias name is the same as the node name in the above example.
>>
>> However, when I try to follow that pattern for my own board, I get an
>> error (-EINVAL):
>>
>> ERROR: register_device: already registered state
[snip]
>> I'm currently using Barebox 2018.12.0, but I don't see any relevant
>> changes in Barebox 2019.01.0 or barebox-next.
>>
> 
> This should be fixed by:
> http://lists.infradead.org/pipermail/barebox/2018-November/035432.html
> I don't think it is a part of 2018.12.0, though

That explains it!  I've now updated to 2019.01.0 to pick up the change 
and it seems to work now.  Thanks for the help.

-- 
-=( Ian Abbott <abbotti@mev.co.uk> || Web: www.mev.co.uk )=-
-=( MEV Ltd. is a company registered in England & Wales. )=-
-=( Registered number: 02862268.  Registered address:    )=-
-=( 15 West Park Road, Bramhall, STOCKPORT, SK7 3JZ, UK. )=-

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

      parent reply	other threads:[~2019-01-18 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 16:16 Ian Abbott
2019-01-17 21:10 ` Andrey Smirnov
2019-01-18  7:02   ` Sascha Hauer
2019-01-18 15:58   ` Ian Abbott [this message]

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=1ea7152b-ac26-33aa-37db-6407a96d4381@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=andrew.smirnov@gmail.com \
    --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