#asahi-dev · 2025-03-21 11:28
dylantaylorAnd, doing a quick sanity check using https://mictests.com/ I can see that input is working. #asahi-dev · 2025-03-21 11:27
dylantaylorI now see "Built-in Audio Multichannel" in the input devices list#asahi-dev · 2025-03-21 11:27
dylantaylorGreat news, that seems to have worked. :)#asahi-dev · 2025-03-21 11:26
fl0_idguess we'll find out haha#asahi-dev · 2025-03-21 11:25
chaos_princesswas it not snd_soc_apple_aop?#asahi-dev · 2025-03-21 11:25
dylantaylorOkay, awesome. I'm just set GRUB_CMDLINE_LINUX_DEFAULT="rhgb quiet rootflags=subvol=root snd_soc_aop.mic_check_123=1" in /etc/default/grub and ran sudo grub2-mkconfig. I see the option in /boot/loader/entries so I'm going to reboot and give that a try.#asahi-dev · 2025-03-21 11:18
jannauthat's the same kernel as asahi-wip#asahi-dev · 2025-03-21 11:17
chaos_princessif it failed that early, it might be#asahi-dev · 2025-03-21 11:17
dylantaylorAh, would this work on the 6.13.7-401.asahi.fc42.aarch64+16k kernel I'm running in F42 beta, or should I try to build asahi-wip?#asahi-dev · 2025-03-21 11:16
jannauI doubt snd_soc_aop is reloadable#asahi-dev · 2025-03-21 11:16
jannaujust add above parameter to the kernel command line#asahi-dev · 2025-03-21 11:15
jannauno need to revert anything. I added `snd_soc_aop.mic_check_123=1` especially to allow this#asahi-dev · 2025-03-21 11:15
dylantaylorCan you point me at the specific commit? I could try building and installing the kernel with a little bit of guidance and I can let you know if it works.#asahi-dev · 2025-03-21 11:14
chadmeddylantaylor: there is a kernel commit you need to revert which prevents aop's audio subdevice from probing. there's not really anything left to "develop" though, i just need to validate it on a j293#asahi-dev · 2025-03-21 11:12
fl0_idPaulFertser ok this is getting kinda OT, maybe weh shoudl move it#asahi-dev · 2025-03-21 11:00
dylantaylorThis isn't a support request; I'd love to be able to assist with the development efforts here in order to have mics working on every Apple silicon device.#asahi-dev · 2025-03-21 10:58
dylantaylorMy guess is that I need to build the asahi-wip branch of the kernel and install that in conjunction with the mics branch of asahi-audio, but wanted to see if my assumptions were correct here.#asahi-dev · 2025-03-21 10:53
dylantaylornode is visible to wireplumber for it to work.#asahi-dev · 2025-03-21 10:53
dylantaylorI have a "j293" 13 inch M1 MacBook Pro (2020). I saw that the microphone support for this exact model is not ready but it is for every other model. I'm interested in helping with testing and troubleshooting this mice support. I did a sudo make install of the patch at https://github.com/AsahiLinux/asahi-audio/tree/mics but do not see the input device. I was wondering if I also need to apply a kernel patch so that the #asahi-dev · 2025-03-21 03:27
nickchanthere's one other patch about rtkit there i don't know how it has to do with cpufreq but that's upstream as well#asahi-dev · 2025-03-21 03:21
nickchani already sent 130-cpufreq upstream#asahi-dev · 2025-03-20 23:29
PaulFertserfl0_id: it's kind of risky being passionate about something that can be ruined any moment by money-driven people who have the ultimate control after all.#asahi-dev · 2025-03-20 23:13
fl0_idPaulFertser I know that. But yeah not all and not everybody is paid to work on it full time like rrendec said#asahi-dev · 2025-03-20 23:08
rrendechaha, it is but many of them are paid to do other things too (myself included) or mainly other things#asahi-dev · 2025-03-20 23:03
PaulFertserYou say it as if Linux isn't meant to be the product of full time paid developers these days.#asahi-dev · 2025-03-20 23:01
fl0_idbut yeah ofc that would be good#asahi-dev · 2025-03-20 23:01
fl0_idPaulFertser true, but that sounds like a fulltime job almost#asahi-dev · 2025-03-20 22:57
PaulFertserA practical way would be for someone to actually obtain at least the most popular brcmfmac devices and to test all the changes on all of them properly, and to become a real brcmfmac maintainer.#asahi-dev · 2025-03-20 22:56
fl0_idPaulFertser yeah I know, and it shouldn't. just aa hypothetical#asahi-dev · 2025-03-20 22:55
PaulFertserfl0_id: such a large scale code duplication wouldn't be accepted either.#asahi-dev · 2025-03-20 22:54
PaulFertserAlso imagine the maintainers getting paid by Intel or similar, and the company requires certain performance and deadlines and such.#asahi-dev · 2025-03-20 22:53
fl0_idyeah good point. guess a new driver would be easier almost#asahi-dev · 2025-03-20 22:53
PaulFertserfl0_id: those dberlin patches actually did regress functionality of the SDIO module I tried them on.#asahi-dev · 2025-03-20 22:52
PaulFertserRaspberryPi. What would justify the risk of breaking it unless the patch author is really convincing and also has tested important things on at least the most popular older models?#asahi-dev · 2025-03-20 22:52
PaulFertserfl0_id: well, it's supposed to happen that way but the whole subsystem thing changed lately too (Kalle Vallo quitting) and also imagine you're a maintainer of all the Linux wireless and you're offered a patch that potentially affects plenty of hardware without any proper documentation for the kernel <-> firmware API. And you know that the driver as it currently is works good enough on#asahi-dev · 2025-03-20 22:48
fl0_id(just curious, tryng to learn)#asahi-dev · 2025-03-20 22:48
fl0_idPaulFertser won't the subsystem maintainer then deal with it, if the original maintainer is mia?#asahi-dev · 2025-03-20 22:46
PaulFertserrrendec: also, brcmfmac was essentially unmaintained and I guess it still is, so the experience upstreaming anything to it might be frustating.#asahi-dev · 2025-03-20 22:43
PaulFertserrrendec: hi. I provided some feedback on brcmfmac patches testing it on AzureWave AW-CM256SM SDIO module (brcmfmac43455-sdio.bin firmware) but dberlin didn't really follow up.#asahi-dev · 2025-03-20 21:42
jannaum2 mini is the ideal target for wifi. a large part of it is for supporting the 6ghz capable bcm4388 used in the m2 mini#asahi-dev · 2025-03-20 21:29
rrendecthanks#asahi-dev · 2025-03-20 21:29
rrendecsounds good#asahi-dev · 2025-03-20 21:28
chaos_princessi guess you can start reading the bits branch in chronological order, package it into self contained features and start sending#asahi-dev · 2025-03-20 21:28
rrendecwell, then wifi it is; any suggestions on how/where I should start?#asahi-dev · 2025-03-20 21:11
svengetting wifi upstream would also be very nice since that branch should also help some other modern Broadcom boards iirc #asahi-dev · 2025-03-20 21:11
svenit does #asahi-dev · 2025-03-20 21:09
rrendecit's also something I can at test at least partially on the hw I have, which is a Mini M2, assuming it uses the brcmfmac driver (I haven't checked)#asahi-dev · 2025-03-20 21:08
rrendecall right, it looks like there isn't much I can work on in those branches I mentioned, so maybe 080-wifi is a better choice after all#asahi-dev · 2025-03-20 20:57
jannaukernel builds now#asahi-dev · 2025-03-20 20:53
jannauthey bring us closer to gentoo-{kernel,sources}. resolving the issue is just a minor annoyance but I think we have to just do it once per kernel release