#asahi-dev · 2026-10-25 11:16
chadmedno stress#asahi-dev · 2026-10-25 11:15
chadmeddid you manage to test WPA2/3 Enterprise?#asahi-dev · 2026-10-25 11:08
chadmedso much to do and so little time to do it in #asahi-dev · 2026-10-25 11:08
chadmedive got a blog post to write too i suppose#asahi-dev · 2026-10-25 11:07
chadmedmight as well go to 7.3#asahi-dev · 2026-10-25 11:05
chadmedi can test upstream mca with macaudio v4 tomorrow evening#asahi-dev · 2026-10-25 11:05
chadmedi think there are a couple of patches we are still carrying but we might be able to just drop them#asahi-dev · 2026-10-25 11:04
chadmedit shouldnt, no. are you testing? #asahi-dev · 2026-10-25 09:07
chadmeddockchannel has been submitted, no progress on spi #asahi-dev · 2026-10-25 06:52
chadmedid argue that case is slightly different as its not really something fundamental to the rtkit implementation and does not matter outside the battery driver. if youve got mixed endianness/key-specific stuff happening in rtc (and possibly others) too then thats a bigger problem#asahi-dev · 2026-10-25 06:51
chadmedthats true actually, it does check for the existence of specific keys#asahi-dev · 2026-10-25 06:48
chadmedbut imo you should do everything in your power to avoid implementation details in the generic drivers#asahi-dev · 2026-10-25 06:48
chadmedsince these drivers are upstream its best to get maintainer input. maybe they dont care anymore#asahi-dev · 2026-10-25 06:47
chadmedperhaps send an RFC to the mailing lists anyway#asahi-dev · 2026-10-25 06:47
chadmed"harder to get right" sure#asahi-dev · 2026-10-25 06:47
chadmedi dont think it is a "worse design" to avoid leaking implementation details into places where they do not fundamentally belong#asahi-dev · 2026-10-25 06:45
chadmedyou just said theyre all like that#asahi-dev · 2026-10-25 06:43
chadmedthe frontend should not care at all#asahi-dev · 2026-10-25 06:42
chadmedyeah so your driver should just switch/case on the keys with the wrong endianness#asahi-dev · 2026-10-25 06:42
chadmedif the latter, put quirks in your backend#asahi-dev · 2026-10-25 06:41
chadmedis that limited to just the battery keys or is the whole thing mixed endian#asahi-dev · 2026-10-25 06:40
chadmedtreat it like a subsystem i guess#asahi-dev · 2026-10-25 06:39
chadmedno, this is backwards. you should not introduce platform-specific API. what you need to do is rework the core so that it has something like struct macsmc_funcs which would just be a bunch of function pointers to the backend's implementations of e.g. read_u16#asahi-dev · 2026-10-25 06:33
chadmedyes, all of that is implementation details that belongs in your x86/acpi backend#asahi-dev · 2026-10-25 06:32
chadmedeach backend should expose callbacks for the operations that the frontend consumes#asahi-dev · 2026-10-25 06:31
chadmedi dont think the "core" (which is really the frontend) should care at all about implementation details of the backends (is_acpi)#asahi-dev · 2026-10-25 06:29
chadmedyeah#asahi-dev · 2026-10-25 06:29
chadmedand take inspiration from it#asahi-dev · 2026-10-25 06:29
chadmedgo back to old versions of the downstream driver, which had a common frontend and then platform-specific backends to talk to the actual hardware#asahi-dev · 2026-10-24 13:43
chadmedmight as well try it#asahi-dev · 2026-10-24 13:43
chadmedwhich is gonna be more cursed :P #asahi-dev · 2026-10-23 13:21
chadmedugh great the dt binding schema thingy doesnt do group regex#asahi-dev · 2026-10-23 10:08
chadmedyeah the mini only has one with downmix#asahi-dev · 2026-10-23 10:04
chadmedwhich is... not configurable on this codec#asahi-dev · 2026-10-23 10:04
chadmedmy attention turns to the bus keeper then#asahi-dev · 2026-10-23 10:04
chadmedthanks#asahi-dev · 2026-10-23 10:04
chadmedhmmm oki#asahi-dev · 2026-10-23 10:02
chadmedsame thing, the capture and playback props should have 96000 in allowed-rates#asahi-dev · 2026-10-23 10:02
chadmedcheck graph.json for the machine youre using in /usr/share/asahi-audio/#asahi-dev · 2026-10-23 10:01
chadmedaudio.allowed-rates should have 96000 in the array #asahi-dev · 2026-10-23 10:00
chadmedcheck /usr/share/wireplumber/wireplumber.conf.d/99-asahi.conf#asahi-dev · 2026-10-23 09:54
chadmedi think its an actual hardware bug or something screwy with j313 specifically if j293 and j274 work fine#asahi-dev · 2026-10-23 09:53
chadmedit panics because we get all 1s back for the voltage and current and it thinks we're pumping 60 watts through the speakers. ive pored over the datasheet for tas2770 and we're not doing anything wrong...#asahi-dev · 2026-10-23 09:52
chadmedlatest would be preferable but the part that it panics on hasnt changed in a long time #asahi-dev · 2026-10-23 09:51
chadmedanything that spins the pcm up at 96 khz will do. if speakersafetyd starts crashing with bad visense data then thats all i need#asahi-dev · 2026-10-21 10:47
chadmedUSB is also working again #asahi-dev · 2026-10-21 10:46
chadmedjannau: gpu driver looks fixed on j415 here now. still issues with dmabuf-wayland on kwin (and dwl) but i believe these are unrelated to the kernel driver #asahi-dev · 2026-10-21 10:37
chadmedcan do so now #asahi-dev · 2026-10-21 10:19
chadmedone problem at a time#asahi-dev · 2026-10-21 06:57
chadmedwell, ive been compiling to bytecode to test obvious things but havent tried to do any installs yet