#asahi-dev · 2025-03-20 20:49
chadmedjannau: should we just drop genpatches while we're churning upstream stuff then? they dont really give us any benefits tbh#asahi-dev · 2025-03-20 20:42
jannauchadmed: I'm looking at the kernel atm and there is another conflict with the toplevel Makefile#asahi-dev · 2025-03-20 20:21
jannauI'd say 90 to 95% are#asahi-dev · 2025-03-20 20:18
chaos_princessit should#asahi-dev · 2025-03-20 20:18
rrendecnice! would it be safe to assume that any kernel submission related to the project would cc that list?#asahi-dev · 2025-03-20 20:17
j`eyyou can also check https://lore.kernel.org/asahi/#asahi-dev · 2025-03-20 20:16
rrendecasking here works for me :)#asahi-dev · 2025-03-20 20:15
jannaurrendec: I can only think of asking here or checking if someone send something in the last months#asahi-dev · 2025-03-20 20:14
chaos_princessidk, can be split out i guess#asahi-dev · 2025-03-20 20:13
jannaudo you think it's necessary/advisable to send with isp? could easily just point to v1 isp submission as justification#asahi-dev · 2025-03-20 20:10
chaos_princessforce-disable/force-reset from 010-soc will be sent with isp, which is now blocked on dart changes#asahi-dev · 2025-03-20 20:09
jannauin 030-misc the kvm/perf changes are handled. pasemi i2c were sent recently, PM domains changes might require a prior discussion. UHS-2 changes need more debugging#asahi-dev · 2025-03-20 20:08
rrendecjannau: I see only two pmgr changes in 010-soc (or 3 with the dt bindings), so that looks like a low hanging fruit#asahi-dev · 2025-03-20 20:07
rrendecyeah, that was the other question: how do I know what's already being worked on, so I can avoid effort duplication?#asahi-dev · 2025-03-20 20:05
jannaufrom 010-soc I think only the pmgr changes are upstreamable. the rtkit ones are mostly all queued for upstream#asahi-dev · 2025-03-20 20:04
rrendecthen maybe I can start with 030-misc?#asahi-dev · 2025-03-20 20:04
chaos_princessthats like what, 4 port imac, and non-ultra mac studio?#asahi-dev · 2025-03-20 20:04
chaos_princessxhci-firmware has annoying hw requirements#asahi-dev · 2025-03-20 20:03
jannau060-spi should be already upstream#asahi-dev · 2025-03-20 20:02
jannaurrendec: best bet would be bits from bits/030-misc or bits/080-wifi, bits/090-spi-hid (needs work), bits/150-xhci-firmware#asahi-dev · 2025-03-20 20:01
rrendec010-soc, 030-misc, 060-spi, 130-cpufreq look interesting, and some of those patches are in areas where I worked before#asahi-dev · 2025-03-20 19:50
rrendecchaos_princess: thanks, that's a really good tip! will look at those branches#asahi-dev · 2025-03-20 19:50
rrendecI noticed there are a lot of changes related to Rust and DRM, and those are two areas that I'm really not familiar with, so I would stay away from those#asahi-dev · 2025-03-20 19:49
chaos_princessreally: if you look at the repo, you will see multiple branches that are called bits/000-something, see if something appeals to you#asahi-dev · 2025-03-20 19:49
chaos_princesshides#asahi-dev · 2025-03-20 19:49
chaos_princesswifi #asahi-dev · 2025-03-20 19:49
rrendecI am familiar with the kernel process and I have contributed before but I'm not actively doing upstream development in any specific area#asahi-dev · 2025-03-20 19:48
rrendecI was hoping to be able to get a quick overview here#asahi-dev · 2025-03-20 19:48
rrendecI haven't looked very closely at your changes because 1200 commits is a lot :)#asahi-dev · 2025-03-20 19:45
jannaudo you have specific knowledge or interests related to our changes? are you familia with the kernel process?#asahi-dev · 2025-03-20 19:44
jannaurrendec: hej#asahi-dev · 2025-03-20 18:08
rrendecwhat would be a good place to start? I already looked at the "asahi" branch on https://github.com/AsahiLinux/linux/tree/asahi and there's a lot in there#asahi-dev · 2025-03-20 18:08
rrendechi all, I'm new to Asahi Linux and around here but I'd like to help with upstreaming some of the Linux kernel bits#asahi-dev · 2025-03-20 14:14
fl0_id(if it matters somewhere)#asahi-dev · 2025-03-20 14:14
fl0_idwell yes but I meant f.e. m1n1 in this case#asahi-dev · 2025-03-20 14:12
kettenisopen source OSes (and applications) already have to deal with the frequency varying from machine to machine#asahi-dev · 2025-03-20 14:10
fl0_idkettenis it prob matters if you want to offer both, as it adds complexity I would guess#asahi-dev · 2025-03-20 13:54
kettenisbut might as well pick 1 GHz since ARM has declared that's the future#asahi-dev · 2025-03-20 13:54
kettenisI don't think it really matters as long as we configure things consistent across cores#asahi-dev · 2025-03-20 13:52
chaos_princessi think we would always want to run with 1ghz#asahi-dev · 2025-03-20 13:51
fl0_idj`ey ok, good to know. I just understood it as "don't use this directly, but use our lib / api which abstracts this"#asahi-dev · 2025-03-20 13:51
j`ey(on macOS)#asahi-dev · 2025-03-20 13:50
j`eyfl0_id: it can return 24Mhz if an app was built against the older SDK#asahi-dev · 2025-03-20 13:48
fl0_idkettenis ok but is it configurable? The change log makes it sound like with 15.x firmware, it always returns 1 Ghz on M3 or newer#asahi-dev · 2025-03-20 13:36
kettenismore like fixed at 24 MHz if < M3, configurable between 24 MHz and 1 GHz when >= M3#asahi-dev · 2025-03-20 13:35
fl0_idi.e if < m3 = 24 Mhz, else 1 Ghz (or sth like that)#asahi-dev · 2025-03-20 13:34
fl0_idmmh, regarding the 24 Mhz / 1 Ghz switch on M3+ - it seems CNTFRQ_EL0 is accessed in hv.c, hv_wdt.c, and utils.c (and gpiola.py and some experiments) I assume code will have to check for which chip/frequency is used everywhere, or probably preferably, introduce a separate function that does that?#asahi-dev · 2025-03-20 12:51
kettenisbest if that happens first before I try to upstream the u-boot bits#asahi-dev · 2025-03-20 12:50
ketteniskernel#asahi-dev · 2025-03-20 12:50
chaos_princessu-boot or kernel?