#
…

2021-12-16

00:01Dcow has joined #asahi-dev
00:18aleasto has quit [Quit: Konversation terminated!]
00:28Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
00:39jannauhid-appleft is no more, suppport is integrated in hid-magicmouse
00:42jannauextended report mode is only switched on by request from hid-magicmouse, I added resolution for X and Y based on the j314 trackpad, no idea if the other ones have other dimensions
00:43jannaufixed all report from kernel test robot
00:54balrog has quit [Quit: Bye]
01:00Dcow has joined #asahi-dev
01:00balrog has joined #asahi-dev
01:10kov has joined #asahi-dev
01:11Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:11yuyichao has quit [Ping timeout: 480 seconds]
02:13chadmeddoes the ANS driver depend on ARCH_APPLE to be built? i want to test it on my A1708 since im pretty sure its the same nvme controller
02:22c10l8 is now known as c10l
02:28chadmedoh its not a platform device on the intel macs anyway rip
02:59riker77_ has joined #asahi-dev
03:01riker77 has quit [Ping timeout: 480 seconds]
03:01riker77_ is now known as riker77
03:06phiologe has joined #asahi-dev
03:09PhilippvK has quit [Ping timeout: 480 seconds]
03:23yuyichao has joined #asahi-dev
03:24yuyichao has quit []
03:27yuyichao has joined #asahi-dev
04:03PhilippvK has joined #asahi-dev
04:05kov has quit [Quit: Coyote finally caught me]
04:06phiologe has quit [Ping timeout: 480 seconds]
04:08kov has joined #asahi-dev
04:19marcanchadmed: NVMe support for intel macs has been in mainline for years now
04:19marcan(the quirks they need that is)
04:50marcanjannau: awesome, I'll test it in a bit!
04:57Dcow has joined #asahi-dev
06:00Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:08chadmedtheres still a bug on the A1708 (and others i believe) where if you let the machine suspend you lose disk access on wake and everything breaks. something to do with d3cold/controller power management
06:16the_lanetly_052__ has joined #asahi-dev
06:48Dcow has joined #asahi-dev
07:30the_lanetly_052___ has joined #asahi-dev
07:32chadmed has quit [Quit: Konversation terminated!]
07:32chadmed has joined #asahi-dev
07:33Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:36the_lanetly_052__ has quit [Ping timeout: 480 seconds]
08:03j`eyjannau: awesome
09:24kettenisjannau: the j314 touchpad coordinates seem to roughly match the j293 values I'm seeing
09:30kettenisalso, I'm seeing a "read" packet for "device" 0 with "type" 0xe010 and I'm wondering if that provides some sort of identification of the device
09:47jannaukettenis: I see that as well. message payload "e0 10 00 00 00". which doubles the type (ignoring endianess)
09:47Dcow has joined #asahi-dev
09:48jannautouchpad coordinates are rounded away from zero to the next multiple of 100, I should have added the measured values as comment
09:50riker77 has quit [Quit: Quitting IRC - gone for good...]
09:50jannauthe first thing I receive is a packet with payload "a0 80 00 00" i.e. too short for the message header
09:52the_lanetly_052___ has quit [Ping timeout: 480 seconds]
10:13kettenisjannau: I see that one too
10:32riker77 has joined #asahi-dev
10:41_jannau_ has quit [Ping timeout: 480 seconds]
10:41jannau has quit [Ping timeout: 480 seconds]
10:56thunfisch has quit [Ping timeout: 480 seconds]
10:57_jannau_ has joined #asahi-dev
10:59jannau has joined #asahi-dev
11:03kettenisjannau, the ioreg output that marcan pasted at some point has a VendorID and ProductID for the keyboard/touchpad
11:04kettenis"VendorID" = 1452
11:04kettenis"ProductID" = 641
11:04kettenisso it might make sense to use these in the driver
11:08Dcow__ has joined #asahi-dev
11:11kettenismy j293 with ISO keyboard layout has "ProductID" = 833
11:12_jannau_vendor id is Apple's USB vender id
11:13Dcow_ has quit [Ping timeout: 480 seconds]
11:13_jannau_product id's are not yet in linux' hid-ids.h
11:22svenchadmed: the Intel Macs use a related nvme chip running in a different mode fwiw
11:27the_lanetly_052 has joined #asahi-dev
11:28aleasto has joined #asahi-dev
11:42povikhere j314 (14' mbp) with "ProductID" = 834
11:42Jamie[m]1unless I'm being obtuse, the m3 mailbox interface in AVD seems different to the m3 mailbox interface in the kernel
11:46kettenispovik, what keyboard layout is that?
11:46somkls^ has quit [Ping timeout: 480 seconds]
11:48poviki don't know, let's see
11:50povikit's czech localization, don't know if that's ISO or not
11:51povikapple support says i have ISO keyboard
11:58sppdqd[m] has joined #asahi-dev
12:04tom-w has quit [Quit: Connection closed for inactivity]
12:06svenJamie[m]1: the m3 mailbox in the kernel is used for the thunderbolt ("CIO") co-processors
12:06svenAVD is probably yet another thing. afaik it also doesn't run rtkit
12:10jannauj314 with iso international has "ProductID" = 834. let's hope there is a way to read the ID's over HID
12:10jannauioreg output looks like could be possible
12:16thunfisch has joined #asahi-dev
12:17blzd has quit [Remote host closed the connection]
12:25thunfisch has quit [Quit: frrrp!]
12:26thunfisch has joined #asahi-dev
12:30Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
12:50kettenisso it seems that apple no longer uses separate product IDs for the ANIS, ISO and JIS keyboard layouts
12:59ketteniss/ANIS/ANSI/
13:00ChaosPrincesscan someone help out, i am trying to update a version of m1n1 that is on the apfs volume, but kmutil configure-boot fails with error 'Invalid Mach-O boot properties'
13:03_jannau_ChaosPrincess: check if the m1n1 apfs volume is the actiive startup disk. that's a requirement with macos 12.0 1tr. please continue in #asahi
13:54Gaspare has joined #asahi-dev
14:01Gaspare has quit [Remote host closed the connection]
14:17the_lanetly_052 has quit [Remote host closed the connection]
14:39the_lanetly_052 has joined #asahi-dev
14:58yuyichao has quit [Ping timeout: 480 seconds]
15:14yuyichao has joined #asahi-dev
15:30riker77 has quit [Quit: Quitting IRC - gone for good...]
16:05riker77 has joined #asahi-dev
16:09marcanJamie[m]1: AVD does not use the m3 mailbox
16:09marcanAVD is just a random hardware block that happens to include a random cortex-m3 that doesn't run RTKit
16:09marcanit is unrelated to anything else
16:10marcanthere will be no shared code for it or mailbox driver or anything; it'll talk directly to the hardware
16:11ChaosPrincesswhat is avd used for?
16:11marcanvideo decoder
17:30kgarrington has joined #asahi-dev
17:31kgarrington has quit [Remote host closed the connection]
17:34kgarrington has joined #asahi-dev
17:36kgarrington has quit [Remote host closed the connection]
17:38the_lanetly_052 has quit [Ping timeout: 480 seconds]
19:05Gaspare has joined #asahi-dev
19:33Gaspare has quit [Ping timeout: 480 seconds]
19:44Lightsword_ is now known as Lightsword
20:02kgarrington has joined #asahi-dev
20:04aleasto has quit [Remote host closed the connection]
20:05kgarrington has quit [Remote host closed the connection]
20:14kgarrington has joined #asahi-dev
20:14kgarrington has quit [Remote host closed the connection]
20:14tpw_rules has joined #asahi-dev
21:00kgarrington has joined #asahi-dev
21:00kgarrington has quit [Remote host closed the connection]
21:10tpw_rulesso i am working on a boot flow using https://github.com/kettenis/u-boot/tree/apple-m1-m1n1-nvme/ and the latest linux-asahi kernel as of today. it seems there's an issue where if u-boot starts the nvme by running "nvme scan", the kernel fails to start it and prints "apple-ans-nvme 27bcc0000.nvme: RTKit did not boot". but if i stop u-boot from running that command, the kernel can start the nvme fine and everything works
21:12tpw_rulesin both cases i'm booting off a usb disk. i'm not sure if u-boot should be de-initializing something before it starts up the kernel, or the kernel needs better handling of an nvme that's already been initialized. cc: kettenis sven
21:12tpw_rules(to be clear, this is not a new problem caused by recent changes AFAICT. i don't know of a setup that works)
21:15svenyeah, that's known
21:15svenu-boot will eventually need to shutdown the co-processor before handing control over to linux
21:16svenbut i think openbsd currently required the co-proc to be already running
21:16sventhis is all still very much WIP :-)
21:16tpw_rulesis that something u-boot currently doesn't do, or do we not know how to shut it down?
21:16svenuboot just doesn't do it because of this: <sven> but i think openbsd currently required the co-proc to be already running
21:16tpw_rulesif you can point me to code that shuts it down, i can probably figure out a patch for my setup
21:17tpw_ruleson the other hand, it feels like the kernel should be able to either use it if it's already started, or reset it
21:17svenor, well, unless we find way to actually reset the processor
21:18tpw_rulesok so that's not possible for what we can call hardware limitations
21:18tpw_rulesjust to be sure, the function apple_rtkit_shutdown is defined in a different commit?
21:18svenwhat do you mean defined?
21:19sventhis is no the nvme driver that's in the asahi branch fwiw
21:19tpw_rulesi mean i only see its prototype and not a definition
21:19svenclick the link again?
21:19svenit should take you to the function
21:19tpw_rulesit doesn't take me anywhere in particular
21:20svenit's in that commit
21:20svenin rtkit.c
21:20svenline 762
21:20tpw_rulesah, it's behind the "large diffs are not rendered by default" banner
21:20tpw_rulesi see it now. cool, thank you!
21:23svenah, so the link doesn't work unless you already clicked on show more once. annoying :/
21:42Gaspare has joined #asahi-dev
23:20Gaspare has quit [Read error: Connection reset by peer]
23:31squags has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
23:42King_InuYasha has quit [Remote host closed the connection]
23:55squags has joined #asahi-dev
…