2021-09-11
00:02zigmars has quit [Ping timeout: 480 seconds]
00:05zigmars has joined #asahi
00:11yuyichao has joined #asahi
00:13zigmars has quit [Ping timeout: 480 seconds]
00:23zigmars has joined #asahi
00:31zigmars has quit [Ping timeout: 480 seconds]
00:34zigmars_ has joined #asahi
00:42zigmars_ has quit [Ping timeout: 480 seconds]
00:52zigmars has joined #asahi
00:54zigmars_ has joined #asahi
00:54zigmars has quit [Remote host closed the connection]
01:02zigmars_ has quit [Ping timeout: 480 seconds]
01:03dfip^ has quit [Ping timeout: 480 seconds]
01:08dfip^ has joined #asahi
01:12zigmars has joined #asahi
01:13zigmars_ has joined #asahi
01:13zigmars has quit [Read error: Connection reset by peer]
01:20Emantor has quit [Quit: ZNC - http://znc.in]
01:20Emantor has joined #asahi
01:27yuyichao has quit [Ping timeout: 480 seconds]
01:40zigmars_ has quit [Ping timeout: 480 seconds]
01:43zigmars has joined #asahi
01:45yuyichao has joined #asahi
01:51zigmars has quit [Ping timeout: 480 seconds]
01:54zigmars has joined #asahi
02:02zigmars has quit [Ping timeout: 480 seconds]
02:05zigmars has joined #asahi
02:13zigmars has quit [Ping timeout: 480 seconds]
02:16zigmars has joined #asahi
02:24zigmars has quit [Ping timeout: 480 seconds]
02:34zigmars has joined #asahi
02:36zigmars_ has joined #asahi
02:36zigmars has quit [Read error: Connection reset by peer]
02:44zigmars_ has quit [Ping timeout: 480 seconds]
02:47zigmars has joined #asahi
02:55zigmars has quit [Ping timeout: 480 seconds]
02:57phiologe has joined #asahi
03:01PhilippvK has quit [Ping timeout: 480 seconds]
03:05zigmars has joined #asahi
03:13zigmars has quit [Ping timeout: 480 seconds]
03:23zigmars has joined #asahi
03:31zigmars has quit [Ping timeout: 480 seconds]
03:34zigmars has joined #asahi
03:42zigmars has quit [Ping timeout: 480 seconds]
03:45marvin24 has joined #asahi
03:49marvin24_ has quit [Ping timeout: 480 seconds]
03:52zigmars has joined #asahi
03:54zigmars_ has joined #asahi
03:54zigmars has quit [Read error: Connection reset by peer]
04:02zigmars_ has quit [Ping timeout: 480 seconds]
04:04zigmars has joined #asahi
04:31zigmars has quit [Ping timeout: 480 seconds]
04:39zigmars has joined #asahi
04:47zigmars has quit [Ping timeout: 480 seconds]
04:50zigmars has joined #asahi
04:58zigmars has quit [Ping timeout: 480 seconds]
05:01zigmars has joined #asahi
05:09zigmars has quit [Ping timeout: 480 seconds]
05:19zigmars has joined #asahi
05:27zigmars has quit [Ping timeout: 480 seconds]
05:30zigmars has joined #asahi
05:38zigmars has quit [Ping timeout: 480 seconds]
05:41zigmars has joined #asahi
05:49zigmars has quit [Ping timeout: 480 seconds]
05:52zigmars has joined #asahi
06:00zigmars has quit [Ping timeout: 480 seconds]
06:03zigmars has joined #asahi
06:10yuyichao has quit [Ping timeout: 480 seconds]
06:11zigmars has quit [Ping timeout: 480 seconds]
06:18robinp_ has joined #asahi
06:21zigmars has joined #asahi
06:22psykose has quit [Remote host closed the connection]
06:22zigmars has quit [Read error: Connection reset by peer]
06:23zigmars has joined #asahi
06:23psykose has joined #asahi
06:25robinp has quit [Ping timeout: 480 seconds]
06:31zigmars has quit [Ping timeout: 480 seconds]
06:43zigmars has joined #asahi
06:49zigmars has quit [Ping timeout: 480 seconds]
06:53chadmed has quit [Remote host closed the connection]
06:53chadmed has joined #asahi
06:59zigmars has joined #asahi
07:01zigmars_ has joined #asahi
07:01zigmars has quit [Remote host closed the connection]
07:09zigmars_ has quit [Ping timeout: 480 seconds]
07:19zigmars has joined #asahi
07:21zigmars_ has joined #asahi
07:21zigmars has quit [Read error: Connection reset by peer]
07:24awal2 has quit [Ping timeout: 480 seconds]
07:29zigmars_ has quit [Ping timeout: 480 seconds]
07:32zigmars has joined #asahi
07:37psykose has quit [Remote host closed the connection]
07:40zigmars has quit [Ping timeout: 480 seconds]
07:42awal2 has joined #asahi
07:43zigmars has joined #asahi
07:51zigmars has quit [Ping timeout: 480 seconds]
07:53zigmars has joined #asahi
08:02zigmars has quit [Ping timeout: 480 seconds]
08:12zigmars has joined #asahi
08:14zigmars has quit [Read error: Connection reset by peer]
08:14zigmars_ has joined #asahi
08:21zigmars_ has quit [Ping timeout: 480 seconds]
08:24zigmars has joined #asahi
08:25awal3 has joined #asahi
08:26awal2 has quit [Ping timeout: 480 seconds]
08:32zigmars has quit [Ping timeout: 480 seconds]
08:35zigmars has joined #asahi
08:43zigmars has quit [Ping timeout: 480 seconds]
08:45psykose has joined #asahi
08:46zigmars has joined #asahi
08:54zigmars has quit [Ping timeout: 480 seconds]
08:57zigmars has joined #asahi
09:05zigmars has quit [Ping timeout: 480 seconds]
09:08zigmars has joined #asahi
09:16zigmars has quit [Ping timeout: 480 seconds]
09:22robinp_ is now known as robinp
09:26zigmars has joined #asahi
09:28zigmars_ has joined #asahi
09:28zigmars has quit [Remote host closed the connection]
09:36zigmars_ has quit [Ping timeout: 480 seconds]
09:39zigmars has joined #asahi
09:47zigmars has quit [Ping timeout: 480 seconds]
09:58zigmars has joined #asahi
10:08zigmars has quit [Remote host closed the connection]
10:16zigmars has joined #asahi
10:18zigmars_ has joined #asahi
10:18zigmars has quit [Read error: Connection reset by peer]
10:26zigmars_ has quit [Ping timeout: 480 seconds]
10:29zigmars has joined #asahi
10:37zigmars has quit [Ping timeout: 480 seconds]
10:40zigmars has joined #asahi
10:43zopieux has quit [Ping timeout: 480 seconds]
10:45zopieux has joined #asahi
10:48zigmars has quit [Ping timeout: 480 seconds]
10:58zigmars has joined #asahi
11:00zigmars_ has joined #asahi
11:00zigmars has quit [Read error: Connection reset by peer]
11:08zigmars_ has quit [Ping timeout: 480 seconds]
11:12landscape15[m]Sorry for the obvious question: Does m1n1 operate similar than OpenCore?
11:13zigmars has joined #asahi
11:15malvo has joined #asahi
11:16landscape15[m]Both are bootloaders and a virtual EFI environment (a translator for ACPI).
11:21landscape15[m]Oh ok, so it is an hypervisor that interact with iboot i suppose.
11:23landscape15[m]So then it is independent from macOS?
11:24jnm1n1 is independent from macos in the sense that iboot->m1n1->linux is a perfectly valid and possible boot flow
11:25landscape15[m]Ok it's very close to an embedded device tree
11:26landscape15[m]Most smartphones use a long device tree to boot Android.
11:29landscape15[m]Nothing. I only think the boot process will be very slow initially.
12:15aleasto has joined #asahi
12:23landscape15[m]Ok, but why Marcan says it's a hypervisor? (i've watched the m1n1 recap)
12:23j_ey it's going to twiddle some CPU bits, modify the device tree a bit, and then load the next thing
12:24landscape15[m]oh thanks. Unfortunately there is not a lot of official documentation from Apple.
12:32kettenis_ is now known as kettenis
12:33landscape15[m]Power Management research will be a pain!
12:33kettenissven: why do you document the mailboxes as 64+32 bits when the driver does a writeq to both registers?
12:33j_eysend an email to timcook@apple.com 'hello how do you detect that usb was disconnected properly?'
12:36landscape15[m]j_ey: his mail is tcook@apple.com i think :)
12:37landscape15[m]j_ey: Yeah i'm quite sure ;)
12:41sventhe other two irqs are also symmetric fwiw. i think they literally just hooked up the same HW block to both processors
12:46kettenissven: it is a bit difficult for me to review the mailbox DT binding from a OpenBSD/U-Boot standpoint since it isn't clear how the upper layers are going to look
12:49svenyeah, i'm not really sure how those will look like yet either. two two alternative i see is to have a separate rtkit node (like https://lore.kernel.org/all/550C7534.8070100@wwwdotorg.org/ suggested for the raspberry pi case) or to have the rtkit handling be part of the nvme driver (shared as some library)
12:50vmcs has joined #asahi
12:51alyssakettenis: sven and I had discussed a mailbox driver that only deals with the hardware, and then a soft RTKit library which implements all the firmware stuff on top of a generic mailbox
12:51sventhere is at least the SEP which will also use the mailbox HW but doesn't speak rtkit at all
12:52alyssamy DCP tree has that setup with some version of sven's mbox and sven's RTKit .. should probably rebase on what's on the list
12:52sventhe other alternative is that separate rtkit node that would handle the rtkit stuff and that the nvme driver could reference
12:52alyssasven: I really dislike that on principle -- device trees are supposed to model the hardware.
12:53kettenisI think what matters here is we end up with multiple device trees node that need to reference specific channels exposes by the RTKit firmware
12:53svenyes. so if we have multiple nodes that need to talk to difference rtkit channels we need that node
12:55alyssasven: For DCP at least, there are lots of rtkit channels but I see no reason not to stick it all in dcp.ko ... the rtkit library api is π― natural to me
12:56alyssaAGX i don't know how it looks but I can't possibly fathom a reason not to do it all in agx.ko
12:57alyssasven: right... it seems like this is future proofing for the sake of future proofing, not because of a particular engineering objective ...
12:59marcan< sven> the other two irqs are also symmetric fwiw. i think they literally just hooked up the same HW block to both processors <- just like the wii :p
12:59kettenisanyway, I think either design could work for U-Boot and OpenBSD, so I think the DT binding for the mailbox should be fine
13:00alyssakettenis: I'm waiting for M2 Macbooks to be released so I can get a used M1 air for cheap π
13:01vmcs has quit [Quit: leaving]
13:01kettenisit looks like both iop,ascwrap-v4 and iop,m3wrap-v2-acio were first introduced on the M1, so even the compatible names make sense to me ;)
13:02marcanthe library solution seems reasonable, especially considering all the display related sub-drivers in DCP are the kind of thing that ends up in one big module on linux anyway, for other hardware
13:09kettenisI don't think it would be too horrible if we skip the rtkit firmware node for now and add it later if it turns out we need it
13:11kettenisbtw, maz and alyssa, I pushed a small change to U-Boot to update the msi-ranges property for the PCIe node to match the proposed binding
13:26yuyichao has joined #asahi
13:59j_eywhat format should the initrd to u-boot be? I get 'Wrong Ramdisk Image Format' with a .cpio.gz
14:07roxfanhttps://github.com/jithinmdas91/u-boot-raspi/blob/e25112be280199d59ed148382fc7a9fac1715b8c/common/image.c#L927 looks complicated
14:09j_eythere's IMAGE_FORMAT_LEGACY IMAGE_FORMAT_FIT and CONFIG_SUPPORT_RAW_INITRD, problem is that m1n1 doesnt support uncompressed cpio which is what I assume CONFIG_SUPPORT_RAW_INITRD is (maybe)
14:14kettenisI believe that with the UEFI boot path folks typically use grub and grub does the initrd loading
14:16kettenisalthough there is EFISTUB as well which allows you to directly load a kernel if I understand things correctly
14:18kettenisnot sure how initrd gets loaded in that scenario, although I have seen people mention that this relies on the EFI LoadFile2 protocol
15:27svenhuh, does anyone know where the SMC firmware is stored? can't find it in the ipsw or in the preboot volume
16:14zigmars has quit [Remote host closed the connection]
16:22zigmars has joined #asahi
16:24zigmars_ has joined #asahi
16:24zigmars has quit [Read error: Connection reset by peer]
16:25zigmars_ has quit [Remote host closed the connection]
16:25zigmars has joined #asahi
16:38svenpipcet[m]: so it looks like this tps USB PD chip has _two_ i2c buses and with that also two independent interrupt controllers. i suspect one of them is connected to the main CPU while the other is connected to the SMC
16:38svencan you try to see if you can break charging when you only disable interrupts in one of those two?
16:58PeterB[m] has joined #asahi
17:06zigmars has quit [Remote host closed the connection]
17:13zigmars has joined #asahi
17:22jnoxon has quit [Ping timeout: 480 seconds]
17:41zigmars has quit [Remote host closed the connection]
17:44zigmars has joined #asahi
18:25boardwalk has quit [Quit: The Lounge - https://thelounge.chat]
18:39vmrope_ has joined #asahi
18:43vmrope_ has quit [Quit: leaving]
18:47boardwalk has joined #asahi
20:13jmcneillanyway, don't be ashamed of being from ontario, it's a beautiful province and in another life i would probably have stayed there
20:14alyssa(also, errr, hello from m1 linux. It really bugs me how much more usable this is already than my Chromebook)
20:16alyssaj_ey: about 3 seconds. but that could easily just be the monitor, nothing to do with the driver stack
20:19alyssaIs it just a mix of System Preferences' Displays tab changing scaling instantly, together with the "m1 go brrr magic" that my twitter follower count relies on?
20:20alyssaon the former charge -- by default macOS on M1 doesn't change physical resolution at all, just reconfigures software scaling. of course that'll be instant..
20:20alyssaI imagine that's a smoke and mirrors trick for the MacBooks... just boot at maximum resolution and *never change it* ... Wow, so fast!
20:31Bastian[m]https://youtu.be/KfbiX7JFKsE?t=368 looks fairly normal here, maybe it's really fast if the screen is still on? closing the lid and switching to monitor only seems somewhat fast
20:33Bastian[m]oh oops is that even an m1 macbook?
20:40Bastian[m]https://twitter.com/stroughtonsmith/status/1329259493075668992 I think this might be the origin of the claim, but I can't find a video of attaching a monitor only the resolution change
20:49alyssaOf course that raises a question already -- there are two type-c ports and only one dcpext
20:55alyssasven: "REG_ACIOPHY_XBAR_DPMODE_MASK" this sort of thing (from corellium atcphy) seems very much relevant
20:56reillyeon has quit [Quit: The Lounge - https://thelounge.github.io]
20:56reillyeon has joined #asahi
21:02alyssaI also wonder, is it possible to have dual type-c monitors on the mac mini, if no hdmi is plugged in?
21:05alyssa> While the M1 MacBooks natively support just one monitor, the M1 Mac Mini does natively support up to two external monitors - one via the HDMI port and a second via USB-C. But the latest models of the MacBook Air and MacBook Pro support only one external display.
21:05alyssa(source: https://www.macworld.co.uk/how-to/how-connect-two-or-more-external-displays-apple-silicon-m1-mac-3799794/ )
21:05alyssathat confirms my understanding of the topology. ok, good, not totally losing my mind here :)
21:11alyssawithout atcphy stuff, dcp driver can only do HDMI or internal panel respectively. good enough for "now"
21:12dottedmagVideo via type-C port -- is it USB-C Alternate Mode with Display Port, or something else?
22:08rossy has quit [Ping timeout: 480 seconds]
22:08rossy has joined #asahi
22:27* brentr123[m]uploaded an audio file: (3KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/olLpiwuIHvuqTMKaWdhvwUUB/Voice%20message%20-%2009.11.2021%2018.27.55.ogg >
22:28brentr123[m]Sorry Iβve been out of the loop, I just started college so I wasnβt able to come on here as much how has progress been so fast?
22:35brentr123[m]Like all the tweets and stuff about progress
22:35brentr123[m]Seems kinda
22:35brentr123[m]Quick
22:39brentr123[m]Yeah itβs my freshman year in college so I gotta take care of school work and shit
22:41brentr123[m]What the fuck is that horse emote supposed to mean
22:45alyssaanyway. i've said it before and will say it again -- sven is the unsung hero of the m1 kernel effort
22:45alyssamy added value is just gfx witchcraft and being inhumanly stubborn enough to decide "i'm using this m1 as my linux box by Sep 1, full stop"
22:47alyssaactually, well, the rk3399 sound drivers have been totally broken for a while so I use that adapter there too
23:03aleasto has quit [Quit: Konversation terminated!]
23:52kettenis has quit [Ping timeout: 480 seconds]