user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dabaiste^ has joined #asahi-dev
chadmed has joined #asahi-dev
user982492 has joined #asahi-dev
dabaiste^ has quit [Remote host closed the connection]
yuyichao_ has quit [Ping timeout: 480 seconds]
amarioguy has quit [Ping timeout: 480 seconds]
NoahSchill[m] has joined #asahi-dev
doggkruse has joined #asahi-dev
DragoonAethis has quit [Quit: hej-hej!]
DragoonAethis has joined #asahi-dev
yuyichao_ has joined #asahi-dev
amarioguy has joined #asahi-dev
riker77_ has joined #asahi-dev
skipwich has quit [Quit: DISCONNECT]
riker77 has quit [Ping timeout: 480 seconds]
riker77_ is now known as riker77
skipwich has joined #asahi-dev
skipwich has quit [Quit: DISCONNECT]
skipwich has joined #asahi-dev
skipwich has quit []
AlvaroFigueroa[m] has joined #asahi-dev
skipwich has joined #asahi-dev
skipwich has quit []
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
doggkruse has joined #asahi-dev
phiologe has joined #asahi-dev
PhilippvK has quit [Ping timeout: 480 seconds]
amarioguy has quit [Ping timeout: 480 seconds]
skipwich has joined #asahi-dev
nicolas17 has quit [Quit: Konversation terminated!]
skipwich has quit []
kov has quit [Quit: Coyote finally caught me]
kov has joined #asahi-dev
skipwich has joined #asahi-dev
skipwich has quit []
skipwich has joined #asahi-dev
KDDLB has quit [Remote host closed the connection]
kode54 has quit [Remote host closed the connection]
KDDLB has joined #asahi-dev
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<jannau>
Glanzmann: FYI linux boots without obvious crashes on M1 Ultra (using the j314c dtb, that means it uses HW of the first die)
<jannau>
I guess that means I have to write a devicetree tonight
<jannau>
marcan: did you spent more thought of how to avoid the manual duplication? I will probably start with a minimal dts with duplication
kode54 has joined #asahi-dev
<Glanzmann>
jannau: Thank you for the update. :-)
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marcan>
jannau: nest two buses inside soc {} with ranges translating into the offset, and #include things into both
<marcan>
we need to split t600x into different files
<marcan>
one for the base that's in M1 Pro and Max and is only on die 0 of Ultra (system core, stuff like smc and ans), one for the parts that are the intersection of both dies in Ultra and Pro, and one for the parts that are extra in Max and on both dies in Ultra
<marcan>
then (re)define a simple macro to mangle the labels
<marcan>
just something like #define L(x) d0_##x will do, before including anything in die 0
<marcan>
then redefine for die 1
<marcan>
and wrap all the labels with that
<marcan>
I'm happy to give it a shot myself if you can wait though :-)
<marcan>
mine should be coming in soon, though I'll wait a few days after that before proper bring-up
<kode54>
I see there was a kernel update today
<marcan>
that was yesterday, it's just a packaging thing
<marcan>
ignore it
<kode54>
gotcha
<marcan>
it has literally 0 changes
<marcan>
only kernel-headers changed
<marcan>
and metadata
<kode54>
okay, thanks for the heads up
<jannau>
makes sense. I'll try to verify that the second die works and wait otherwise. I should work on spi_hid anyway
jakebot6 has joined #asahi-dev
jakebot has quit [Read error: Connection reset by peer]
<jannau>
and 40% of that is just mapping the frame buffer
MajorBiscuit has joined #asahi-dev
Major_Biscuit has joined #asahi-dev
MajorBiscuit has quit [Ping timeout: 480 seconds]
jakebot has quit [Read error: Connection reset by peer]
jakebot has joined #asahi-dev
amarioguy has joined #asahi-dev
amarioguy has quit [Remote host closed the connection]
the_lanetly_052 has joined #asahi-dev
<chadmed>
im making a list of redundant/outdated wiki pages to get rid of
<chadmed>
any requests?
klaus has joined #asahi-dev
klaus has quit []
jakebot has quit [Read error: Connection reset by peer]
jakebot has joined #asahi-dev
kameks has joined #asahi-dev
<chadmed>
jannau: am i right in understanding that on the M1 Ultra, only one die is responsible for whole-chip type stuff like SPI, DCP, etc?
jakebot0 has joined #asahi-dev
jakebot has quit [Ping timeout: 480 seconds]
jakebot0 is now known as jakebot
<Glanzmann>
chadmed: Btw. the DesktopKernel was up2date and had all the config options in. So maybe we should keep it, but I also have the information in my m1-debian repository.
<jannau>
chadmed: most HW is on die 0, ans/nvme, 2 usb-c/thunderbolt ports and 1 gpio controller is used from die 1
<chadmed>
i was thinking that information would probably be better suited somewhere else, since the kernel builds are served up as packages now and we have canonical .config files in the repos
<chadmed>
jannau: thanks, just working on a feature support section for it and didnt want to get anything wrong
<j`ey>
chadmed: I like the idea of documenting config options, the config files in the packages are big, and its not obvious what's important for the AS platforms or not
<Glanzmann>
chadmed: I see. Than leave it deleted. It was a pain to keep it up2date anyway.
<j`ey>
but I suppose most people wont be building kernels, so maybe it's not so important
<chadmed>
j`ey: yeah i was just about to say that info belongs somewhere, but probably in a developer-specific page
<chadmed>
as a sub-section of tethered booting or something like that
<j`ey>
Glanzmann: good to have them on the wiki too
<chadmed>
povik: the only thing about that separation of responsibility between pw/wp is that wp cant actually set up new virtual devices, only manipulate ones pipewire has set up
<chadmed>
so idk what wim is talking about when he says what we want is a job for wireplumber
<Glanzmann>
j`ey: Lets see with what chadmed comes up with and we can always restore the 'DesktopKernel' page or call it somewhere else.
<jannau>
chadmed: it should not matter on which die a specific function is. we should have no problem using them on either die
<povik>
strange, he explicitly says SM creates virtual sinks
<chadmed>
i cannot find a single piece of documentation to suggest that
<chadmed>
the pipewire wiki explicitly says to use pipewire config fragments too
<povik>
could it be a pipewire config fragment still means SM creates the sinks?
<povik>
just that there's a unified config format
<chadmed>
i mean possibly, but you call them in with pipewire and they live in pipewire's config directories, not wireplumbers
<chadmed>
which has its own config fragments and lua scripting engine etc
<povik>
ah
<povik>
i should do some doc reading of my own to have an informed opinion
<chadmed>
it wont take you long, theres not much there :P
Major_Biscuit has quit [Ping timeout: 480 seconds]
<chadmed>
which of course is 90% of the problem
<chadmed>
as i said last week, the vast vast vast majority of hte time it took me to deliver the first batch of FIRs for this machine was me just bumbling around trying to wrap my head around how any of this stuff works because documentation is just nonexistent
Major_Biscuit has joined #asahi-dev
<povik>
hm
Ashutosh[m] has joined #asahi-dev
jakebot3 has joined #asahi-dev
jakebot has quit [Ping timeout: 480 seconds]
jakebot3 is now known as jakebot
chadmed has quit [Remote host closed the connection]
MajorBiscuit has joined #asahi-dev
Major_Biscuit has quit [Ping timeout: 480 seconds]
kameks has quit [Ping timeout: 480 seconds]
manacho[m] has joined #asahi-dev
yuyichao_ has quit [Ping timeout: 480 seconds]
kita99 has joined #asahi-dev
kelito has quit [Ping timeout: 480 seconds]
yuyichao_ has joined #asahi-dev
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi-dev
doggkruse has joined #asahi-dev
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
amarioguy has joined #asahi-dev
user982492 has joined #asahi-dev
auhk[m] has joined #asahi-dev
auhk[m] has left #asahi-dev [#asahi-dev]
auhk[m] has joined #asahi-dev
auhk[m] has left #asahi-dev [#asahi-dev]
auhk[m] has joined #asahi-dev
<sven>
huh, I wondered where that weird enum format thing I did in rtkit.c came from because I couldn’t remember doing that. It’s clang-format :/
Major_Biscuit has joined #asahi-dev
amarioguy has quit [Ping timeout: 480 seconds]
MajorBiscuit has quit [Ping timeout: 480 seconds]
auhk[m] has left #asahi-dev [#asahi-dev]
auhk[m] has joined #asahi-dev
shnert[m] has joined #asahi-dev
<shnert[m]>
Hello, it would be possibility to help with language translation in future segment of project?
Thib[m] has joined #asahi-dev
nicolas17 has joined #asahi-dev
<j`ey>
sven: why it do something weird!
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<tpw_rules>
jannau: so it does have two sockets, but is not NUMA
<jannau>
lscpu seems to count the clusters as sockets so it has 6 sockets
<tpw_rules>
not 4?
<jannau>
2 efficiency sockets and 4 performace sockets
<jannau>
+n
<tpw_rules>
hrm, i feel like i need a graphic
<tpw_rules>
anyway, the "UltraFusion" thing works i guess?
<opticron>
that's certainly an interesting way for lscpu to break up those cores
<jannau>
M1 Pro/Max has 1 cluster with 2 efficiency cores and 2 clusters with 4 performance cores each
<jannau>
M1 Ultr doubles that
<maz>
jannau: do you mind posting a full dmesg somewhere?
<maz>
tpw_rules: I'd be very surprised if it wasn't NUMA. there is no way the interconnect doesn't add cost to the memory path if accessing cross node.
<maz>
(i.e. there is no magic).
<tpw_rules>
i guess maybe linux just hasn't been told that yet?
<tpw_rules>
i mean the way apple worded their marketing made it sound like it's not NUMA, but that's marketing
<maz>
indeed. if you don't put the NUMA description in DT, the kernel doesn't know about it.
<maz>
it doesn't mean it's free.
<tpw_rules>
i guess annotating it as NUMA can't hurt
<AlvaroFigueroa[m]>
Here's an explanation of why it doesn't look like numa, even it "ultrafusion" is just marketing.