#asahi-dev · 2026-07-27 12:26
aites[m]sofus: I think that the problem is that hid-haptic implements functions to "Configure the haptics of the trackpad passed to it" but the problem would be that if we implemented the upload effects etc into the actuator driver, then we would be passing trackpad hdevs into actuator driver code since the haptic ioctls are sent to the trackpad #asahi-dev · 2026-07-27 12:11
sofushttps://github.com/japalvia/linux-hid-magicmouse/blob/main/linux/drivers/hid/hid-magicmouse.c#L838#asahi-dev · 2026-07-27 12:11
sofusi also found this fork that enables it on the external one#asahi-dev · 2026-07-27 12:10
sofusmy suggestion was based on how hid-{multitouch,haptic}.c does it. I dont really know anything about the hid subsystem, but i assumed it would be more flexible if separated#asahi-dev · 2026-07-27 11:54
aites[m]and in the case that we want to add further support to other magicmouse devices like the USB trackpad, I think that would have the actuator registered under the same device so it would be helpful to be able to just add a branch statement within these already existing functions and reuse much of the code#asahi-dev · 2026-07-27 11:52
aites[m]I think I could do that but I'm not sure if that's the best way, since all of the force feedback callbacks under the haptics subsystem are registered under the trackpad, so all the callback functions would give you pointers to the trackpad hdev rather than the actuator's one#asahi-dev · 2026-07-27 11:41
aites[m]sofus: as in implement all of these functions within the actuator driver and then call them from the magicmouse?#asahi-dev · 2026-07-27 11:14
sofusi think the biggest missing piece for av1 support is one buffer. I think its av1 tables, its 9166 bytes long tho :(#asahi-dev · 2026-07-27 10:35
svenlooks like my smp issue is some truly weird memory corruption. this is gonna be fun to track down again :(#asahi-dev · 2026-07-27 10:21
chadmed_anyone testing dcp 14.8.3 keep in mind that not freeing stale framebuffer references _will_ cause it to stop working after some time in use#asahi-dev · 2026-07-27 09:20
yukasome tweets indeed state that t600x was moved in 26.4, while t8103 is moved in 27.0#asahi-dev · 2026-07-27 09:15
chaos_princess27?#asahi-dev · 2026-07-27 09:14
jannauI don't think so#asahi-dev · 2026-07-27 09:13
svensptm hans't hit m1 yet in any macos release, has it?#asahi-dev · 2026-07-27 09:09
jmax[m]🎉📸🎥#asahi-dev · 2026-07-27 09:03
sofusas in webcam boots and works, tested with firefox#asahi-dev · 2026-07-27 08:57
sofusadding apple,dart-vm-size = <0x0 0xa0000000>; works#asahi-dev · 2026-07-27 08:42
sofuschaos_princess: failed to read 'apple,dart-vm-size': -22#asahi-dev · 2026-07-27 08:41
sofusthat worked very well, thanks!#asahi-dev · 2026-07-27 08:31
jannauit doesn't seem to#asahi-dev · 2026-07-27 08:30
jannaucopying the other vendor firmware to a specific dir would work as well. not sure if CONFIG_EXTRA_FIRMWARE accepts wildcards#asahi-dev · 2026-07-27 08:29
sofusjannau: thanks!#asahi-dev · 2026-07-27 08:28
jannaufor avd I use https://paste.debian.net/hidden/ed40321f#asahi-dev · 2026-07-27 08:28
sofuschaos_princess: thanks CONFIG_EXTRA_FIRMWARE i will try#asahi-dev · 2026-07-27 08:28
jannauI need to update (and write a proper doc) how I deal with firmware and module loading#asahi-dev · 2026-07-27 08:28
sofusJamesCalligeros[m]: yes i did that, should be ok#asahi-dev · 2026-07-27 08:25
JamesCalligeros[m]Vendor firmware wont load without the dracut module. Your best bet is to copy it from the esp manually for tethered boot#asahi-dev · 2026-07-27 08:24
chaos_princessthere is a kconfig field that allows building firmware directly into the kernel image#asahi-dev · 2026-07-27 08:24
sofusonly trackpad firmware got loaded#asahi-dev · 2026-07-27 08:22
sofusmaybe the disk is being mounted to late or something?#asahi-dev · 2026-07-27 08:21
sofusyes okay, drivers seem to load okay now, i still have some issues the the firmware tho, it looks like the firmware is in the correct place#asahi-dev · 2026-07-27 07:55
chadmedif you build everything in you no longer use an initramfs, just make sure the firmware is where the driver expects it in the rootfs#asahi-dev · 2026-07-27 07:55
chadmedotherwise you have to make sure every single module ends up in your initramfs or you have to copy over /lib/modules/ every time #asahi-dev · 2026-07-27 07:55
sofusand should i do anything special with the initframs im also having trouble with the fw#asahi-dev · 2026-07-27 07:54
chadmedyeah its far easier#asahi-dev · 2026-07-27 07:53
sofusshould i build everything as built-in? I think im just using it wrong#asahi-dev · 2026-07-27 07:50
chadmedwhats going on#asahi-dev · 2026-07-27 07:49
sofushmmm im having some trouble with the tethered boot thing#asahi-dev · 2026-07-27 07:32
chaos_princessOk, add https://github.com/WhatAmISupposedToPutHere/linux/tree/t8122-isp to the mix then#asahi-dev · 2026-07-27 07:31
sofusisp: Heap: 0xd7c000..0x1000000 (0x284000 @ 0x108db530000)#asahi-dev · 2026-07-27 07:31
sofusisp: Data: 0x960000..0xd7c000 (0x41c000 @ 0x10001a60000)#asahi-dev · 2026-07-27 07:31
sofusisp: Code: 0x0..0x960000 (0x960000 @ 0x10000964000)#asahi-dev · 2026-07-27 07:30
sofusyes, but i lost them, 2 sec#asahi-dev · 2026-07-27 07:28
chaos_princessdid it print the "isp: Code: ..." bits?#asahi-dev · 2026-07-27 07:23
sofusisp: Version 0xf3001#asahi-dev · 2026-07-27 07:23
sofusoh wait sorry, it does boot#asahi-dev · 2026-07-27 07:21
sofusim not sure how to check#asahi-dev · 2026-07-27 07:10
chaos_princessjust check if it boots#asahi-dev · 2026-07-27 07:08
sofussorry, how do i test this?#asahi-dev · 2026-07-27 06:54
chaos_princessno, but i would appreciate someone testing https://github.com/WhatAmISupposedToPutHere/m1n1/tree/t8122-isp