X-Git-Url: http://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/blobdiff_plain/5064faae513ad55e98babaa5f495ed4c3712650e..b994e9f1d64281464d66ad3b2f7abe8e7e9b7cc0:/doc/notes.txt?ds=sidebyside

diff --git a/doc/notes.txt b/doc/notes.txt
index 06ec3a3..4905a65 100644
--- a/doc/notes.txt
+++ b/doc/notes.txt
@@ -142,3 +142,72 @@ tune2fs -U random /dev/whatever
 07:56 < VinDuv> So the installation workflow from 1TR could be “plug in a USB stick, hold the power button, select Install Asahi” instead of having to manually open the terminal and run curl | sh. The installer doesn’t even need to be graphical since
                 it’s possible for the launched shell script to start the recovery environment’s Terminal and giving it an arbitrary command to run.
 07:59 < VinDuv> This is also not limited to external USB drives; it also works if the files are in an APFS volume in internal storage, which I guess might be useful to have a Asahi Recovery boot option in the boot menu or something.
+
+---- .IAPhysicalMedia ---------------------------------------------------------
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>AppName</key>
+	<string>Some App.app</string>
+	<key>ProductBuildVersion</key>
+	<string>00A191</string>
+	<key>ProductVersion</key>
+	<string>12.2.1</string>
+</dict>
+</plist>
+
+---- Some App.app/Contents/Info.plist -----------------------------------------
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>CFBundleDisplayName</key>
+	<string>Some App</string>
+	<key>CFBundleExecutable</key>
+	<string>SomeApp</string>
+</dict>
+</plist>
+
+---- Some App.app/Contents/Resources/<lang code>.lproj/InfoPlist.strings ------
+"CFBundleDisplayName" = "Some App";
+
+---- Some App.app/Contents/MacOS/SomeApp (executable) -------------------------
+#!/bin/bash
+exec /System/Applications/Utilities/Terminal.app/Contents/MacOS/Terminal "${0%/*}/../Resources/myscript.command"
+
+---- Some App.app/Contents/Resources/myscript.command -------------------------
+#!/bin/sh
+
+echo "Hello, world!"
+exec /bin/bash
+
+
+19:14 <VinDuv> marcan: I have done a bit more testing with the .IAPhysicalMedia file and it looks like ProductBuildVersion can be any value including blank. ProductVersion seems to be checked against the minimal macOS version supported by the Mac; on my mini the icon shows up in the boot menu only if it’s >= 11.3.
+19:15 <VinDuv> Maybe it should be set to a higher value for forward compatibility with future Macs that will require 13.0? I’ve tested setting it to 99 and it works.
+
+21:46 < povik> with pulse, you can get the jack by getting into pacmd
+21:46 < povik> and running: load-module module-alsa-sink device=hw:0,1
+
+If you see this in Xorg.0.log, it means that simpledrm has not initialized.
+...
+[     4.259] (EE) open /dev/dri/card0: No such file or directory
+...
+[     4.278] (EE) 
+[     4.278] (EE) Backtrace:
+[     4.278] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaaad26e0398]
+[     4.278] (EE) unw_get_proc_info failed: no unwind info found [-10]
+
+An initialized simpledrm looks like that:
+
+(air) [~] dmesg | grep -i simpledrm
+[    2.215718] [drm] Initialized simpledrm 1.0.0 20200625 for be2120000.framebuffer on minor 0
+[    2.218952] simple-framebuffer be2120000.framebuffer: [drm] fb1: simpledrmdrmfb frame buffer device
+
+This is probably because someone forgot to enable one of the following kernel options:
+
+CONFIG_BACKLIGHT_CLASS_DEVICE=y
+CONFIG_BACKLIGHT_GPIO=m
+CONFIG_DRM=y
+CONFIG_DRM_SIMPLEDRM=y
+CONFIG_FB_EFI=n