| 25 Nov 2024 |
 oak 🏳️🌈♥️ | If I'd buy a new Android phone right now, I'd probably go for 256GB model of Pixel 9 Pro | 21:00:39 |
| oak 🏳️🌈♥️ | I have instantnoodlep which is OnePlus 8 Pro, it's also a bit old at this point, the last officially supported update came out few months ago. (OnePlus usually supports their devices for 4 years.) Then I used my even older OnePlus 5T (dumpling) as a test phone, even that seems to run LineageOS 21. But I think that's because that LineageOS developer luk1337 puts quite much effort to supporting those devices | 21:03:52 |
| oak 🏳️🌈♥️ | https://github.com/melontini/bootloader-unlock-wall-of-shame | 21:06:14 |
| oak 🏳️🌈♥️ | What is cool about Pixel 8 and Pixel 9 is that they support the new ARM Memory Tagging Extensions | 21:10:25 |
| oak 🏳️🌈♥️ | https://googleprojectzero.blogspot.com/2023/11/first-handset-with-mte-on-market.html | 21:13:35 |
| 26 Nov 2024 |
 ryantrinkle | samueldr: oak Thanks for the info! | 14:45:40 |
|  @jack:unredacted.org joined the room. | 20:40:37 |
| @jack:unredacted.org | Hi. Anyone here know how to compare pvmfw.img between two AOSP (Android 15) builds? It is an unusual file structure and I don't know how to unpack this before comparing with diffoscope. | 20:41:42 |
 atemu12 | What is the file type? | 20:42:25 |
| @jack:unredacted.org | pvmfw.img is an Android boot image (according to the file command). The unpack_bootimg.py from AOSP can unpack it, but the "kernel" file inside of it has just "data" as its file type.
| 20:44:55 |
| @jack:unredacted.org | $ file pvmfw.img.unpacked/*
kernel: data
ramdisk: empty
| 20:49:37 |
| @jack:unredacted.org | It's a really weird couple of files and I really don't know how to make diffoscope compare them properly. | 20:51:38 |
| @jack:unredacted.org | The pvmfw.img file itself has this type:
$ file pvmfw.img
pvmfw.img: Android bootimg, kernel
| 20:53:22 |
| @jack:unredacted.org | Maybe I should try checking if platform/build/+/master/tools/extract_kernel.py can make some sense out of it. | 20:54:16 |
| @jack:unredacted.org | Yeah, not even AOSP's extract_kernel.py can make some sense out of pvmfw.img.unpacked/kernel. | 21:06:33 |
| @jack:unredacted.org | * Yeah, not even AOSP's extract_kernel.py can make some sense out of pvmfw.img.unpacked/kernel.
| 21:06:41 |
| @jack:unredacted.org | * Maybe I should try checking if platform/build/+/master/tools/extract_kernel.py can make some sense out of it.
| 21:06:48 |
| @jack:unredacted.org | Aside from this, I've also used unpack_bootimg.pyto unpack the boot.img. That one has a perfectly normal ARM64 kernel image, but diffoscope still shows a large diff when comparing two builds of the same boot.img.unpacked/kernel. Do I need to preprocess this kernel image somehow before comparing? Not sure if I need to strip signatures from the image or how to do this, by the way.
| 21:14:19 |
| @jack:unredacted.org | * Aside from this, I've also used unpack_bootimg.py to unpack the boot.img. That one has a perfectly normal ARM64 kernel image, but diffoscope still shows a large diff when comparing two builds of the same boot.img.unpacked/kernel. Do I need to preprocess this kernel image somehow before comparing? Not sure if I need to strip signatures from the image or how to do this, by the way.
| 21:14:29 |
 samueldr | jack: when I hit a weird filetype, especially when it's likely others have it it, searching its filename in github code search helps... when you know how to use it, which is non-obvious: use a regex to search
| 21:14:54 |
| @jack:unredacted.org | In reply to @samueldr:matrix.org
jack: when I hit a weird filetype, especially when it's likely others have it it, searching its filename in github code search helps... when you know how to use it, which is non-obvious: use a regex to search
That's a good idea. Thanks. | 21:15:32 |
| samueldr | given I see Protected VM firmware image along it, maybe that's not "just" a linux kernel | 21:16:05 |
| samueldr | even though it's packaged within the "container" of an android boot image | 21:16:24 |
| @jack:unredacted.org | In reply to @jack:unredacted.org
Aside from this, I've also used unpack_bootimg.py to unpack the boot.img. That one has a perfectly normal ARM64 kernel image, but diffoscope still shows a large diff when comparing two builds of the same boot.img.unpacked/kernel. Do I need to preprocess this kernel image somehow before comparing? Not sure if I need to strip signatures from the image or how to do this, by the way.
Any idea on this one? | 21:16:48 |
| samueldr | https://github.com/GrapheneOS/platform_packages_modules_Virtualization/tree/9ec1c44084125875aa9619635e4e6fdf3172b57c/pvmfw#integration | 21:17:07 |
| samueldr | In reply to @jack:unredacted.org
Any idea on this one? nope | 21:17:27 |
| @jack:unredacted.org | In reply to @jack:unredacted.org
Aside from this, I've also used unpack_bootimg.py to unpack the boot.img. That one has a perfectly normal ARM64 kernel image, but diffoscope still shows a large diff when comparing two builds of the same boot.img.unpacked/kernel. Do I need to preprocess this kernel image somehow before comparing? Not sure if I need to strip signatures from the image or how to do this, by the way.
boot.img unpacked perfectly and has a perfect ARM64 kernel image, but I personally don't know how to compare different kernel images, maybe I have to strip signatures like I successfully did with the kernel modules before. | 21:18:06 |
| @jack:unredacted.org | In reply to @jack:unredacted.org
Aside from this, I've also used unpack_bootimg.pyto unpack the boot.img. That one has a perfectly normal ARM64 kernel image, but diffoscope still shows a large diff when comparing two builds of the same boot.img.unpacked/kernel. Do I need to preprocess this kernel image somehow before comparing? Not sure if I need to strip signatures from the image or how to do this, by the way.
* | 21:18:20 |
| samueldr | | 21:18:41 |
| samueldr |
The pVM firmware (pvmfw) is the first code executed by a pVM, similar to the boot ROM of a physical device.
| 21:18:52 |
