ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
pb17 has joined #asahi-dev
jolexxa has joined #asahi-dev
jolexxa has quit [Quit: jolexxa]
chrisl has joined #asahi-dev
chrisl has quit [Ping timeout: 480 seconds]
croissant has quit [Quit: Leaving]
nora_ has joined #asahi-dev
nora has quit [Ping timeout: 480 seconds]
pb17 has quit [Ping timeout: 480 seconds]
chrisl has joined #asahi-dev
chrisl has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi-dev
john-cabaj has joined #asahi-dev
chrisl has joined #asahi-dev
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #asahi-dev
kenzie7001 has quit [Ping timeout: 480 seconds]
al3xtjames has joined #asahi-dev
tobhe has quit [Ping timeout: 480 seconds]
kenzie7001 has joined #asahi-dev
chrisl has joined #asahi-dev
c10l has quit [Ping timeout: 480 seconds]
nora has joined #asahi-dev
chrisl has quit [Ping timeout: 480 seconds]
nora_ has quit [Ping timeout: 480 seconds]
john-cabaj has quit [Ping timeout: 480 seconds]
<nickchan>
some sysregs has changed meaning across chip generations, so apple_regs.json kind of getting tricky
<nickchan>
s3_4_c15_c2_6 used to be VMSA_LOCK_EL1 but it is VMSA_LOCK_EL12 in current chips
<nickchan>
s3_0_c15_c13_0 used to be HID11_EL1 but now it is "BIU_TLIMIT"
riker77 has quit [Quit: Quitting IRC - gone for good...]
chrisl has quit [Ping timeout: 480 seconds]
riker77 has joined #asahi-dev
david has joined #asahi-dev
pb17 has quit [Ping timeout: 480 seconds]
<jannau>
maz: did you ever test m1n1's proxy protocol using UART over CS?
david4 has quit [Ping timeout: 480 seconds]
Sebastian2 has joined #asahi-dev
<maz>
jannau: is that (for example) loading the kernel using the CS UART?
<maz>
if so, then no, I always used the USB2.0 side of the connection.
<maz>
that's how all my devices boot.
<maz>
and I suspect you would have to implement the UART speed change side of things, as you don't want to upload something big at 115200.
<maz>
or do I have the wrong end of the stick?
<jannau>
yes, although not really interested in booting kernel but getting information from m1n1 and chainloading a new m1n1 during bringup
<maz>
as long as m1n1 sticks to 115200, you should be OK (baring bugs in the UART<->USB code).
Sebastian2 has quit [Quit: Sebastian2]
<david>
I am unable to run hypervisor on 15.0.1 m1 m1n1 it throw an exception on CPU 0 EXCEPTION_LOWER/SYNC. does anyone face this problem
pb17 has joined #asahi-dev
midou has quit [Remote host closed the connection]
midou has joined #asahi-dev
<jannau>
the status output certainly breaks things but my fusb breakout setup isn't wotking with the mu uart either. tx on device side works but rx might be broken on m4