buzzmarshall has quit [Quit: Konversation terminated!]
adeepn has quit [Remote host closed the connection]
adeepn has joined #linux-amlogic
rockosov has joined #linux-amlogic
djrscally has joined #linux-amlogic
<rockosov>
mkorpershoek: Hi Mattijs,
<rockosov>
I hope you're doing well! I’d like to get your opinion on the U-Boot + AOSP architecture, particularly from your perspective as a maintainer deeply involved in this area.
<rockosov>
We’re trying to understand the correct architectural behavior for right-most and left-most parsing of AOSP init code regarding bootargs parameters. Here’s what we’ve observed:
<rockosov>
U-Boot appends all bootargs arguments to the end of /proc/cmdline, including AOSP-specific parameters (e.g., as handled in image-android.c).
<rockosov>
AOSP init parses all key-value pairs in a right-most manner.
<rockosov>
However, when InitPropertySet() sets a read-only (ro.) property, it doesn’t respect the right-most value due to restrictions on ro. properties.
<rockosov>
Do you think this is an AOSP init architectural bug, or is this behavior intentional? There seems to be some ambiguity here, and I’d appreciate your thoughts.
<rockosov>
If needed, we can prepare a patch for AOSP init, but we’d first like to confirm whether this is the expected behavior.
<rockosov>
Looking forward to your thoughts!
cbeznea has joined #linux-amlogic
Daanct12 has quit [Quit: WeeChat 4.7.0]
djrscally has quit [Remote host closed the connection]