2023-04-27
00:01cylm has joined #asahi-dev
00:02cylm_ has quit [Ping timeout: 480 seconds]
00:36nsklaus has quit [Quit: WeeChat 3.8]
00:37nsklaus has joined #asahi-dev
01:04vivithecanine has quit [Quit: WeeChat 3.8]
01:06nsklaus has quit [Ping timeout: 480 seconds]
01:56stipa is now known as Guest12289
01:56stipa has joined #asahi-dev
02:00gabuscus has quit []
02:02Guest12289 has quit [Ping timeout: 480 seconds]
02:13gabuscus has joined #asahi-dev
02:38nyx_o has joined #asahi-dev
03:36abd has joined #asahi-dev
04:23eiln has joined #asahi-dev
04:42elvishjerricco has quit [Read error: Connection reset by peer]
04:43elvishjerricco has joined #asahi-dev
04:44marcanI think that means we can probably cook a release soon, after wifi/bt is fixed for t602x machines and the u-boot oslog thing
05:02drubrkletern has joined #asahi-dev
05:04elvishjerricco has quit [Read error: Connection reset by peer]
05:06elvishjerricco has joined #asahi-dev
05:12elvishjerricco has quit [Read error: No route to host]
05:13elvishjerricco has joined #asahi-dev
05:19kaazoo has quit [Quit: Leaving.]
05:31jannauI was asking myself that as well. the core watchdog device has suspend/resume callbacks to stop/start its thread and ping the watchdog on suspend
05:34jannautrying to think if it's possible if specific watchdog drivers could do something better than stopping the watchdog on suspend but I can't think of anything which would work for s2idle
05:35jannaueiln: do you need information from the m1 ultra? I wanted to look into that when you asked but forgot
05:45eilnjannau: yes please! do you mind tracing trace_device(node, mode=TraceMode.SYNC) for ane0, ane1, ane2, ane3
06:25compassion has quit [Ping timeout: 480 seconds]
06:30elvishjerricco has quit [Read error: Connection reset by peer]
06:33elvishjerricco has joined #asahi-dev
06:35drubrkletern has quit [Remote host closed the connection]
06:39compassion has joined #asahi-dev
06:40bps has joined #asahi-dev
06:40elvishjerricco has quit [Read error: No route to host]
06:45elvishjerricco has joined #asahi-dev
06:52elvishjerricco has quit [Read error: Connection reset by peer]
06:54elvishjerricco has joined #asahi-dev
07:05elvishjerricco has quit [Read error: No route to host]
07:13bps has quit [Ping timeout: 480 seconds]
07:13hightower2 has quit [Ping timeout: 480 seconds]
07:22elvishjerricco has joined #asahi-dev
07:30elvishjerricco has quit [Read error: No route to host]
07:33cylm has quit [Ping timeout: 480 seconds]
07:48elvishjerricco has joined #asahi-dev
07:55elvishjerricco has quit [Remote host closed the connection]
07:56elvishjerricco has joined #asahi-dev
08:04elvishjerricco has quit [Read error: No route to host]
08:05elvishjerricco has joined #asahi-dev
08:10elvishjerricco has quit [Remote host closed the connection]
08:10elvishjerricco has joined #asahi-dev
08:11bps has joined #asahi-dev
08:19marcanarnd: so for the next window I plan to merge https://lore.kernel.org/asahi/20230328-soc-mailbox-v1-0-3953814532fd@marcan.st/T/ but I haven't gotten a proper ack from Jassi yet
08:19elvishjerricco has quit [Ping timeout: 480 seconds]
08:19marcanI can just merge the new addition and leave the old driver to rot for now, the only downside of that is it forces a config symbol change which means churn for packagers
08:20marcanJassi did say he's "ok" with it, just seems reluctant to give a formal ack for some reason...
08:29elvishjerricco has joined #asahi-dev
08:35elvishjerricco has quit [Read error: Connection reset by peer]
08:38elvishjerricco has joined #asahi-dev
08:41elvishjerricco has quit [Read error: Connection reset by peer]
08:42chadmedalyssa: dunno if you peep logs during your absences but you sniped me real good the other day -> https://github.com/chadmed/asahi-audio/tree/desktops/mini
08:42benpoulson has joined #asahi-dev
08:42chadmedits not fantastic magic like the laptops but it makes the speaker tolerable to use and thats good enough for now
08:44elvishjerricco has joined #asahi-dev
08:53elvishjerricco has quit [Read error: Connection reset by peer]
08:54elvishjerricco has joined #asahi-dev
08:56hightower2 has joined #asahi-dev
08:57elvishjerricco has quit [Read error: No route to host]
08:59elvishjerricco has joined #asahi-dev
09:00abd has quit [Remote host closed the connection]
09:03elvishjerricco has quit [Read error: Connection reset by peer]
09:09kettenis has joined #asahi-dev
09:18elvishjerricco has joined #asahi-dev
09:25elvishjerricco has quit [Read error: Connection reset by peer]
09:25elvishjerricco has joined #asahi-dev
09:28arndmarcan: I'm at Linaro Connect right now, I think jassi is here as well, will ask him about it if I see him
09:33elvishjerricco has quit [Read error: Connection reset by peer]
09:34elvishjerricco has joined #asahi-dev
09:48elvishjerricco has quit [Read error: Connection reset by peer]
09:48elvishjerricco has joined #asahi-dev
09:49kaazoo has joined #asahi-dev
09:52bpye has quit [Quit: Ping timeout (120 seconds)]
09:53bpye has joined #asahi-dev
09:53elvishjerricco has quit [Read error: No route to host]
09:55ketteniscan someone explain me the rules about upstreaming other people's diffs in this strange world of magic git commit message tags?
09:56korreckj328 has joined #asahi-dev
09:58elvishjerricco has joined #asahi-dev
09:59kettenisI think I should try to upstream at least marcan's rtkit diffs, but I read conflicting things about what tags should be added
10:00nsklaus has joined #asahi-dev
10:04elvishjerricco has quit [Read error: Connection reset by peer]
10:04elvishjerricco has joined #asahi-dev
10:08kaazoohttps://github.com/AsahiLinux/u-boot/pull/11/commits/ea9459d3eb65da9c4c646e3f7631555808ea087b
10:08marcanthe git send email or whatever should keep a From: body-header in that makes git keep the original author name
10:11marcankettenis: feel free to merge it straight to asahi, I'll rebase the releng stuff next time I tag a release
10:12kettenisI was planning to merge the M2 Pro/Max stuff and the asmedia firmware loading stuff into the asahi branch soon
10:12marcanthe sram thing is worrying, maybe oslog doesn't re-request its buffer and confuses us with a similar message?
10:14marcaneither way if this needs u-boot fixes that would be on top of what you did so far so no reason to block it
10:15kaazooI might have done it wrong, but u-boot is stil complaining about unknown oslog messages. Will post screenshot in a sec.
10:15marcanthe way macos does it, oslog goes into a dedicated memory area, and if we're stuck with that I'm tempted to move this all to m1n1 and fix it for good there, but that doens't mean u-boot shouldn't know how to do this anyway.
10:16_jannau_kettenis: any updatess on your asahi,efi-system-partition support patch? I'd be happy if we could get rid of the patched distro_bootcmd
10:17elvishjerricco has quit [Read error: Connection reset by peer]
10:20ketteniskaazoo, marcan: that commit message probably needs a bit of tweaking to be acceptable upstream
10:22kaazoomarcan: if we don't care about those messages, then I can also remove that print statement in u-boot
10:24marcansorry, this probably should go in m1n1 then, but yeah, you can remove the print statement
10:26marcanI wonder if there is some codepath to clear this out, I should probably throw the firmware into ghidra and check before I spend time moving this to m1n1
10:29elvishjerricco has joined #asahi-dev
10:34marcanok, I think we're going to do that, which does in fact mean more special-casing for u-boot needed
10:36marcankaazoo: your patch is correct as far as handling that in general, but we're going to need an extra special case based on a device tree property here
10:36marcanlet me play around with ghidra just to make sure there isn't an easier way, if not we'll go the SRAM route
10:37kaazookettenis: I updated the commit message: https://github.com/AsahiLinux/u-boot/pull/11/commits/42bb4082b51725f1cb74a4864e009dc13b9301d3
10:42kaazooDid anybody look into wifi support on j414 with 13.3 FW yet? How is wifi stuff connected? PCIe? lspci shows nothing
10:48kettenisdriver needs some changes; on openbsd I end up in the equivalent of brcmf_chip_sysmem_ramsize() but the code in that function is wrong
10:49marcanoh wow the MTP firmware literally has an OS_LOG segment that does *not* get put into SRAM but rather contains all the strings for the oslog entries, which themselves just have pointers to them
10:50kaazookernel log says: nvme-apple 34bcc0000.nvme: RTKit: syslog message: apcie.c:428: APCIe 1 is configured as unused.
10:50kettenisthe android bcm4389 driver has different code there handling two different cases and none if that matches what the asahi linux brcmfmac driver does
10:52elvishjerricco has quit [Read error: No route to host]
10:57elvishjerricco has joined #asahi-dev
11:03elvishjerricco has quit [Read error: Connection reset by peer]
11:08elvishjerricco has joined #asahi-dev
11:09cylm has joined #asahi-dev
11:15elvishjerricco has quit [Read error: Connection reset by peer]
11:34povikyeah, i ran the full-os install under hypervisor, skipping over u-boot, and still saw them
11:34povikbefore that i tried patching the in-kernel pwrstate to never turn off domains, did a bunch of reboots, and saw them too
11:35povikbut that was with u-boot, so i am making sure it's safe to conclude power domains (even being transitionally turned off) are not to be blamed
11:38elvishjerricco has joined #asahi-dev
11:44elvishjerricco has quit [Read error: No route to host]
11:44benpoulson has quit [Remote host closed the connection]
11:45benpoulson has joined #asahi-dev
11:45elvishjerricco has joined #asahi-dev
11:50elvishjerricco has quit [Read error: Connection reset by peer]
11:56nsklaus has quit [Quit: WeeChat 3.8]
11:57nsklaus has joined #asahi-dev
12:00kaazoo has quit [Quit: Leaving.]
12:03_jannau_kaazoo: missing CONFIG_PCIE_APPLE, are you building a kernel with 4k page size (ARM64_PAGE_SHIFT == 12)?
12:03kaazoo has joined #asahi-dev
12:03_jannau_kaazoo: missing CONFIG_PCIE_APPLE, are you building a kernel with 4k page size (ARM64_PAGE_SHIFT == 12)?
12:05hightower2 has quit [Ping timeout: 480 seconds]
12:07kaazoo has quit [Read error: Connection reset by peer]
12:18kaazoo has joined #asahi-dev
12:22kaazooThere is a sleep button (moon icon) on my now functional keyboard. Seems like the machine went to sleep when I pressed it while trying out all buttons, but the display driver (llvmpipe) didn't come back and the screen stayed dark. Caps-lock worked, so I guess the machine came back from sleep/idle/whatever.
12:23chadmedi wasnt going to bother doing the desktops at all but you were right they are really _really_ bad
12:26kaazooI'm using tobhe's repo (https://github.com/tobhe/ubuntu-asahi) and installed Ubuntu 23.04 . The kernel build script included that 4K patch: https://github.com/tobhe/ubuntu-asahi/blob/lunar/scripts/asahi/01-build-asahi-kernel.sh#L22
12:26_jannau_kaazoo: if it is sleep only the power button wakes it up, watchdog should reset the system after 30 if booted through u-boot
12:30marcanthis whole setup you are basing on seems to be quite ancient, which does not bode well for getting stuff right (e.g. the new firmware stuff)
12:32marcanomg why is it using "eatmydata" is this from before we added the flush defer stuff to NVMe? ffs that was fixed *ages* ago
12:34marcanseriously, you might be better off starting from scratch if the base you have is such a mess of random patches and bad branches and ancient workarounds that haven't been relevant for a year+
12:40tobhekaazoo: you can get a more up-to-date source for the ubuntu kernel,m1n1 and u-boot via apt source or from https://launchpad.net/~tobhe/+archive/ubuntu/asahi
12:40alyssaI guess the provided .wavs are filters and all the audio is convolved with those filters?
12:41alyssaand the filters are provided as audio file (.wav) because filters are data and data are filters?
12:41_jannau_t6020 is a slightly wrong u-boot branch but it shouldn't matter as long you use it with asahi-wip and have only a single other OS install. there is no correct branch yet with t602x support
12:42povikalyssa: it's a waveform and has a sample rate and format exactly like any audio signal would have
12:43chadmedalyssa: yup all the filters are represented as an impulse response over the input signal on that virtual sink, with the convolved output sent to the hardware
12:45povikcould the SIO be getting some unexpected IRQs due to bad interaction with one of our drivers?
12:49povikhttps://github.com/AsahiLinux/m1n1/blob/254a2acf189691b2081dc13603665e10a4e3ac0a/proxyclient/m1n1/hw/asc.py
12:49cylm_ has joined #asahi-dev
12:50nyilas has joined #asahi-dev
12:51kaazootobhe: the current packages for m1n1, u-boot and kernel in https://launchpad.net/~tobhe/+archive/ubuntu/asahi?field.series_filter=lunar won't support M2 Pro. That's why I've built the stuff locally. Also allowed me to understand the whole installation and boot procedure a bit better.
12:51cylm has quit [Ping timeout: 480 seconds]
12:51svenso probably these speakers don’t have a very flat frequency response and those filter presumably try to fix that
12:53marcankaazoo: fwiw the best way to understand the boot process etc is https://github.com/AsahiLinux/docs/wiki/Open-OS-Ecosystem-on-Apple-Silicon-Macs
12:57chadmedkettenis: yeah but having a big ol component system with big ol floorstanders is just so nice
12:58svenah, I just have some parametric filters I found somewhere for my headphones and adjusted them a bit
12:58chadmedi think the last time i eqed a set of headphones was when i had some shockingly bad corsair gaming thing that was nothing but mids
13:00svenI have a hd600 which is pretty good except for the weak bass. much more enjoyable after bumping that up a bit
13:01TheLinksven: I regretted that I didn't get the hd600 again after mine died -- the hd663 has much worse bass
13:01chadmedwhen i was still working front of house i had a pair of 280s i took everywhere, they were seriously good for the price
13:16axboejannau: overnight and moving to office suspend, all good on resume. not unexpected as it clearly was the watchdog, but just noting it regardless
13:17korreckj328 has quit [Ping timeout: 480 seconds]
13:22hightower2 has joined #asahi-dev
13:28_jannau_axboe: thanks, good to know. the watchdog issue would have hiddenany long running suspend issue
13:34zjstraus has quit [Ping timeout: 480 seconds]
13:41poviknever mind i switched what INBOX and OUTBOX means, so i don't seem to have gotten the reply
14:03zjstraus has joined #asahi-dev
14:10kettenis has quit [Remote host closed the connection]
14:14kettenis has joined #asahi-dev
14:26kaazoo has left #asahi-dev [#asahi-dev]
14:45nyilas has quit [Remote host closed the connection]
15:07marcanpovik: IIRC I did see similar behavior for IRQ_NOT_PEND when testing something like mailbox messages, the FIQ one was a guess
15:13bcrumb has joined #asahi-dev
15:20bcrumb has quit [Quit: WeeChat 3.8]
15:26pharonix71 has joined #asahi-dev
15:30kaazoo has joined #asahi-dev
15:34kaazooAfter hopefully correctly switching to 16K page size and enabling PCIe driver, lspci shows these Broadcom devices:
15:35kaazooIs brcmfmac the right driver? I wasn't loaded automatically and also doesn't detect anything when loading it manually.
15:35kaazooCould it be that we need to add the product ID of the wifi nic to the driver's list of supported devices?
15:37jannaubrcmfmac is the correct driver, adding the product id will not be enough, see waht was said earlier today on the topic
15:39bps has quit [Ping timeout: 480 seconds]
15:44kaazoo has left #asahi-dev [#asahi-dev]
15:50axboe has quit [Remote host closed the connection]
15:51Tomdownsouth has joined #asahi-dev
15:52marcankaazoo: The new chips are not supported yet, there is a known set of things we need to implement for every new chip
15:53axboe has joined #asahi-dev
15:53marcanIDs, SRAM offset, OTP offset, plus (hopefully zero but possibly not) firmware API changes
16:39lynndotpy has quit [Quit: bye bye]
16:41lynndotpy has joined #asahi-dev
16:55alyssa has left #asahi-dev [#asahi-dev]
16:59pthariensflame has joined #asahi-dev
16:59Tomdownsouth has quit [Ping timeout: 480 seconds]
17:28brolin has joined #asahi-dev
17:30brolin has quit []
17:31brolin has joined #asahi-dev
17:34brolin has quit []
17:35eiln has quit [Quit: WeeChat 3.8]
17:41brolin has joined #asahi-dev
17:51drubrkletern has joined #asahi-dev
17:57pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
18:03brolin has quit [Quit: leaving]
18:04brolin has joined #asahi-dev
18:17cylm_ has quit [Ping timeout: 480 seconds]
18:27Guest12262 has quit [Ping timeout: 480 seconds]
18:28rhysmdnz has quit [Ping timeout: 480 seconds]
18:28gladiac has joined #asahi-dev
18:28brolin has quit [Ping timeout: 480 seconds]
19:02maximbaz has quit [Quit: Ping timeout (120 seconds)]
19:02maximbaz has joined #asahi-dev
19:08jannaudcpext works now reliably on every second try. there has to be something which is not reset properly
19:15gladiac has quit [Quit: k thx bye]
20:26bps has joined #asahi-dev
20:29benpoulson has quit [Remote host closed the connection]
20:56Jamie has joined #asahi-dev
20:56rhysmdnz has joined #asahi-dev
20:56Jamie is now known as Guest12357
21:08eiln has joined #asahi-dev
21:24rhysmdnz has quit [Quit: Reconnecting]
21:24rhysmdnz has joined #asahi-dev
21:49bps has quit [Ping timeout: 480 seconds]
21:59alyssa has joined #asahi-dev
22:00alyssamarcan: Maybe coincidental lack of luck, but I think USB regressed between gpu/rust-wip UAPI version 7 and 8
22:02alyssaAfter bumping my kernel, they didn't work. Got to my TTY and nothing from the keyboard. The LED on my mouse lit up (so I know it was getting power) but not properly animated (so it wasn't working properly)
22:03alyssaEventually some amount of plugging and unplugging and waiting and they both showed up and worked
22:03alyssaI'm not sure what gpu/rust-wip is on top of, I would be unsurprised if this is some random USB regression in linux-next unrelated to anything we do
22:10alyssatype-c appears to also be affected but IDK if that's a recent regression, I don't use type-C regularly on the mini
22:11alyssaI am really hoping this is a known issue and I can revert some linux-next patch because woof
22:11alyssaundecided whether I will revert my kernel and use uapi v7 until fixed or just suck it up and deal with it
22:12alyssaI don't want to block Lina over this, at the same time I really do kinda need my keyboard to work Lol
22:18alyssaIn the new kernel, it tries to probe my keyboard 30+ times before it finally goes through
22:18alyssa[ 12.198004] usb 3-1: New USB device found, idVendor=05ac, idProduct=1006, bcdDevice=96.15
22:19alyssafinally after device number 63, it detects the keyboard plugged into the hub and probes into the input subsystem and
22:22alyssaThe working kernel was on ec153d79a5da ("drm/asahi: Identify more Render fields & update to UAPI 10007")
22:28alyssaI think I'm going to merge Lina's change, but if you could look at this maybe Monday, I would appreciate
22:32alyssa(I.e. is this "Alyssa's setup is weird and hit some weird issue becasue of it" or is it "absolutely real regression that Alyssa hit before everyone else did")
22:32alyssa(For the former, I think I might be building my kernel with clang because I don't know how Rust for Linux works. Or maybe it's gcc. Unsure ^_^)
22:34WindowPain has quit [Read error: Connection reset by peer]
22:34WindowPain has joined #asahi-dev
22:39dax has joined #asahi-dev
22:45brolin has joined #asahi-dev
22:51kettenis has quit [Ping timeout: 480 seconds]
23:00brolin has quit [Ping timeout: 480 seconds]
23:02kettenis has joined #asahi-dev
23:05_rudi1 has joined #asahi-dev
23:11_rudi has quit [Ping timeout: 480 seconds]
23:21piroko has quit [Ping timeout: 480 seconds]
23:21jannauI haven't noticed any USB-A issues on the mac mini with a directly connected lenovo compact keyboard with 6.3-rc4 or 6.3 based kernels but I wouldn't have necessarily spotted issues which occur occasionally
23:27kettenis has quit [Ping timeout: 480 seconds]
23:34brolin has joined #asahi-dev
23:40nsklaus has quit [Quit: Zzz]
23:40eiln has quit [Read error: Connection reset by peer]
23:59dax has left #asahi-dev [#asahi-dev]