#asahi-dev · 2025-04-12 05:21
nickchanturns out some of the socs breaks the cpu iorvbar pattern in /arm-io reg#asahi-dev · 2025-04-12 03:24
halloy-userhi#asahi-dev · 2025-04-12 00:03
chadmeddid that dcp issue with multiple displays end up getting fixed?#asahi-dev · 2025-04-11 14:11
chaos_princessthats a good one#asahi-dev · 2025-04-11 14:10
chadmedcant see the word commissar without thinking of falco or after the fire#asahi-dev · 2025-04-11 14:10
chadmedhttps://www.youtube.com/watch?v=dPCu8mQZWqU#asahi-dev · 2025-04-11 14:00
klausklausyeah that is what i am talking about#asahi-dev · 2025-04-11 13:59
chaos_princessneed a commissaring#asahi-dev · 2025-04-11 13:59
chaos_princess@jannau, @j`ey#asahi-dev · 2025-04-11 13:59
klausklaushe seems not to be his usual self, he is clearly broken#asahi-dev · 2025-04-11 13:59
klausklausyou guys have to help him and keep him in check!#asahi-dev · 2025-04-11 13:59
klausklausman guys, whats up with marcan / lina these days? he should get his mental health checked out ASAP, otherwise he will end up like Near / byuu#asahi-dev · 2025-04-11 13:41
chadmedill take a couple of weeks off work or something#asahi-dev · 2025-04-11 13:41
chadmedi need to buy a new dac and cal mic to redo some of the speaker eq so when i do that ill tune the mics i have access to as well#asahi-dev · 2025-04-11 13:41
jannauI'll do direct comparison with j314. this was just a quick test of the new kernel tag#asahi-dev · 2025-04-11 13:40
chadmedfixable with some EQ and probably tweaking the gains but thats not gonna be triforce #asahi-dev · 2025-04-11 13:40
chadmedoh okay yeah thats probably just the mics then lol #asahi-dev · 2025-04-11 13:39
jannaumuffled#asahi-dev · 2025-04-11 13:30
chadmedunless apple are just using crappier mics, or the mics being where they are affects things somehow. sonically, what are you noticing that's worse? muffled? crackling? #asahi-dev · 2025-04-11 13:28
chadmedjannau: i assume it's going to be some combination of the parameters. the general algorithm shouldnt care what shape the mic array is#asahi-dev · 2025-04-11 12:28
jannauchadmed: tested mics on j493. I think quality is noticeable worse. unsure if that the mic array layout itself, beam-forming parameters or triforce with this mic layout#asahi-dev · 2025-04-10 19:28
chaos_princessesp since everything just uses the 24mhz clock anyway#asahi-dev · 2025-04-10 19:28
jannauagreed#asahi-dev · 2025-04-10 19:27
chaos_princessnot worth it imo#asahi-dev · 2025-04-10 19:27
jannauclocks would be a standard property but with rust we would need of course more bindings to query the rate#asahi-dev · 2025-04-10 19:19
chaos_princessi just do not want to introduce any custom fields into bindings unless absolutely neccesary#asahi-dev · 2025-04-10 19:18
chaos_princessEven if we transfer from adt, if i read it from dt, it would need to be documented in bindings, and those are always a bikeshed-fest about whether it describes hardware or not, and other random issues#asahi-dev · 2025-04-10 19:13
jannauin the m2 pro/max adt I've seen that aop has clock_ids#asahi-dev · 2025-04-10 19:12
jannauthe clocks could probably modelled with fixed rate clocks like we do with other devices#asahi-dev · 2025-04-10 19:12
jannauchaos_princess: we could transfer the values from the ADT in m1n1 but the majority of the parameters looks indeed not as they would describe hardware#asahi-dev · 2025-04-10 16:58
martinryeah that's the first place i looked #asahi-dev · 2025-04-10 16:53
jannauthat's at least what the pdf devicetree spec suggests#asahi-dev · 2025-04-10 16:53
jannauI suppose we should have used the top level model proerty for that instead of our strings#asahi-dev · 2025-04-10 16:47
martinrsven: great thanks :)#asahi-dev · 2025-04-10 16:14
svenand yeah, this would definitely still be interesting:)#asahi-dev · 2025-04-10 16:10
svenhttps://github.com/AsahiLinux/linux/blob/73e1d684c7ac8efe6a343741f973b0d1657c9434/arch/arm64/boot/dts/apple/t8103-j274.dts#L16 you should be able to get that compatible#asahi-dev · 2025-04-10 13:53
chaos_princessthat kind of stuff usually gets put into the device tree#asahi-dev · 2025-04-10 13:53
martinr(i.e. J313AP for the M1 MBA)#asahi-dev · 2025-04-10 13:51
martinrjannau: ok great, currently i've got the unlock key hard-coded for my device (obviously undesirable) - is there a mechanism for accessing the mac device name from the kernel? (which is where the key is derived from)#asahi-dev · 2025-04-10 13:42
jannauwith that we have macvdmtool functionality on linux#asahi-dev · 2025-04-10 13:42
jannaumartinr1: welcome back. Yes, we're still interested in this. The other interesting vdm command is enabling the uart (remote and locally)#asahi-dev · 2025-04-10 13:34
alyssaso if not for a freeze i'd expect a migration to testing at the end ofmay#asahi-dev · 2025-04-10 13:33
alyssacy8aer: I mean the upstream Mesa package isn't released until may#asahi-dev · 2025-04-10 13:23
martinrsven: i've got an initial PoC of a tipd driver that can unlock the ACE chip and send VDMs (just tested remote device reboot so far). is this still needed/or is there interest in this feature? if so, I can spend some time extending it to the other VDM commands#asahi-dev · 2025-04-10 05:52
cy8aerhm, or not?#asahi-dev · 2025-04-10 05:50
cy8aertobhe_: Right it is too late for trixie#asahi-dev · 2025-04-09 22:26
tobhenothing wrong with that as long as you still get your CVEs fixed every once in a while#asahi-dev · 2025-04-09 22:19
nicolas17meanwhile I still have systems on bullseye because of procrastination /o\#asahi-dev · 2025-04-09 22:15
tobhecy8aer: everything is freezing right now. I'm dealing with three freezes around the same time /o\#asahi-dev · 2025-04-09 22:13
tobhealyssa: oh nice :) I will forward that to our group