From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Barebox List <barebox@lists.infradead.org>
Subject: Possible regression 2024.12.0 in parsing "aliases"
Date: Wed, 11 Dec 2024 09:14:32 +0300 [thread overview]
Message-ID: <CAP1tNvQoUsjRNKMr-CZ_Q67-PKGfj_ZsoePeT3pgOe_DefriMg@mail.gmail.com> (raw)
Hello.
After updating barebox to version 2024.12.0, an error message appeared
when loading
the RK3568 board. Accordingly, the I2C1 interface does not work.
In the previous version (2024.10.0), everything worked as it should. I did not
understand what the problem is, but I suspect that aliases are now
parsed incorrectly.
The system has an alias i2c1 (this is the basic SOC i2c1 interface)
and an alias i2c10 for the GPIO expander. Perhaps the problem is somewhere here?
ERROR: rk3x-i2c fe5a0000.i2c@fe5a0000.of: probe failed: Device or resource busy
Thanks!
next reply other threads:[~2024-12-11 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 6:14 Alexander Shiyan [this message]
2024-12-12 9:03 ` Sascha Hauer
2024-12-12 9:30 ` Alexander Shiyan
2024-12-12 11:31 ` Sascha Hauer
2024-12-12 12:23 ` Alexander Shiyan
2024-12-12 12:13 ` Alexander Shiyan
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=CAP1tNvQoUsjRNKMr-CZ_Q67-PKGfj_ZsoePeT3pgOe_DefriMg@mail.gmail.com \
--to=eagle.alexander923@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