millenialhacker has quit [Ping timeout: 480 seconds]
kettenis has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
the_lanetly_052 has joined #asahi-dev
MajorBiscuit has joined #asahi-dev
the_lanetly_052__ has joined #asahi-dev
the_lanetly_052 has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has quit []
kov has joined #asahi-dev
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
hir0pro has joined #asahi-dev
hir0pro has quit [Remote host closed the connection]
hir0pro has joined #asahi-dev
MajorBiscuit has quit [Quit: WeeChat 3.5]
the_lanetly_052 has joined #asahi-dev
pseigo has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
pseigo has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
<marcan>
might stream the M2 wrap-up (assuming I don't run into weirdness), i.e. dockchannel & friends drivers, in a bit
<sven>
\o/
<ar>
marcan: btw, what do you think is the purpose of the accelerometer on dockchannel in m2? is it integrated in the soc and they intend to use the same one in ipads?
<ar>
because the obvious reasons (parking hdd, rotating touchscreen) don't apply on those laptops
<marcan>
no, it would be in the trackpad
<marcan>
they used to have an option for accelerometer on the motherboard but I don't think they ever populated it on shipping machines, at least newer ones
<j`ey>
marcan: have you been fed?
<marcan>
yes
<sven>
:D
<marcan>
ar: if I had to guess it's related to Force Touch; if I'm looking at this photo right, the whole touchpad PCB is mounted on the floating platform side, including the accelerometer
<marcan>
might even be used only for Force Touch calibration
<marcan>
that would actually make sense
<marcan>
since I do remember the calibration app running through a bunch of test sequences and it has to get feedback somehow
<marcan>
probably cheaper and more reliable to throw an accel there worth pennies, than try to build in some kind of weirdo calibration jig in the factory that couples it externally
<ar>
i wonder if it's a full-featured accelerometer. i used to play neverball by tilting my whole thinkpad x300 back in 2010 or so ;)
<sven>
marcan: do you already have something in place for firmware renaming for people who’ve already run the installer?
<marcan>
no, just prepared for it by having the tarball around. it's on the list to write something (can probably just live in the installer repo) to package up the firmware stuff as a package with a postinstall we can ship
<marcan>
ar: probably! and since we have that calibration tool, I can probably figure out how to use it even if normally it never is
<sven>
alright, I’ll just write the renaming part for the installer for now then
<marcan>
cool :)
<sven>
packaging stuff is too far into user space for me ;p
millenialhacker has quit [Remote host closed the connection]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Remote host closed the connection]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
hir0pro has quit [Quit: hir0pro]
kettenis has joined #asahi-dev
MajorBiscuit has joined #asahi-dev
MajorBiscuit has quit [Quit: WeeChat 3.5]
kettenis has quit [Ping timeout: 480 seconds]
nicolas17 has joined #asahi-dev
<j`ey>
sven: in your bindings, you mention "net/wireless/brcm,brcm4329-fmac.yaml"
<j`ey>
but it's "bindings/net/wireless/brcm,bcm4329-fmac.yaml"
<j`ey>
(second brcm is bcm)
<sven>
ah, whoops. good catch!
kettenis has joined #asahi-dev
kettenis_ has joined #asahi-dev
kettenis has quit [Quit: leaving]
kettenis_ is now known as kettenis
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
___nick___ has quit [Ping timeout: 480 seconds]
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
the_lanetly_052 has quit [Ping timeout: 480 seconds]
<marcan>
sven: so what really sucks now is that this firmware is not in /usr/share/firmware, it's one of the things the installer copies into Preboot, but apparently iBoot does not load it. Doesn't matter for M2 since it'll be for new installs, but we're going to have the same problem with the M1 MBP for touch bar support. so pacman isn't going to cut it for that one... :(
<marcan>
(unless we ship apfs, or ship something that downloads it from the CDN under linux)
<marcan>
guess I'm going to have to start making the installer copy more stuff just in case...
<sven>
ugh…
<marcan>
and we could run into firmware version compatibility problems too, which we weren't expecting for any of the other linux-loaded firmwares... so distros really are going to have to be careful about keeping stuff up to date with the manifest for this one.
<sven>
they should’ve just gotten rid of that touchbar :/
<marcan>
well now this is for the trackpad too so...
<sven>
fair enough…
<nicolas17>
hm I was thinking of writing my own partialzip-like tool in Python for other purposes
<sven>
I wonder why this firmware is different from the others
<marcan>
something something signing?
<sven>
like, I get why WiFi and Bluetooth und that usb thing has to be loaded by Linux
<marcan>
but the whole root filesystem is signed so I don't get it
<sven>
but why the touchpad thingy?!
<marcan>
yeah, they should've just embedded this in MTP firmware
<marcan>
why the hell is it separate
<sven>
yeah
<marcan>
also this does mean we need to actually ship img4tool (or a minimal python reimplementation) with the installer
<sven>
and all this just to get a keyboard and the touchpad to work :(
<marcan>
touchpad only
<nicolas17>
yes, it makes fixed-size "block" requests right?
<marcan>
keyboard is easy...
<marcan>
nicolas17: yes
<marcan>
well, not entirely fixed
<marcan>
but kinda
<sven>
maybe I should’ve paid better attention during the stream. I thought it was both keyboard and touchpad
<marcan>
no, keyboard has worked since the previous stream
<marcan>
this is the broadcom multitouch firmware
<marcan>
I just haven't written the keyboard linux driver yet
<sven>
for some reason I thought keyboard kinda worked but today you discovered that firmware blob… and now that I wrote it I realize that doesn’t make any sense