X-Git-Url: http://cvs.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/blobdiff_plain/7f82212ff6c112055927086f5f734ebea39ffb24..2bb4f32a7702763b4f48a5296a8ae4c901371d66:/doc/notes.txt?ds=inline

diff --git a/doc/notes.txt b/doc/notes.txt
index dbbdaa3..5fbe8b9 100644
--- a/doc/notes.txt
+++ b/doc/notes.txt
@@ -21,6 +21,7 @@ Chromium 16KB patch: https://tg.st/u/Set-kernal-page-size-to-16K-on-loongson-MIP
 15:26 < tpw_rules> Glanzmann: https://pastebin.com/NzJEQJDW - https://tg.st/u/NzJEQJDW
 15:26 < tpw_rules> last i checked the built chromium only worked with the flags --in-process-gpu --no-sandbox --no-zygote but that may have been a kernel config problem
 Upstream BUG: https://bugs.webkit.org/show_bug.cgi?id=236564
+16:21 < tpw_rules> https://bugs.chromium.org/p/chromium/issues/detail?id=1301788
 
 22:39 < jannau> `dtc -I fs -O dts -o - /proc/device-tree` will output the device-tree as seen by linux
 
@@ -191,6 +192,8 @@ exec /bin/bash
 21:56 < povik> that mode of playing in parallel through the speakers and jack has a defect
 21:57 < povik> there's noise mixed-in then, at a period
 21:57 < povik> don't know how that happens yet
+When disabling the speakers, run rm -rf ~/.config/pulse/ and reboot otherwise the jack will be in the future off or 100% (which is too loud).
+
 
 If you see this in Xorg.0.log, it means that simpledrm has not initialized.
 ...
@@ -396,12 +399,11 @@ ctl.!default {
 
 16:43 < povik> marcan: two fixes on top of 'asahi' that should make it into the release: https://github.com/povik/linux/commits/asahi-fixes
 
-# Manually install m1n1 in chainloading mode:
 # boot into 1tr
 diskutil list
 diskutil info <identifier of esp>
 curl -sLo tg.st/u/m1n1-rust.bin
-cat m1n1-rust.bin <(echo 'chainload=<Partition UUID>;m1n1/boot.bin') > object.bin
+cat m1n1-rust.bin <(echo 'chainload=<ESP Partition UUID>;m1n1/boot.bin') <(echo 'chosen.asahi,efi-system-partition=<ESP Parition UUID>') > object.bin
 kmutil configure-boot -c object.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v /Volumes/Linux
 
 20:29 < Glanzmann> One question though what is difference between chosen.asahi,efi-system-partition=EFI-PARTITION-PARTUUID and chainload=EFI-PARTITION-PARTUUID;m1n1/boot.bin?
@@ -410,3 +412,14 @@ kmutil configure-boot -c object.bin --raw --entry-point 2048 --lowest-virtual-ad
 20:32 < Glanzmann> I see. Thank you for the elaboration.
 20:32 < jannau> chosen.asahi,efi-system-partition is passed from the 1st stage forward to the second stage
 20:33 < Glanzmann> I see, so the first stage informs the second stage about the uuid of the esp partition which is than passed using dt to u-boot which can than select the right esp to select the efi binary.
+
+17:25 < Jamie[m]1> I had a dumb idea and had to implement it: using http range requests and DEFLATE trickery to download Wifi firmware from Apple's CDN with only 18MB of transfer (out of a 13GB ipsw) http://github.com/JJJollyjim/firmware-abomination
+
+23:23 <@jannau> Glanzmann: on the mini vram can fit 5.5 million pixels, would be good for 3440x1600 or 3840x1433 at 32bpp
+
+11:37 < AdryzzOLEDEdition[m]> https://lists.gnu.org/archive/html/bug-gnu-emacs/2021-03/msg01260.html
+
+https://gist.github.com/rqou/2dafd40cfe0362cc84c3ee26c68b2b36
+
+https://arvanta.net/alpine/install-alpine-m1/
+21:48 < mps> Glanzmann: no, but /etc/local.d/$scriptname.start