#asahi-dev · 2025-08-18 18:26
jannaushould we drop /var/log/Xorg.0.log from asahi-diagnose?#asahi-dev · 2025-08-16 14:26
jannauargh, why did the fastmail remove the line breaks#asahi-dev · 2025-08-16 14:25
jannau`b4 trailers` doesn't find anything after changing commit msg subject#asahi-dev · 2025-08-16 13:51
jannauit's ok to handle that as a future problem (if it ever is)#asahi-dev · 2025-08-16 13:50
jannauthe only thing a can think of is the lid angle in hid#asahi-dev · 2025-08-16 13:49
jannauI was only saying that they bring their own float handling and do not use a common helper#asahi-dev · 2025-08-16 13:47
jannauhid iio sensors match too, amdgpu and bcachefs#asahi-dev · 2025-08-16 13:45
jannaugrepping for exponent reveals a few drivers with custom float handling, best match is probably drivers/hwmon/pmbus/pmbus_core.c#asahi-dev · 2025-08-16 10:31
jannauI've pushed `asahi-6.16.1-1` to github, rebase, a few kernel-robot fixes squashed in and imported the btrfs log replay fix (not in v6.16.1)#asahi-dev · 2025-08-16 07:17
jannauthe non-desktop property might break things as well but weston at least starts after deinstalling tiny-dfr (which needs convinincing on FAR since it's a dependency of the meta package)#asahi-dev · 2025-08-16 07:14
jannaulooks like the seat-touchbar trickery in tiny-dfr breaks using the touchbar display with compositors: https://www.reddit.com/r/AsahiLinux/comments/1mrjybj/touchbar_as_drm_device_backend_for_wayland/#asahi-dev · 2025-08-15 11:32
jannauhow much additional effort would be to fix C completely first? it would be a little cleaner because it avoids supporting buggy behavior in rust/ffi#asahi-dev · 2025-08-14 19:42
jannauodds are that has already happened#asahi-dev · 2025-08-14 19:41
jannau> The findings reveal the internal identifier t8152, which matches the “M4 Ultra” scheme and also goes by the codename “Hidra.”#asahi-dev · 2025-08-14 19:40
jannauone of the "journalists" claimaing that#asahi-dev · 2025-08-14 19:33
jannauwhere can I bet on mac rumors? "t8152" is not going to be m4 ultra#asahi-dev · 2025-08-14 10:11
jannaudrat!#asahi-dev · 2025-08-14 08:43
jannaudrat 4 level page table support sent#asahi-dev · 2025-08-13 08:58
jannaushould "pci[0-9a-f]{4}," added as NOT vendor property to the list at the begiining of vendor-prefixes.yaml (which explicitly says it should not be extended) or shall I add pci14e4 as broadcom vendor prefix?#asahi-dev · 2025-08-13 08:56
jannaurobher: checkpatch complains about "WARNING: DT compatible string vendor "pci14e4" appears un-documented". using "pci${vendor_code},${device_code}" as compatible is not uncommon#asahi-dev · 2025-08-13 08:38
jannausigh, brcmfmac BCM4388 suport is not upstream, I guess I need to strip that from the t6020 submission#asahi-dev · 2025-08-12 18:30
jannaumaz: I think the fw loader was never in upstream u-boot#asahi-dev · 2025-08-12 17:03
jannauu-boot doesn't care as it has no ethernet driver. could be an issue for the asm hcdon m2 pro mac mini though. I was more concerned about *bsd#asahi-dev · 2025-08-12 10:27
jannauI think only t8103-j457 is affected in mainline. I'm currently preparing the t602x device trees fior upstream#asahi-dev · 2025-08-12 10:25
jannauI think that probably just doesn't have the port disabled#asahi-dev · 2025-08-12 10:22
jannauyes, iommu-map-ping assigns an disabled dart#asahi-dev · 2025-08-12 10:21
jannauthat results unexpected PCI bus numbers. the device tree expects a gap but Linux' PCI subsystem assigns continuous bus numbers#asahi-dev · 2025-08-12 10:19
jannauI'm looking at devices with unused pcie ports (M1 imac with 2 USB-C ports, M2 Pro Mac mini). both have an unused port in the middle#asahi-dev · 2025-08-12 10:17
jannauis "bus-range" in PCI bridge device tree nodes descriptive or normative?#asahi-dev · 2025-08-11 12:12
jannauthe joys of running make dtbs_check on the t602x device trees#asahi-dev · 2025-08-11 09:06
jannauget_reg needs to walk the tree to do "ranges" based address translation#asahi-dev · 2025-08-08 17:48
jannauI've merged #477, please rebase any PR with failing packit jobs#asahi-dev · 2025-08-08 08:28
jannauisn't CPU measurement completely broken. 7.7 / 8.4 W while the battery depletes less than 3W#asahi-dev · 2025-08-08 07:28
jannauchaos_princess: did you check after `echo 1 > /sys/module/macsmc_power/parameters/log_power` where the energy use is reduced?#asahi-dev · 2025-08-04 13:53
jannauto understanding at most unprocessed parts in the log/journal after the reboot#asahi-dev · 2025-08-04 13:41
jannauthere's unfortunately no power fail signal so the capacitance is wasted. sudden system reset / hang should trigger it as well#asahi-dev · 2025-08-04 13:32
jannauto my understanding the bug doesn't eat (much) data and needs a power fail at the "right" time to trigger#asahi-dev · 2025-08-04 08:30
jannauI doubt we can cover all GPU core variants ourself but I'm unsure if we need to#asahi-dev · 2025-08-04 08:20
jannauI'm undecided if the verification is something we should ship to users#asahi-dev · 2025-08-04 08:18
jannauno pressing need. I still need to verify that the m1n1 init is identical to the existing driver one#asahi-dev · 2025-08-04 08:06
jannaudiff is a little noisy since I did cleanup/refactoring in some branches. I think my conflict resolution for wifi is less likely to cause problems for other brcmfmac chipsets#asahi-dev · 2025-08-04 08:02
jannauchaos_princess: there was some delta between your 6.16 bits branches and mine. It looked like you undid some of aop probe changes. was that intentional? please check#asahi-dev · 2025-08-03 18:43
jannauI think it's a bad idea because it'll end in madness because you end up with implementing thin in 5 to 10 bootloaders then#asahi-dev · 2025-08-03 18:42
jannausven: u-boot / grub have code to select the matching dt based on the kernel version#asahi-dev · 2025-08-03 16:34
jannautons of stuff. `git log -- 'src/kboot*'`#asahi-dev · 2025-08-03 16:33
jannauso now you have two things you have to update if something changes#asahi-dev · 2025-08-03 16:33
jannauu-boot would need to copy all the dynamic information m1n1 fills in kboot to the dtb#asahi-dev · 2025-08-03 15:49
jannauwe're building with "-march=armv8.2-a". did you change that already? not sure what could blow but LSE atomics certainly would#asahi-dev · 2025-08-03 15:41
jannaunickchan: are we using LSE atomics?#asahi-dev · 2025-08-03 15:41
jannauso you're not going to fix PCI hotplug? it looks like nvidia might be struggling with usb4 / thunderbolt for dgx spark as well. it's delayed. nvidia lists just usb-c in their spec and the partner devices list usb3.2