04:42 <DmitrySharshakov[m]> chadmed: yes, although Julian wrote that it should be okay for daily use, but still Asahi is a distro which is most likely to have to deal with Pro Audio production workloads etc. So let's stay with 0.4 which is familiar to people. Then I'll first fix correctness and merge into 0.4 (maybe without hardware volume if that'd be hard). This 0.4.x can then be shipped and I'll continue my work on WP 0.5, improving configuration

04:42 <DmitrySharshakov[m]> discovery mechanism as well as optimizing things like hardware volume

05:21 <DmitrySharshakov[m]> Notice: it's worth testing at least something before continuing. Did the config I wrote work for somebody?

06:02 <chadmed> tbh given the state of PW/WP documentation and the general attitude of devs towards issues being "lol just fix it yourself" i wouldnt trust their assessments of user readiness as far as i could throw a fujitsu m12

06:02 <chadmed> plus the supposedly massive api change _will_ result in users having questions and the like and if we are packaging up and shipping an untested branch then we would be expected to field those questions ourselves

06:03 <chadmed> no one here wants to do that just for the sake of rushing speaker support out the door

06:03 <chadmed> we have the When It's Done(tm) advantage, we dont have any particular deadlines we need to rush towards and so we can afford to just wait until it's out and settled

06:10 <chadmed> and besides, the current handling works and is stable for people who want it badly enough to go through the DT editing process, the stuff we're doing now is just to ensure that its maintainable long term and can be generalised for arbitrary devices. to me, that goal in and of itself is nowhere near important enough to warrant pushing beta branches to users and assuming the responsibility for maintaining them

07:53 <DmitrySharshakov[m]> <chadmed> "and besides, the current..." <- Well, no DT editing should be needed after updated audio bits go in (volume and HPF caps are in place in that series)

07:53 <DmitrySharshakov[m]> <chadmed> "plus the supposedly massive..." <- Yes, so it'll be going into 0.4 for now and 0.5 just going it's way as an unstable branch

07:55 <DmitrySharshakov[m]> Just need some feedback on how do my patches fit the use case + I'll fix some pieces and et voila we have it in a released WP version. Then 0.5 comes implementing a better config discovery mechanism

07:57 <DmitrySharshakov[m]> The advantage should be used when updated audio bits (povik sent those for review for Asahi branch yesterday) land, so would be great to have in less time than WP 0.5

17:47 <leidenfrost[m]> Hi all. I'm trying to get into Asahi development and I'm reading the SW:Hypervisor wiki page. Question, when it says "install m1n1 as custom boot object" does it mean to do it through the installer? Or to do it manually?

17:49 <j`ey> leidenfrost[m]: you can use the installer

17:51 <sven> for running the hv as well? Don’t you need a full macOS install for that to work?

17:52 <j`ey> oh sorry, that page is about macOS under m1n1

17:53 <leidenfrost[m]> Yes. My thought was to run the hv on top of my macOS install, and watch the debug info through iTerm or something like that.

17:53 <j`ey> leidenfrost[m]: If you want ro run macOS under the hv, you cant use the asahi-installer

17:53 <j`ey> leidenfrost[m]: do you have a second computer to develop on?

18:15 <leidenfrost[m]> j`ey: yes, an x86 arch machine

18:16 <j`ey> ok well you'd see the logs on that, not on the mac itself

18:34 <leidenfrost[m]> Ok I see. It seems there's no way to have something like a local virtual uart interface

21:06 <jannau> povik: "input: Mac Studio J375 integrated audi Headphone Jack as /devices/platform/sound/sound/card0/input1"

21:06 <jannau> are we missing an 'o' somewhere or is the name truncated?

21:14 <jannau> headphones / headset are working

21:19 <jannau> 31 chars, so probably truncated to 32 - 1 for '\0'

21:21 <povik> yeah, truncated

21:21 <povik> 23:14 < jannau> headphones / headset are working

21:21 <povik> nice

21:23 <povik> i guess we will have to put in something shorter for the name

21:23 <povik> which is a shame since i really wanted to point out these are the integrated sound peripherals

21:23 <jannau> internal is a little shorter

21:24 <povik> ha, saves the o

21:24 <kettenis> just drop thw word?

21:26 <povik> as i said, in a card list i would like to see these are the internal peripherals

21:26 <jannau> I kind of agree, external audio devices would not have the same name

21:26 <povik> although that could be just silliness on my end

21:26 <povik> yeah

21:27 <jannau> nobody is going to sell "Mac Studio J375" usb/pcie soundcards, Apple's trademark lawyers will ensure that

21:27 <povik> :)

22:00 <jannau> povik: cs42l84 works on the m2 mbp13 as well with an trivial patch

22:03 <jannau> povik: https://gist.github.com/jannau/5e4801a5af9707f769976e976f2c0362

22:06 <povik> it's this, right?

22:06 <povik> + status = "okay";

22:06 <povik> there's no interference with the speaker amps

22:06 <jannau> yes, the i2c bus was disabled

22:06 <povik> ok

22:06 <povik> the speakers should be disabled on the sound node already

22:06 <povik> so they need not be disabled on the speaker amps themselves

22:06 <povik> that should be safe

22:08 <jannau> yes, i2c1 should be enabled then as well

22:09 <povik> ah, thanks, will do those on bits-update/000-devicetree

22:16 <jannau> enabling the speaker amps is no problem, updated https://gist.github.com/jannau/5e4801a5af9707f769976e976f2c0362 if you haven't already done so

22:20 <jannau> t8112-j413.dts will probably work with the same changes but I guess marcan can add that after testing

22:34 <povik> pushed (done the j413 changes too)