#
#asahi-dev · 2025-03-14 21:19
svenwhich brings us back to <sven> it shouldn't matter but we really have no way of knowing
#asahi-dev · 2025-03-14 21:18
fl0_idI was just comparing it to other socs and everywhere else init_common is used but not there
#asahi-dev · 2025-03-14 21:18
alyssa:P
#asahi-dev · 2025-03-14 21:18
alyssanot in m1n1 tho
#asahi-dev · 2025-03-14 21:18
alyssawell we do in the kernel
#asahi-dev · 2025-03-14 21:18
alyssawe don't pay by the line from here ;)
#asahi-dev · 2025-03-14 21:18
fl0_idmmh ok sure
#asahi-dev · 2025-03-14 21:18
svenyup
#asahi-dev · 2025-03-14 21:17
alyssa^ something to reevaluate in a year from now to clean up. best not to sneeze on it yet
#asahi-dev · 2025-03-14 21:16
svenif the bits are wrong you can everything from an obvious explosion early in the kernel to very subtle misbehavior later on
#asahi-dev · 2025-03-14 21:15
svenit shouldn't matter but we really have no way of knowing
#asahi-dev · 2025-03-14 21:15
svenI wouldn't touch the order
#asahi-dev · 2025-03-14 21:14
fl0_idand I cannot just test t6030 as I only have t6031
#asahi-dev · 2025-03-14 21:14
fl0_iddoes someone know if the order of chicken bits usually needs to be in order? because I would like to simplify the previous (unmerged) t6030 bringup code by moving everything that is common to init_common_everest() but not all common parts right now are directly after another
#asahi-dev · 2025-03-14 21:09
fl0_idoh ok good to know, just saw that this was their commit I think
#asahi-dev · 2025-03-14 21:09
fl0_idalyssa haha
#asahi-dev · 2025-03-14 19:48
alyssanicolas17: damn, goals.
#asahi-dev · 2025-03-14 19:41
nicolas17alyssa: DannyB hasn't talked on IRC since december 2023 btw
#asahi-dev · 2025-03-14 19:26
svenlooks like some implementation defined register. unless there’s a name in xnu sources or whatever it’s going to be very hard to figure out what it does if it’s part of the chicken bit sequence
#asahi-dev · 2025-03-14 18:25
alyssaDannyB: ^
#asahi-dev · 2025-03-14 18:03
fl0_id(there's a comment saying "it is new but no idea what it does")
#asahi-dev · 2025-03-14 18:02
fl0_idif daniel berlin is here, do you have any idea what reg_set(s3_0_c15_c2_3, BIT(3)); (and the next line) does now?
#asahi-dev · 2025-03-14 18:02
fl0_idinteresting comparing existing code for t6030 to t6031. a lot is the same but some bits are not, and not sure if that actually has a reason or not lol
#asahi-dev · 2025-03-14 18:01
fl0_idah right
#asahi-dev · 2025-03-14 17:55
svenprobably to prevent a compiler warning when the argument of a function isn’t used anywhere
#asahi-dev · 2025-03-14 17:53
fl0_idif there is UNUSED(rev); (or similar) does it mean it is actually unused or shouldn't be used or what's the dea? (yes I checked where that is defined, it didn't help)
#asahi-dev · 2025-03-14 17:20
fl0_idmmh, 6031 chip id is in hv/__ini__.py on main, but not sure if that is enough for hv
#asahi-dev · 2025-03-14 17:15
fl0_idI cleaned the t6030-bringup commits up a little by moving constants to midr.h - but I couldn't test this yet and don't know if a-ramses would be fine with me continuing it. (though ofc all their commits are still by them) https://github.com/step21/m1n1/tree/t6031-bringup (I renamed it t6031-bringup as I don't have a t6030 to test)
#asahi-dev · 2025-03-14 17:04
chaos_princessdumped as either tar or cpio on ESP, there is a kernel patch to add a secondary firmware directory, then hooks somewhere in boot process to mount a tmpfs there and extract the firmware from esp
#asahi-dev · 2025-03-14 17:02
aditya*wifi firmware
#asahi-dev · 2025-03-14 17:02
adityaBtw out of curiosity, I want to know how is the firmware dumped to Linux in Asahi Linux now?
#asahi-dev · 2025-03-14 16:52
adityaAlso, hid devs might want to see this PR, https://github.com/AsahiLinux/linux/pull/372
#asahi-dev · 2025-03-14 16:51
adityaThere is also a long standing weird bug in your firmware collection script, which we discovered when using it for our Macs. I had sent a PR long ago here: https://github.com/AsahiLinux/asahi-installer/pull/277
#asahi-dev · 2025-03-14 16:46
aditya*Can I (not I can)
#asahi-dev · 2025-03-14 16:46
adityaHi guys. I can I have an HID record of the trackpad on M1 Macs. I want to compare it with the t2 ones so that I can trace any chance of getting trackpad size using report ID. Otherwise libinput trackpad coordinates are anyways working well,
#asahi-dev · 2025-03-14 16:21
mischa85_yeah i also had to do some changes to the adt parsing for t6041
#asahi-dev · 2025-03-14 16:17
fl0_id(and not just a dirty hack that potentially breaks stuff)
#asahi-dev · 2025-03-14 16:17
fl0_id(I could make a PR if somebody confirms that this is ok to do...)
#asahi-dev · 2025-03-14 16:16
fl0_idok. for dumping adt I had to make a small hack to make it work, but not sure if that is actually the right way to do things ... or if I did sth wrong https://www.pastery.net/jgkwgt/
#asahi-dev · 2025-03-14 16:14
svendunno, would have to take a closer look
#asahi-dev · 2025-03-14 16:14
fl0_idand conflict resolving I mean
#asahi-dev · 2025-03-14 16:13
fl0_iddoes it just need commit prettyfying?
#asahi-dev · 2025-03-14 16:13
fl0_idsven you mean this one? https://github.com/AsahiLinux/m1n1/pull/426
#asahi-dev · 2025-03-14 16:10
sventhere are also still two or three open MRs, maybe rebasing these is enough
#asahi-dev · 2025-03-14 16:10
svenor maybe that's already upstream? dunno
#asahi-dev · 2025-03-14 16:10
fl0_idyeah, probably. I haven't tried it, but somebody got usb working so maybe
#asahi-dev · 2025-03-14 16:10
sveniirc at least the cpu start logic
#asahi-dev · 2025-03-14 16:09
svenit'll probably need some minor changes at least
#asahi-dev · 2025-03-14 16:08
fl0_idpmgr still exists there I think, but dumping it gave not so nice output
#asahi-dev · 2025-03-14 16:07
fl0_iddoes somebody know if hv should work on m3? (otherwise I assume no)

plus ›