#asahi-dev · 2025-05-21 07:48
jmtpAlright, it all makes sense now so I'll go for the tethered boot approach. Thanks for the guidance.#asahi-dev · 2025-05-21 07:33
jannauu-boot has no m3 support yet#asahi-dev · 2025-05-21 07:32
jannaueventually yes but the first step should be getting tethered booting working https://asahilinux.org/docs/sw/tethered-boot/#asahi-dev · 2025-05-21 07:31
jmtpjannau: I assume the installer approach would be to run MacOS on top of m1n1 for reverse engineering purposes, right?#asahi-dev · 2025-05-21 07:31
chaos_princessyou won't reach u-boot with upstream m1n1 i think?#asahi-dev · 2025-05-21 07:30
jmtpSo what I wanted to do is to install m1n1 as stage1 and stage 2 bootloaders. Then uboot as well. From there it must be regular Linux kernel boot which I'm used to.#asahi-dev · 2025-05-21 07:22
jannau13.7 would probably work, there is just very little reason to test that. 13.6 does work. We tried it in the hope to work around the dcp promotion bug#asahi-dev · 2025-05-21 07:19
chaos_princessoh, neat. well, it is still a problem for 12.3 and 13.5 that we use, but at least less of an issue for 14.x#asahi-dev · 2025-05-21 07:18
jannau12.7.4 and 13.7.6 are still available as well#asahi-dev · 2025-05-21 07:16
jannauhttps://mrmacintosh.com/macos-sonoma-full-installer-database-download-directly-from-apple/ lists various 14.7 installers as still available#asahi-dev · 2025-05-21 07:14
jannauI think the latest installer of each main macos version is still available from apple's CDN#asahi-dev · 2025-05-21 07:14
chaos_princessapple unfortunately does not keep them forever on their cdn like ipsws#asahi-dev · 2025-05-21 07:13
jannaujmtp: I did not mean version of the main macos install#asahi-dev · 2025-05-21 07:13
chaos_princessthere should be installassistants for various 14.x versions on archive.org#asahi-dev · 2025-05-21 07:12
jannauI probably should spent some time to get j504 (14-inch M3 Macbook Pro) usable#asahi-dev · 2025-05-21 07:12
jmtpIt's a mpb with m3 max. MacOS is 15.5.#asahi-dev · 2025-05-21 07:08
jannauthe installer versions obviously don't make sense for m3 devices. I would choose the latest available 14.x installer since the nvme firmware changed in an incompatible way in macos 15#asahi-dev · 2025-05-21 07:05
jannaujmtp: which m3 device? a second macOS with a manually installed m1n1 like described in https://asahilinux.org/docs/sw/m1n1-hypervisor/ would be a good first step#asahi-dev · 2025-05-21 06:59
jmtpThank you. I'll give it a try.#asahi-dev · 2025-05-21 06:56
chaos_princessyou will have to do it manually, installer will refuse to run on m3#asahi-dev · 2025-05-21 06:47
jmtpWhat would be the best way to get started? Just run the installer to flash m1n1 bootloader and go from there? Or install it manually instead?#asahi-dev · 2025-05-21 06:46
jmtpHi everyone, I've got a question about running on M3. I'm aware it's not fully supported, so I'd like to help with the development and testing on my own laptop.#asahi-dev · 2025-05-19 21:59
allmazzjannau: sry, false alarm, the dt is ok on j414#asahi-dev · 2025-05-19 18:49
allmazzjannau: hm, I will try to investigate it#asahi-dev · 2025-05-19 18:27
jannauallmazz: yes, that expected to work and I'm not aware of changes which could affect that. hid-apple wouldn't be my first place to look for issue. I'd start looking in dockchannel/mtp but that was working on a 13-inch m2 macbook pro#asahi-dev · 2025-05-19 14:24
alyssafair#asahi-dev · 2025-05-19 14:01
leiofirst showing what it looks like in a text editor too#asahi-dev · 2025-05-19 14:00
leioin gentoo we have a tool that takes a PR number and just git am's the lot to your local branch via downloading that#asahi-dev · 2025-05-19 13:58
alyssa..annoys the crap out of other mesa developers but it's an a11y thing for me so \shrug/#asahi-dev · 2025-05-19 13:57
alyssaleio: I have a script to do exactly that for gitlab, I use it for most my mesa reviews!#asahi-dev · 2025-05-19 13:01
allmazzjannau: does device tree ok in the wip branch? keyboard doesn't not work on j414, suppose that hid_apple isn't loaded for somereason#asahi-dev · 2025-05-18 16:35
jannauI've pushed asahi-6.14.7-1 to github. some hopefully minor devicetree property fixes for the GPU M1 Pro/Max/Ultra (all devices) and M2 Pro/Max/Ultra (mac mini/studio), provide panel dimension for simpledrm#asahi-dev · 2025-05-18 13:01
svenyeah, my point is simply that every method has its issues and that I can live with email thanks to b4#asahi-dev · 2025-05-18 13:00
leioput .patch at the end of the forge commit or PR URL and feed it into your remote file supporting text editor; but not what you meant :)#asahi-dev · 2025-05-18 11:14
svenyup, those bots are quite useful. at some point asahilinux/linux got added to their list of repos to pull from and now I get stuff like e.g. https://lore.kernel.org/oe-kbuild-all/202505181857.NVLANqSD-lkp@intel.com/T/#u#asahi-dev · 2025-05-18 11:11
nickchanand i have seen some compile issues that only happens on like a hexagon randconfig that i would have never noticed without a ci bot#asahi-dev · 2025-05-18 11:09
nickchana forge doesn't have to be limited to a web ui#asahi-dev · 2025-05-18 11:04
svenoh yeah, it has some issues. but I e.g. also prefer to read the changeset in a text editor to the github web UI#asahi-dev · 2025-05-18 11:02
chadmedif i see some silly mistake i want to just force push a branch and fix it rather than wait the customary two weeks or whatever to avoid spamming maintainer mailboxes#asahi-dev · 2025-05-18 11:02
chadmedb4 is a great help but i do think there are some frustrating aspects to the ML workflow that can only really be resolved with a proper forge. the fact that patch versions are discrete units and sending "too many" is considered bad manners is endlessly frustrating#asahi-dev · 2025-05-18 10:59
svenb4 already takes away much of the pain with email imho#asahi-dev · 2025-05-18 10:58
chadmedfuture technology. maybe someone can vibe code something like that in cursor :p #asahi-dev · 2025-05-18 10:57
chadmedit would be even cooler if we just like, had merge requests. in some sort of like git-laboratory or something.#asahi-dev · 2025-05-18 10:55
sveni keep forgetting that various CI bots pick up all branches from our github repo and then point out issues in sven/atcphy that I likely would've only found after v1 otherwise #asahi-dev · 2025-05-18 10:53
chadmedsent#asahi-dev · 2025-05-18 10:28
chadmedill swap the first two commits and send then#asahi-dev · 2025-05-18 10:26
svenchadmed: mca looks to me now#asahi-dev · 2025-05-18 10:20
jannauno, expected to be merged for 6.16#asahi-dev · 2025-05-18 10:17
vulpes2just want to double check before I submit a pull request to update the docs#asahi-dev · 2025-05-18 10:16
vulpes2is pcie support for T602x fully upstreamed in 6.15?