#
✕ nick:povik
#asahi-dev · 2023-04-27 11:16
povikwill u-boot under some conditions turn off power domains?
#asahi-dev · 2023-04-27 08:49
povikif you are looking for what to be sniped with next...
#asahi-dev · 2023-04-27 08:49
povikchadmed: i am borrowing an imac to write that one codec driver we are missing
#asahi-dev · 2023-04-26 19:55
povikand you should let m1n1 do the same
#asahi-dev · 2023-04-26 19:55
povikmacos will most likely set the DAPF according to that ADT property
#asahi-dev · 2023-04-26 19:53
povikso don't take the above absolutely
#asahi-dev · 2023-04-26 19:53
povikbut e.g. the data section of SIO's firmware is mapped by DART
#asahi-dev · 2023-04-26 19:51
povikdepending on the coprocessor some mmio regions might be visible to it without mapping by DART nor DAPF
#asahi-dev · 2023-04-26 19:50
poviksomeone can correct me on that
#asahi-dev · 2023-04-26 19:50
povikChaosPrincess: typically data that's shared between the application processor and the coproc will be mapped by DART, data that's for the coproc only, and the foreign mmio regions it accesses, will be mapped by DAPF
#asahi-dev · 2023-04-26 19:42
povikjannau: thanks!
#asahi-dev · 2023-04-26 19:42
povikthough you might want to inspect the DAPF entries just to see what gets mapped
#asahi-dev · 2023-04-26 19:42
povikso it will get set by dapf_init_all() probably and you don't need to care about it
#asahi-dev · 2023-04-26 19:41
povikthat node has filter-data-instance-0 and dapf.c in m1n1 will know how to set the DAPF according to that
#asahi-dev · 2023-04-26 19:41
povikChaosPrincess: that instance= value you copied seems to be from dart-ave
#asahi-dev · 2023-04-26 19:36
povikah remember myself asking the same question
#asahi-dev · 2023-04-26 19:36
povik21:35 < ChaosPrincess> whats dapf
#asahi-dev · 2023-04-26 19:34
povikok then, you seem to know your microbiology better than me :p
#asahi-dev · 2023-04-26 19:33
poviklooks like a DNA sequence :D
#asahi-dev · 2023-04-26 19:29
povikor ADT subnodes?
#asahi-dev · 2023-04-26 19:29
povikinstances stuff meaning some constant register imprint in silicon?
#asahi-dev · 2023-04-26 19:23
povikah apple memory cache controller probably
#asahi-dev · 2023-04-26 19:22
povikgoogles AMCC
#asahi-dev · 2023-04-26 19:00
povikhappy about the other thing getting reproduced :)
#asahi-dev · 2023-04-26 19:00
povik\o/
#asahi-dev · 2023-04-26 18:50
povikit doesn't seem to be a power-domain thing after all, at least the failures still occur without turning off any domains, and with resets disabled
#asahi-dev · 2023-04-26 18:50
poviki will see try flipping on SIO and see if i can reproduce
#asahi-dev · 2023-04-26 18:49
povikanything that's similar to the one you were getting boot failures with, if it isn't too bloated
#asahi-dev · 2023-04-26 18:49
povikjannau: do you have a .config that might be worth trying? see if i can reproduce it?
#asahi-dev · 2023-04-26 18:48
poviki only get them on a full-fledged OS install which makes debugging hard
#asahi-dev · 2023-04-26 18:48
povik[ 2.335642] apple-sio 236400000.sio: error -ETIME: SIO did not boot
#asahi-dev · 2023-04-26 18:48
poviknow if only we could figure out those :/
#asahi-dev · 2023-04-26 18:44
povikah, i was wondering about that, right
#asahi-dev · 2023-04-26 18:38
povikhttps://github.com/AsahiLinux/m1n1/pull/286/commits/37c6c06d0871192da8218b22c775e3b4ef7f71f9
#asahi-dev · 2023-04-26 18:38
povikon the other hand this made the errors go away
#asahi-dev · 2023-04-26 18:38
povikjannau: i might be messing something up in the installation of a patched u-boot version (this is on a nixos install), but it's unlikely, i tried changing the font size and that took effect
#asahi-dev · 2023-04-26 18:23
povikhuh
#asahi-dev · 2023-04-26 18:19
povikthough there doesn't seem to be anything that prohibits the overlap of the /memory node and the reserved regions, the devicetree spec even has an example that's overlapping, so still not sure what the u-boot error is about
#asahi-dev · 2023-04-26 18:17
povikah, of course the devicetree spec itself discusses /memory
#asahi-dev · 2023-04-26 18:12
povikare the semantics of the memory@ node documented somewhere?
#asahi-dev · 2023-04-26 18:11
povikok, that's easy then :)
#asahi-dev · 2023-04-26 18:11
povikand i guess moving dt_set_memory in m1n1's kboot.c behind the sio setup is all one needs to do to cut out the sio reserved regions from the memory@ node...
#asahi-dev · 2023-04-26 18:01
povikwhich seem to be the only ones that fall within the span of the memory@80000000 node
#asahi-dev · 2023-04-26 18:01
povikit complains about the four sio-firmware-data@... reserved nodes
#asahi-dev · 2023-04-26 18:00
povikhere are the relevant devicetree nodes: https://tpaste.us/wxa5
#asahi-dev · 2023-04-26 17:59
povik^ that's in u-boot
#asahi-dev · 2023-04-26 17:46
povikok, upping both LMB_MAX_REGIONS and LMB_RESERVED_REGIONS to 64 doesn't make the SIO reservation errors go away
#asahi-dev · 2023-04-24 14:08
povik:D
#asahi-dev · 2023-04-21 16:32
povikthe sio boot failures seem most likely to be a power domain dependency unmodeled in ADT, like the dependency on ps_spi_p when any DMA is active :/
#asahi-dev · 2023-04-21 16:29
povik(and is wrong)

plus ›