#
✕ nick:fl0_id
#asahi-dev · 2025-06-07 23:25
fl0_id(I hope Ia m using container correctly here... the apfs container in the separate partition I mean, wherein one would then create a separate volume as desribed here https://asahilinux.org/docs/sw/m1n1-hypervisor/#running-macos-under-the-m1n1-hypervisor
#asahi-dev · 2025-06-07 23:24
fl0_idfor running a debug macos under hv, is it better to do this in the m1n1 container or in the original macos container?
#asahi-dev · 2025-06-07 20:02
fl0_idI can also try updating my stage1 m1n1 / check if there were any changes or generally try to check uart
#asahi-dev · 2025-06-07 20:01
fl0_idamarioguy I guess so? you know more then me tbh. do you think it would make sense to try other registers, to check if it's just sth about this on or sth else?
#asahi-dev · 2025-06-07 10:28
fl0_idsven tracing is prob a good idea, but I think I don't have a setup yet for that. (so far I only have avery basic second macos container, which is now set up to boot m1n1 and would have to check how much work it would be to enable a ful hv / tracing setup on that
#asahi-dev · 2025-06-07 10:27
fl0_id*is
#asahi-dev · 2025-06-07 10:27
fl0_idsven ok. it might be, I don't know enough to know which error count that s
#asahi-dev · 2025-06-07 09:48
fl0_idto try to understand the data structure that it's reading before it breaks. to see what's what. Like just locally of course for trying things. sorry if I am misunderstanding something
#asahi-dev · 2025-06-07 09:36
fl0_idsven mmh thx that already helps. though not sure how. maybe for starters I'd just add some print statements...
#asahi-dev · 2025-06-07 09:25
fl0_id@amarioguy - oh and if I tried to run it again, it would not give an error / timeout but just not respond and I'd have to close the shell forcefully
#asahi-dev · 2025-06-06 23:47
fl0_idalso, I updated m1n1 python console etc to the latest if there were any changes - but it seems that some errors for m3 at least remain. f.e. I had to reapply my hack: https://github.com/AsahiLinux/m1n1/issues/449 - otherwise shell and ishell.py crash. Could I make a PR for my bypass, or can someone point me in the right direction to otherwise fixing it?
#asahi-dev · 2025-06-06 23:34
fl0_idamarioguy I got this as a result, though I have to check if sth else is wrong maybe too. https://www.pastery.net/praejy/
#asahi-dev · 2025-06-03 14:00
fl0_idsth else - if there is not just one address and size for a register, is just the first one used for the dt, or is there a more complicated calculation e.g. how a set of five address / size pairs for a reg entry are transcribed?
#asahi-dev · 2025-06-03 13:59
fl0_idmakes sense
#asahi-dev · 2025-06-03 13:27
fl0_idok
#asahi-dev · 2025-06-03 13:24
fl0_id(this is from the adt)
#asahi-dev · 2025-06-03 13:23
fl0_idso I assume the s5l8960x is still there
#asahi-dev · 2025-06-03 13:23
fl0_idnickchan are you sure that "apple,aic" cannot be compatible? while the adt has compatible = [aic,3] for the aic, the wdt has compatible = [wdt,t8101, wdt,s5l8960x]
#asahi-dev · 2025-06-03 12:33
fl0_idjannau thx for explaining
#asahi-dev · 2025-06-03 12:33
fl0_idnickchan thx, good to know that's what I was hoping. I have serial I think. not sure about wdt
#asahi-dev · 2025-06-03 11:00
fl0_idsure. I think I looked at that one too. and very little if anything should be extra. I only though about adding the display, as it's a laptop, but hopfeully framebuffer works without as this needs DART or sth I think
#asahi-dev · 2025-06-03 10:57
fl0_idand clusters
#asahi-dev · 2025-06-03 10:57
fl0_idthough I adapted a bit to fit newer style, f.e. using cpu-map
#asahi-dev · 2025-06-03 10:57
fl0_idI was in the past pointed to this as a minimal device tree https://github.com/AsahiLinux/linux/commit/7d2d16ccf15d8eb84accfaf44a0b324f36e39588#diff-845c07f30f0f94856b22d7b50c0ff3d27a961abeffefcdfab01f2e8cd64569cc
#asahi-dev · 2025-06-03 10:56
fl0_idthx I will take a look again later. I'm very aware that there are still issues, likely I did not conisder the ranges property
#asahi-dev · 2025-06-03 10:46
fl0_idnot sure how important those small differences are. I have the c, but supposedly there is also an m variant
#asahi-dev · 2025-06-03 10:46
fl0_idI at least have some inconsistency still where sometimes I have j514 but in other places like the bindings I use j514c
#asahi-dev · 2025-06-03 10:45
fl0_idI didn't give any errors after adding the bindings
#asahi-dev · 2025-06-03 10:45
fl0_idnickchan I did that
#asahi-dev · 2025-06-03 10:44
fl0_idnickchan thx.
#asahi-dev · 2025-06-03 10:39
fl0_idstill have to test it though ...
#asahi-dev · 2025-06-03 10:39
fl0_idmade a super basic M3 device tree https://github.com/step21/linux-asahi/commit/403b936c9e97362dbffee3a01f0f3b21fbea6bf2
#asahi-dev · 2025-06-02 22:38
fl0_idah ok so compatible etc is in Documentaton/devicetree/bindings I think...
#asahi-dev · 2025-06-02 22:37
fl0_idfor the second, I though the answer should be easy to find but well...
#asahi-dev · 2025-06-02 22:22
fl0_idand is there a good way to tell make dtbs_check to only redo one folder / files? make dtbs_check DTB_SCHEMA_FILES=/folder but AFAIK that is only for schema files, not dts
#asahi-dev · 2025-06-02 22:20
fl0_idok dumb question potentially. in the DTs, when you have "compatible = "apple,icestorm";" or similar, where are these defined? I naively updated them, but then dtc complains that it's not defined...
#asahi-dev · 2025-06-02 22:03
fl0_idmixi thx.
#asahi-dev · 2025-06-02 16:22
fl0_iddoes the firmware version matter?
#asahi-dev · 2025-06-02 16:21
fl0_idamarioguy well yeah that's good enough
#asahi-dev · 2025-06-02 16:01
fl0_idfl0_id thx. I guess the mistake was copying just the relevant files separately then
#asahi-dev · 2025-06-02 15:56
fl0_idfor testing syntac compatibility of device trees, is there a good way to get better errors out of the compiler / should it be possible to compile outside of the kernel tree (with includes added into the relevant directory)? I get syntax errors quite at the beginning, but do not really see an error when compring it to others.
#asahi-dev · 2025-06-02 12:22
fl0_idchadmed in some other device trees it's the same, so it seems reasonable
#asahi-dev · 2025-06-02 11:20
fl0_idsame haha
#asahi-dev · 2025-06-02 11:14
fl0_id newb question, in my m3 max device tree dump there is "#address-cells = 1 \n #size-cells = 0" - is that possible or does it mean that the dump is wrong?
#asahi-dev · 2025-06-02 07:13
fl0_idif amarioguy comes back, you can tell him I could test for m3 max, but ideally he would provide like a python script to run in proxy mode or similar...
#asahi-dev · 2025-05-28 14:33
fl0_id(I quoted those from memory so they might not be exactly correct)
#asahi-dev · 2025-05-28 14:32
fl0_idzink_context, zink_screen and memory page sizes for vn_renderer seemed most likely to be relevant
#asahi-dev · 2025-05-28 14:31
fl0_idchaos_princess well those were the patches being applied in the fedora package. some seemed unrelated like "gnome-sth-fix" and others obsolete. But you could very well be right ofc :)
#asahi-dev · 2025-05-28 13:56
fl0_idyeah, I assume so. but I have no idea which parts might only be relevant for one or the other :)
#asahi-dev · 2025-05-28 13:54
fl0_idthx

plus ›