#asahi-alt · 2026-09-12 18:37
j`eyscoopy[m]: no#asahi-alt · 2026-09-12 18:36
scoopy[m]oh did the llm policy get changed recently ?#asahi-alt · 2026-09-12 18:34
mpskernel maintainers for ARM/APPLE MACHINE SUPPORT are asahi members afaik#asahi-alt · 2026-09-12 18:27
chaos_princessdon't worry about it#asahi-alt · 2026-09-12 18:19
Tomus[m]Like if this happens Asahi devs will either branch out from the main kernel entirely in this field or accept the ai generated driver that breaks their policy#asahi-alt · 2026-09-12 18:19
Tomus[m]What will happen if omarchy team manages to merge the sep driver they made upstream#asahi-alt · 2026-09-12 18:04
lacamar[m]There are AI patches being merged into the kernel all the time, so in a way this is already happening. But I guess the real concern is the violation of copyright by AI regurgitating tainted code and that getting upstream#asahi-alt · 2026-09-12 15:50
beastdTomus[m]: worries me as well :-/#asahi-alt · 2026-09-12 14:42
Tomus[m]The thing that worries me is what will happen if these drivers will get rejected from Asahi kernel tree for being ai generated and what will happen if omarchy manages to upstream an ai generated driver, and will Asahi adopt it#asahi-alt · 2026-09-12 14:37
mpswonder why is complicated to open terminal and type 'curl $url_of_distro_installer | sh'#asahi-alt · 2026-09-12 14:34
beastdreminds me of setting up recurring donations to asahi#asahi-alt · 2026-09-12 14:34
beastdasahi policy about that is quite on point#asahi-alt · 2026-09-12 14:32
mpsand when see "vibe coding" words I just smile#asahi-alt · 2026-09-12 14:31
mpsas such*#asahi-alt · 2026-09-12 14:31
mpsyea, also I see such#asahi-alt · 2026-09-12 14:30
beastdfrom the looks of omarchy and what i read from dhh, i guess they plan a wild mix of vibe coding stuff to perfection. but really dunno. think i don't know a single person from that community.#asahi-alt · 2026-09-12 14:29
beastdnot even sure one can even count omarchy as a distro. but at least in the looser sense i guess yes#asahi-alt · 2026-09-12 14:29
beastdfrom that post i understand that they want to mess with all parts kernel, tools, and their own distro#asahi-alt · 2026-09-12 14:28
beastdthink that is true. there is only the concept of a flag ship distro AFAIK#asahi-alt · 2026-09-12 14:26
mpsI view asahi as kernel patches and tools needed to install any distro on apple M, and not as distro#asahi-alt · 2026-09-12 14:17
mpsbeastd: just read it. funny ;p#asahi-alt · 2026-09-12 14:05
j`eybeastd: nope#asahi-alt · 2026-09-12 14:02
beastdthis is not a cooperation thing or something, right?#asahi-alt · 2026-09-12 14:02
beastdhmm I was just by pure accident (i don't ever plan to use Omarchy) reading a blog post by Omarchy about Omarchy M (dates to 2026-09-11) . in my mind it reads really condescending (or even hostile) to the Asahi project#asahi-alt · 2026-09-12 13:49
jannauI'll update the kernel ebuilds later today#asahi-alt · 2026-09-12 13:46
jannaudowngrading to wpa_supplicant 2.11 should work#asahi-alt · 2026-09-12 13:42
n3phaha, did read up on everything now - thanks for the pointer #asahi-alt · 2026-09-12 13:41
n3phAh, that's from 15h ago, so I guess this is going to land with 7.1.13-p2 / 7.1.14#asahi-alt · 2026-09-12 13:40
n3phalso: means downgrading to 2.10 will work? #asahi-alt · 2026-09-12 13:38
n3phI did see it, though, haven't touched any ebuilds yet, guess it's not upstream in the overlay yet? #asahi-alt · 2026-09-12 13:38
LarstiQn3ph: are you using https://github.com/AsahiLinux/linux/commit/710a1d44c7a5bd2958a2ca38979ffd444f9f3fa1 to match 2.11?#asahi-alt · 2026-09-12 13:36
n3phAlready went through the backlog and downgraded wpa_supplicant to 2.11 with no luck #asahi-alt · 2026-09-12 13:35
n3phHi there! I've emerged wpa-supplicant, kernel and a couple other newer ebuilds and got a broken wifi/bluetooth stack. https://bpa.st/BHGA13#asahi-alt · 2026-09-12 11:49
sofusthe actual bug can be found on line 793#asahi-alt · 2026-09-12 11:49
sofusoh yeah, i guess im pretty used to the minus1 + 1 dance#asahi-alt · 2026-09-12 11:47
JamesCalligeros[m]Where we decide the number of slices from the image height in map units minus 1 and then add 1 to it. nothing wrong with it at all its just funny#asahi-alt · 2026-09-12 11:47
LarstiQsofus: this one https://github.com/AsahiLinux/linux/pull/615/changes#diff-5d6ab4ae0168c503b027f1799463d0163f339bfce064ca8e43bb068fda432636R608#asahi-alt · 2026-09-12 11:46
sofusJamesCalligeros[m]: what?#asahi-alt · 2026-09-12 11:46
sofusflokli: i did test it, so im confident it works#asahi-alt · 2026-09-12 11:44
JamesCalligeros[m]minus1 + 1#asahi-alt · 2026-09-12 11:43
floklisofus: ty, I'll try to take a look today.#asahi-alt · 2026-09-12 11:42
sofusflokli: https://github.com/AsahiLinux/linux/pull/615#asahi-alt · 2026-09-12 11:37
mpsdoes wpa_supplicant have FILS? long time didn't used it so didn't check#asahi-alt · 2026-09-12 11:19
jannaunicolo: yes, patches for wpa_supplicant 2.11 / 2.12 are necessary until https://lore.kernel.org/linux-wireless/20260912-brcmfmac-4way-handshake-offload-authenticated-event-v1-1-e41a6a8281a2@jannau.net/T/ lands in stable kernels. it is in asahi-7.1.13-3#asahi-alt · 2026-09-12 08:10
nicolo(with the caveat of wait for stable kernel release etc)#asahi-alt · 2026-09-12 08:09
nicolocorrect?#asahi-alt · 2026-09-12 08:09
nicoloand you are saying that once a certain patch is merged into the kernel, then your patch to wpa_supplicant can dropped#asahi-alt · 2026-09-12 08:08
nicolothanks. just to make sure i understand: i talk about your patch to wpa_supplicant itself, not to the kernel.#asahi-alt · 2026-09-12 06:38
jannaunicolo: the rebased patch is necessary and there is no fixed kernel version. I would wait until the patch is in a stable kernel release as the issue doesn't just affects apple silicon devices but afaik raspberry pis as well#asahi-alt · 2026-09-12 05:54
floklisofus: I'm fine to add a few patches on top of the kernel, sure. Feel free to poke me once there is something:-)