#
✕ nick:JoshuaPeisach[mds]
#asahi-dev · 2026-02-18 17:11
JoshuaPeisach[mds]chadmed: chadmed: just read the progress report, very glad to see how things are progressing! I'll give fairydust a spin at some point - let me know if you have any low hanging fruit for a newbie to handle.
#asahi-dev · 2026-02-10 13:28
JoshuaPeisach[mds]actually for the rest of the cores on my 18,1Pro it is missing frequency steps above 3.04 GHz (e.g the 3.23), I’ll look into that
#asahi-dev · 2026-02-10 13:25
JoshuaPeisach[mds]they are 0 and 1, it may just be a false positive (which in this case it is because they do run at different frequencies)
#asahi-dev · 2026-02-10 13:21
JoshuaPeisach[mds]It mentioned cpu core 9, but it seemed fine - is it possible that it's talking about how the first two cores are at different frequencies than the rest?
#asahi-dev · 2026-02-10 13:20
JoshuaPeisach[mds]so I ran "fwts" which is a pretty helpful tool (looks like there is some wakealarm issues, though really in our context I'm not sure how much ACPI applies to us lol), and it mentioned that cpufreq tables were "inconsistent"
#asahi-dev · 2026-02-08 18:47
JoshuaPeisach[mds](or one that could use a check for regressions)
#asahi-dev · 2026-02-08 18:47
JoshuaPeisach[mds]ah i thought this was a patch for m1 lol
#asahi-dev · 2026-02-08 18:20
JoshuaPeisach[mds]need a m1 tester for this atcphy thing?
#asahi-dev · 2026-01-31 12:54
JoshuaPeisach[mds]Going to do a local rebuild for my J316, any branch specifically that I should use? Maybe a M3 WIP branch to test for regression?
#asahi-dev · 2026-01-27 19:00
JoshuaPeisach[mds]good! (in terms of completion but not me trying to find a way to be helpful with my device everyone has had for five years)
#asahi-dev · 2026-01-27 18:50
JoshuaPeisach[mds]anyways.. so I noticed that camera doesn't work on J316. (unless cheese is lying to me). any specific troubles i can maybe look at?
#asahi-dev · 2026-01-27 18:48
JoshuaPeisach[mds]I don't think we're trying to do like.. voltage glitching \:P
#asahi-dev · 2026-01-27 18:47
JoshuaPeisach[mds]what restrictions?
#asahi-dev · 2026-01-27 15:45
JoshuaPeisach[mds]fl0_id: i see the framebuffer0 mentioned in the dt, i don't think the other dt's have the framebuffer specifically lined out (or is the M3 different?)
#asahi-dev · 2026-01-26 17:59
JoshuaPeisach[mds]after that merge window is when an -rc1 is declared
#asahi-dev · 2026-01-26 17:58
JoshuaPeisach[mds]fl0_id: 6.19 still has to be released and then there is like, a two week merge window
#asahi-dev · 2026-01-23 20:16
JoshuaPeisach[mds]thanks
#asahi-dev · 2026-01-23 20:15
JoshuaPeisach[mds](which area of code are you guys talking about, so as a newbie I can follow along?)
#asahi-dev · 2026-01-21 14:09
JoshuaPeisach[mds]hm, my kernel of integral’s PR isnt booting for me. seems to get stuck at loading initial ramdisk. I’ll try it later. Though I don’t think a change in the power code for macsmc would trigger this…
#asahi-dev · 2026-01-21 13:42
JoshuaPeisach[mds]don't fix what's broken haha
#asahi-dev · 2026-01-21 13:40
JoshuaPeisach[mds]nevermind then! thanks for the sanity check though
#asahi-dev · 2026-01-21 13:40
JoshuaPeisach[mds]oh macsmc_battery_get_property is supposed to return any error while trying to get the property right
#asahi-dev · 2026-01-21 13:35
JoshuaPeisach[mds]technically, wouldn't this evaluate to reporting `val->intval` when `val->intval` is **less than 0**, which should only occur in the case of an error?
#asahi-dev · 2026-01-21 13:35
JoshuaPeisach[mds]`ret = val->intval < 0 ? val->intval : 0;`
#asahi-dev · 2026-01-21 13:35
JoshuaPeisach[mds]question: while trying to look at the macsmc_power spam of failing to report charge_behaviour, before I knew about the PR that should fix that, I found in `macsmc_battery_get_property`, line 406 https://github.com/AsahiLinux/linux/blob/f1879b3d78dcf69a8ff9be3b504c1bd6d5f2f47/drivers/power/supply/macsmc-power.c#L406
#asahi-dev · 2026-01-20 21:07
JoshuaPeisach[mds]chaos_princess: yeah, line 227, sorry https://github.com/AsahiLinux/linux/blob/f1879b3d78dcf69a8ff9be3b504c1bd6d5fa2f47/drivers/gpu/drm/asahi/mmu.rs#L207
#asahi-dev · 2026-01-20 20:55
JoshuaPeisach[mds]kernel newbie here, question about the TODO in the “asahi” drm driver. I see it wants DMA address/range validation, is it basically just ensure address + range > kernel VA range global?