Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rinato: Expose ATAGS cmdline to userspace #21

Open
casept opened this issue Jan 9, 2025 · 1 comment
Open

rinato: Expose ATAGS cmdline to userspace #21

casept opened this issue Jan 9, 2025 · 1 comment

Comments

@casept
Copy link
Owner

casept commented Jan 9, 2025

Needed to figure out device identifiers and boot mode (normal, recovery, charging only)

@casept casept changed the title Expose ATAGS cmdline to userspace rinato: Expose ATAGS cmdline to userspace Jan 9, 2025
@casept
Copy link
Owner Author

casept commented Jan 10, 2025

Just enabling ATAGS and ATAGS_PROC seems insufficient (kernel prints No ATAGs?).

The atags saved by the kernel just looks like an all-zero region.

But it doesn't seem to pass it via DTB either (even though it detects that we're booting a DT-enabled kernel).

The cursed way to go about this would be to pull it out of the S-Boot logs in memory (strings of the form ATAG_CMDLINE: 76 54410009 'console=ram loglevel=4 root=/dev/mmcblk0p15 ro rootfstype=ext4 rootwait bootmode=normal pwron.reason=ap:swrst,pmic:pwron sec_debug.enable=1 sec_debug.enable_user=1 softlockup_panic=0 sec_log=0x200000@0x46000000 lcdtype=0 oops=panic pmic_info=1875 sysscope=0xee000000 cordon=ed54f2b82322ef31ecc35db3b049264c serialno=4100cd38423931e5 tizenboot.emmc_checksum=3 tizenboot.odin=1 bootloader.ver=R380XXU0BOA2 bootloader.fb=0x48000000 bootloader.log=0x15d2@0x4600485d'), but that'd require logic to figure out which of the entries in there pertains to the current boot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant