#
✕ nick:hex86[m]
#asahi-dev · 2026-11-13 12:32
hex86[m]🥹
#asahi-dev · 2026-11-13 12:31
hex86[m]Hooray!
#asahi-dev · 2026-11-13 12:09
hex86[m]chadmed: Okay thanks for letting me know, how is it now?
#asahi-dev · 2026-11-13 11:24
hex86[m]By the way, what's the status now on the haptic touchpad MR https://github.com/AsahiLinux/linux/pull/573 ? Sofus is happy with it as it is, and not much has happened so far, what should be done at this point?
#asahi-dev · 2026-10-31 15:25
hex86[m]👍️
#asahi-dev · 2026-10-31 15:23
hex86[m]Oh true, if this can be tested by anyone with a spi touchpad that would also be god
#asahi-dev · 2026-10-31 15:23
hex86[m]sofus: hahahahahaha finally!! you are freed
#asahi-dev · 2026-10-31 15:21
hex86[m]if there's no problems then I'll send a MR for it
#asahi-dev · 2026-10-31 15:20
hex86[m]can anyone else on this matrix / irc also test out this patch for me?
#asahi-dev · 2026-10-31 15:20
hex86[m]https://github.com/hex-64/linux/tree/palm-rejection
#asahi-dev · 2026-10-31 15:20
hex86[m]:D
#asahi-dev · 2026-10-31 15:18
hex86[m]Yeah I don't really like DWT that much because I like to use my trackpad immediately after typing, so the poor palm rejection on asahi affects me more than people who enable DWT, and the palm rejection seems to be a lot better with the patch
#asahi-dev · 2026-10-31 15:16
hex86[m]sofus: you destroyed the libinput quirks?? 😭
#asahi-dev · 2026-10-26 13:42
hex86[m]How far are we from upstreaming the magicmouse stuff? I'd like to gain some experience in upstreaming existing patches and try my hand at it myself
#asahi-dev · 2026-10-25 21:28
hex86[m]Haha hopefully we can get this merged at some point, I've left it sitting around for maybe a little too long!
#asahi-dev · 2026-10-25 21:28
hex86[m]ok sofus I should have responded to everything from your review now! :D
#asahi-dev · 2026-10-25 17:14
hex86[m]*magicmouse instead of putting it into the actuator
#asahi-dev · 2026-10-25 17:13
hex86[m]Do you mean putting it into the probe of the magicmouse or actuator?
#asahi-dev · 2026-10-25 17:13
hex86[m]By the way, could you clarify what is meant by https://github.com/AsahiLinux/linux/pull/573#discussion_r4371104043 ?
#asahi-dev · 2026-10-25 17:13
hex86[m]sofus: Yeah I think so, and even the magicmouse.c file itself is really different from upstream, I have no idea how to even start with handling all of that.. 🫪
#asahi-dev · 2026-10-25 16:27
hex86[m]and the magicmouse / apple hid drivers get a patch every so often anyways, as they're used for non-macbook devices too, and so finally getting these upstreamed would probably help reduce asahi maintainence burden too :D
#asahi-dev · 2026-10-25 16:26
hex86[m]I'd really like to take on the work of getting the pre-requisite patches upstreamed, I've submitted to the kernel before but I've never tried upstreaming patches from kernel forks, and I'd like to get experience on that, but I might need some advice because I've never tried
#asahi-dev · 2026-10-25 16:25
hex86[m]So I don't even know how I'd get started on getting these upstreamed 😅
#asahi-dev · 2026-10-25 16:24
hex86[m]But I think a lot of the pre-requisite patches that lead up to it haven't been upstreamed yet
#asahi-dev · 2026-10-25 16:24
hex86[m]and to answer your question, I would really like to get it upstreamed; There's basically nobody using the haptic functionality in the kernel right now (See: Libinput) and so having more of the haptic functionality actually in the kernel would definitely help push adoption
#asahi-dev · 2026-10-25 16:24
hex86[m]Working through it now
#asahi-dev · 2026-10-25 16:24
hex86[m]sofus: Thank you so much for the feedback!
#asahi-dev · 2026-10-12 09:43
hex86[m]Ohh wait right yea it wouldn't necessarily run on macos 😅
#asahi-dev · 2026-10-12 09:43
hex86[m]Out of curiosity, why not just use the base calamares installer?
#asahi-dev · 2026-10-12 09:40
hex86[m]so cool
#asahi-dev · 2026-10-12 09:40
hex86[m]holy shit
#asahi-dev · 2026-09-21 19:51
hex86[m]James Calligeros: Hi! I wanted to ask a followup to the review you left me 3 weeks ago, (https://github.com/AsahiLinux/linux/pull/573#discussion_r3888280798) I was wondering, for this kconfig issue how would you suggest I resolve this issue?