nico_32_ has quit [Remote host closed the connection]
yamii_ has joined #asahi-dev
yamii has quit [Read error: Connection reset by peer]
JTL has quit [Remote host closed the connection]
phiologe has joined #asahi-dev
PhilippvK has quit [Ping timeout: 480 seconds]
nico_32 has joined #asahi-dev
JTL has joined #asahi-dev
mps has quit [Ping timeout: 480 seconds]
kov has quit [Quit: Coyote finally caught me]
kov has joined #asahi-dev
systwi_ has quit [Read error: Connection reset by peer]
systwi has joined #asahi-dev
merry_ has joined #asahi-dev
merry has quit [Ping timeout: 480 seconds]
igrom[m] has joined #asahi-dev
mps has joined #asahi-dev
dsrt^ has joined #asahi-dev
MajorBiscuit has joined #asahi-dev
Telvana2 has joined #asahi-dev
Telvana has quit [Read error: Connection reset by peer]
nicolas17 has quit [Quit: Konversation terminated!]
BahramAbasov[m] has joined #asahi-dev
Telvana2 has quit []
Telvana has joined #asahi-dev
the_lanetly_052 has joined #asahi-dev
millenialhacker has joined #asahi-dev
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi-dev
akemin_dayo has joined #asahi-dev
riker77 has quit [Ping timeout: 480 seconds]
riker77 has joined #asahi-dev
the_lanetly_052__ has joined #asahi-dev
nicklas[m] has joined #asahi-dev
the_lanetly_052 has quit [Ping timeout: 480 seconds]
bps has joined #asahi-dev
<millenialhacker>
Does anyone know how to interpret "segment-ranges" property in ADT ?
<sven>
for co-processors? iirc those are the memory regions of the firmware
<jn>
i haven't seen an example, but based on the name, it'd try to read it as a address translation map, like "ranges"
<sven>
each entry should contain the iova, the physical address and the length
<sven>
and there should be a segment-names that sometimes even tells you the name of the segment (e.g. TEXT or DATA)
<millenialhacker>
What I know so far it's that it should include IOVA / PHY / LENGHT and some REMAP (???) stuff. but when I try to read it from my ADT, it makes no sense.
<millenialhacker>
if I split in 8 bytes (numbers I see doesn't look IOVA or PHY address)
<jannau>
for DCP I see 32 bytes per segment, first 8 byte seems to be physical address in 32-bit cells, little endian
<jannau>
the physical address should be in /carveout-memory-map
<WhyNotHugo>
I'm trying to install NixOS on an M1. I intend to use the same kernel sources as Asahi. What `config` options need to be different from the defaults for M1 support?
<millenialhacker>
@jannau: yes, it's 32 bytes per segment, each segment divided in four 8-bytes value. What do you mean by phy-add in 32-bits cells?
<_jannau_>
millenialhacker: values in devicetree are represented as cells of u32
<jn>
how do two 32-bit cells combine to form a 64-bit number, in ADT?
<jn>
little endian as inside a cell, or big-endian as in other devicetree implementations?
<_jannau_>
not sure. not even sure if segment-ranges is expressed in cells. The ADT is a mess. it's just how I think about values in the device trees
millenialhacker has quit [Quit: Konversation terminated!]
<null>
winter: 9
<null>
SOrry, that was meant to be `/window 9` but I hit the wrong key
<maz>
null: I though you were playing "Riot in cell block #9"...
___nick___ has joined #asahi-dev
<marcan>
jn: little endian. ADT doesn't really use cells, it's just "whatever Apple felt like throwing in there"
<marcan>
though it does align sizes to 4 bytes IIRC
<marcan>
but there are whole C structs in there and such
<jn>
i see
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
dsrt^ has quit [Remote host closed the connection]
<jannau>
I splitted commits between t600x and t8103 to make the rebasing simpler. t600x is splitted so that we could submit the devicetrees for all devices for 5.19, i.e. nvme is in, cpufreq is not
<jannau>
still missing dt-bindings updates for mac studio (and the macbooks if we haven't done it already)
<jannau>
only the merged tree tested so far (single boot on the mac studio)