Stages TWRP's GUI engine and standalone tooling as PawletOS-owned modules instead of a bootable/recovery fork, per the plugin-architecture finding in NOTES-ota-recovery-ab.md: stock recovery_main.cpp already dlopen()s librecovery_ui_ext.so and dlsym()s make_device() from it at runtime, so the UI layer doesn't require touching stock bootable/recovery at all. Confirmed via source grep that recovery.cpp/install.cpp have zero references into the partition manager/backup engine/GUI code and vice versa. recovery_ui/: TWRP's gui/, minuitwrp/, libpixelflinger/ (copied verbatim, GPL-3.0), plus a new device/ providing PawletTwrpUI (a ScreenRecoveryUI subclass) and make_device() — written from scratch against stock's RecoveryUI/ScreenRecoveryUI virtual-method contract, since TWRP's own fork never ships a make_device() (every real TWRP device provides its own, and no reference device tree was available to copy from). Top-level Android.bp defines librecovery_ui_pawlet_twrp, the module TARGET_RECOVERY_UI_LIB should point at. gui/Android.bp and minuitwrp/Android.bp had their include_dirs rewritten for the new paths. recovery_toolkit/: partition manager, backup engine (tar/digest/adbbu/apex), filesystem/format support (exfat/dosfstools/gpt/fuse/mtp/crypto), scripting (openrecoveryscript/orscmd/twrpinstall), shared helpers. Source only, no Android.bp yet for any of it. Known gap blocking recovery_ui from actually linking: gui/'s libguitwrp depends on libaosprecovery, built from recovery_toolkit/helpers/twrp.cpp via a Go Soong plugin (libaosprecovery_defaults.go) not yet ported. Neither repo has been build-tested — no local AOSP build environment available in this workspace. See each directory's README.md for a precise done/not-done breakdown.
42 lines
1.2 KiB
Plaintext
42 lines
1.2 KiB
Plaintext
Announcing the release of mkdosfs version 0.3b (Yggdrasil)
|
|
|
|
It seems I didn't get the bug completely fixed in 0.3a. Some
|
|
borderline cases would still allocate too many sectors for the FAT.
|
|
Again, nothing to worry about, just a nitpick -- this one would only
|
|
in certain cases add one sector per FAT.
|
|
|
|
Announcing the release of mkdosfs version 0.3a (Yggdrasil)
|
|
|
|
Fixed a bug which would cause too many sectors to be reserved for the
|
|
FAT (filesystem will still work fine, but have slightly less space
|
|
available).
|
|
|
|
Announcing the release of mkdosfs version 0.3 (Yggdrasil)
|
|
|
|
This version correctly handles even very large filesystems, and
|
|
properly supports the modern (3.3+) DOS bootsector format, including a
|
|
message printed on boot attempts.
|
|
|
|
Peter Anvin
|
|
Yggdrasil Computing, Inc.
|
|
hpa@yggdrasil.com
|
|
|
|
--------------
|
|
|
|
Announcing the release of mkdosfs version 0.2
|
|
|
|
|
|
I've just uploaded mkdosfs to sunsite.unc.edu. It works in a similar way
|
|
to Remy Card's mke2fs, but creates an MS-DOS filesystem.
|
|
|
|
The filename is mkdosfs-0.2.tar.gz.
|
|
|
|
This second release should fix a small bug that could lead to FAT sizes that
|
|
Linux's dosfs would accept but MS-DOS wouldn't.
|
|
|
|
The archive contains a manual page, binary and source versions.
|
|
|
|
|
|
Dave Hudson
|
|
dave@humbug.demon.co.uk
|