#asahi-dev · 2024-09-16 11:04
nickchanrevision == 3 would mean boot cmdline length 1024#asahi-dev · 2024-09-16 11:03
nickchanluckily for the newest increase in boot cmdline length you should be able to get around with checking the revision field of the BootArgs struct#asahi-dev · 2024-09-16 11:02
nickchanthere are some even older ones that have device tree issue that I have not gotten around to fixing yet...#asahi-dev · 2024-09-16 11:01
nickchanfor the BootArgs struct stuff because some very old firmwares like iBoot-2817 doesn't even have mem_size_actual I made some assumption and assumed the dram bottom to 0x800000000, then rounded things up to the nearest 256 MB#asahi-dev · 2024-09-16 09:53
mazI wish the author had provided a script...#asahi-dev · 2024-09-16 09:52
mazjannau: yeah, I had a fun time fixing those.#asahi-dev · 2024-09-16 09:50
jannauoh, joy. changinging the platform_device.remove function pointer signature from returning int to void for ~20 drivers#asahi-dev · 2024-09-16 09:43
emxlIf you dont get any output on your screen the culprit is probably a new version of the boot_args struct (if you have a recent macOS version). This moves mem_size_actual, breaking the mapping code and crashing m1n1 before it can initialize the screen console. I fixed this for me by increasing cmdline from 608 to 1024 bytes.#asahi-dev · 2024-09-16 09:40
emxlkj1243: You asked 2 weeks ago if you could help develop for M3. I think it would be helpful if you got to work on whatever init code for your platform is missing in m1n1. You can build m1n1 for your platform, flash it to a new OS install (then enable the -v (for verbose) boot arg with nvram boot-args="-v") and see what breaks and what works.#asahi-dev · 2024-09-14 22:03
chadmedthat said, we kinda boot way too fast for it to even matter :p#asahi-dev · 2024-09-14 22:02
chadmedi dont think we can make it not suck for us because we reset dcp so we're always going to get some amount of flicker#asahi-dev · 2024-09-14 22:01
chadmedit might need to be explicitly blocked...#asahi-dev · 2024-09-14 22:00
chadmedjannau: plymouth just waits for _a_ drm driver, so simpledrm triggers it for us#asahi-dev · 2024-09-14 18:00
nickchanthere is also a possibility that I am missing some code from the loader but idk.#asahi-dev · 2024-09-14 17:15
nickchanespecially without the luxury of access tracing#asahi-dev · 2024-09-14 17:15
nickchancan never know for sure if what you are doing is right when dealing with these hardware...#asahi-dev · 2024-09-14 17:14
nickchanoh no I think everything cpufreq related had to be retracted for now#asahi-dev · 2024-09-13 17:41
nicolas17goes back under his rock#asahi-dev · 2024-09-13 17:40
nicolas17but where is 120-125ms pro#asahi-dev · 2024-09-13 17:39
nickchanill call it 120-125ms max#asahi-dev · 2024-09-13 17:11
nickchanand the 16k devices that i have reseted in 80ms#asahi-dev · 2024-09-13 17:11
nickchanokay a8 is the worst it seems a8x is slightly faster#asahi-dev · 2024-09-13 17:05
nicolas17jannau: could you add it to the yaks page, if you agree it should be there?#asahi-dev · 2024-09-13 17:04
f87jannau: *nods* thanks for the heads-up re: dwc3#asahi-dev · 2024-09-13 17:03
nickchantakes 130-135 ms to reset#asahi-dev · 2024-09-13 17:02
nickchana8 is worse#asahi-dev · 2024-09-13 16:56
nickchanwill test newer ones too but i think the older the soc is the slower it is#asahi-dev · 2024-09-13 16:55
nickchangonna make it wait 150 ms just to be safe#asahi-dev · 2024-09-13 16:55
nickchana7 takes about 105-110 ms to actually reset#asahi-dev · 2024-09-13 16:39
nickchanand by not enough I mean the reboot failed messages shows then the system resets#asahi-dev · 2024-09-13 16:39
nickchani should do some experiments to increase the limit#asahi-dev · 2024-09-13 16:38
nickchanthe 50ms delay in the wdt driver isn't enough on some old socs i have tested#asahi-dev · 2024-09-13 16:35
jannauf87: rust xHCI + dwc3 driver + usb storage are required macos style "external" boot support. for asahi that would allow chainloading 2nd stage m1n1 from external media#asahi-dev · 2024-09-13 16:16
nicolas17maybe someone wants to help and the low-priority nice-to-have item in the list is the one they have knowledge/experience with#asahi-dev · 2024-09-13 16:14
nicolas17yak shaving page needs more entries imo#asahi-dev · 2024-09-13 16:07
f87(if usb can ever be considered 'nice')#asahi-dev · 2024-09-13 16:06
f87fair, it's not something i'm going to apply full time effort to but it's a nice backburner project#asahi-dev · 2024-09-13 15:31
opticronI know it's been mentioned off-hand as a nice to have eventually, but I don't remember anyone having actually started on it. I don't see it on the yak shaving wiki page, either. (I'm not an authoritative source on anything)#asahi-dev · 2024-09-13 14:22
f87Is anyone already working on such?#asahi-dev · 2024-09-13 14:21
f87I was considering the possibility of working on a rust xHCI USB stack (partly for m1n1 reasons but also personal interest)#asahi-dev · 2024-09-13 13:37
nickchani will post them seperately later#asahi-dev · 2024-09-13 13:36
nickchancaches are not gonna be in tomorrow's v2 just because of a10#asahi-dev · 2024-09-13 13:19
nickchanmaybe just taking the pcore value is fine? to stay consistent with the frequency adjustments#asahi-dev · 2024-09-13 13:10
nickchandepending on the p-state#asahi-dev · 2024-09-13 13:10
nickchansince the p/e core pairs acts as logical cores that suddenly have their cache resized#asahi-dev · 2024-09-13 13:10
nickchanin the devicetree#asahi-dev · 2024-09-13 13:09
nickchani have no provision of describing the cache in a10#asahi-dev · 2024-09-13 13:09
nickchani just realized#asahi-dev · 2024-09-13 12:53
nickchangot some figures on a10 cpu voltage gonna add into the device tree for documentation purposes#asahi-dev · 2024-09-13 06:25
chadmedif we wanted to be strict with opp-shared we'd need to dupe the opp tables for each cluster