#
…

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:14jnlandscape15[m]: in which respect?
11:15malvo has joined #asahi
11:16landscape15[m]Both are bootloaders and a virtual EFI environment (a translator for ACPI).
11:18jni don't think there's any EFI or ACPI related code in m1n1, at this point
11:19jn(and as far as i understand it, this role would rather be filled by u-boot anyway)
11:21landscape15[m]Oh ok, so it is an hypervisor that interact with iboot i suppose.
11:22jnm1n1 interacts with iboot in the sense that it is launched by iboot
11:23jnit can either act as a hypervisor or pass full control to the next stage
11:23landscape15[m]So then it is independent from macOS?
11:23jn(so, it's not always a hypervisor)
11:24jnm1n1 is independent from macos in the sense that iboot->m1n1->linux is a perfectly valid and possible boot flow
11:24jnbut iboot->m1n1->macos works too, as far as i know
11:25landscape15[m]Ok it's very close to an embedded device tree
11:25jnwhat do you mean by that?
11:26landscape15[m]Most smartphones use a long device tree to boot Android.
11:27jn...and?
11:29landscape15[m]Nothing. I only think the boot process will be very slow initially.
11:30jnwhy do you think so?
11:45j_eylandscape15[m]: I think android booting is the slowest part of that
11:53alyssam1n1 is just a chainloader
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_eylandscape15[m]: it's a hypervisor too, but the normal use-case will be a chain loader
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:25j_eyindeed, would be a lot better if there was!
12:32kettenis_ is now known as kettenis
12:32svenespecially for certain parts like the entire graphics stack or the usb phy stuff
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:33svenkettenis: because it ignores the upper 32bit
12:33j_eysend an email to timcook@apple.com 'hello how do you detect that usb was disconnected properly?'
12:33j_eyis there any reason to use writel over writeq?
12:34svenhm. i never tried to use writel actually
12:35kettenisbut is it the mailbox hardware that ignores those bits or is it the rtkit firmware?
12:35sventhe mailbox hardware
12:35jmcneill12:41 PM < krbtgt> the hinterlands east of quebec
12:35jmcneillkrbtgt: hey me too! new brunswick here
12:35kettenishow did you figure that out?
12:35kettenis(just curious)
12:35svenyou can access both ends of the mailbox
12:35sventhe coprocessor sees the same mmio space
12:36svenso if i write to offset 0x60/0x68 i can read those messages from 0xa0/0xa8
12:36landscape15[m]j_ey: his mail is tcook@apple.com i think :)
12:36kettenisso if you write a nonzero value in the top bits, it reads back as zeroes?
12:36sven(if the coprocessor is dead, but that's easy to do)
12:36j_eylandscape15[m]: doesnt matter, it will go unreplied either way :p
12:37sventhe upper bits contain things like the read/write pointer of the HW fifo
12:37svenand some of them are just always zero
12:37svenand i've tried writing all ones there and it completely ignored that.
12:37j_eysven: I think you had those defines in the original driver? m1n1 still has them maybe
12:37j_eythe CNT/PTR things
12:37sveni think they are still in the current driver as well
12:37landscape15[m]j_ey: Yeah i'm quite sure ;)
12:38sveni copy/pasted them from marcan's original m1n1 tracer i think
12:38j_eyah yeah they are
12:38j_ey+#define APPLE_MBOX_MSG1_OUTCNT GENMASK(56, 52)
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:47ketteniscurrently the U-Boot mailbox driver handles the rtkit protocol as well
12:48kettenisso the NVMe node can simply reference the mailbox
12:49kettenisbut it looks as if your Linux mailbox driver only deals with the hardware mailbox
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:49alyssajmcneill: new brunswick! 😁
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:51alyssawith the DT describing only the physical hw mailbox
12:51sventhat's one alternative, yes
12:51sventhere is at least the SEP which will also use the mailbox HW but doesn't speak rtkit at all
12:51alyssaand then the NVMe driver (or whatever) calling into the RTKit library for pacakging
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:52svennot really sure which of those i prefer
12:52alyssasven: I really dislike that on principle -- device trees are supposed to model the hardware.
12:52alyssathe mbox is physical hardware, rtkit is just a protocol.
12:52sven"I expect you'd end up representing the low-level mbox HW and the remote
12:52svenfirmware as separate nodes in DT. There's certainly precedent for
12:52svenrepresenting firmware in DT as a separate node. Perhaps something like:"
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:53kettenisif that's the case, I think we need a separate node for the RTKit firmware
12:53svenyes. so if we have multiple nodes that need to talk to difference rtkit channels we need that node
12:54alyssaright, true
12:54alyssaSMC is the obvious block that needs that sort of stupid
12:54svenuh, no
12:54svenSMC is a single rtkit channel
12:54alyssaoh I misread that
12:54alyssaSMC needs other stupid, my bad πŸ˜‰
12:54svenyup :D
12:54j_eyalyssa: (btw there's asahi/mailbox/v2 now, so dont use whats on the list)
12:54alyssaj_ey: Ack
12:55svenwhich is what's on the list + alyssa's review comments :-)
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:55j_eyand jassi's!
12:55alyssaSMC is a single channel so irrelevant as discussed
12:55j_eyalyssa: youre so hip n cool with your πŸ’―
12:56alyssaj_ey: 😎
12:56svenj_ey: oh, yep. ofc!
12:56alyssasven: so ... which block are we worried about?
12:56alyssaSEP isn't even RTKit ... NVMe maybe?
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:56sveni dunno
12:56j_eyNVMe doesnt use the mailbox, just has to start it
12:57alyssasven: right... it seems like this is future proofing for the sake of future proofing, not because of a particular engineering objective ...
12:57alyssaadmittedly it's a thin tightrope since we don't have docs on current or future apples
12:58sveni don't even know about all blocks that _currently_ use rtkit
12:58kettenisyes, apple should hurry up with their next-gen hardware such that we can compare ;)
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:00sventhanks, that's good to know.
13:00sveni don't have a strong opinion regarding that separate rtkit node fwiw
13:00alyssakettenis: I'm waiting for M2 Macbooks to be released so I can get a used M1 air for cheap πŸ˜‹
13:01marcanseparate rtkit node is basically what macos does, fwiw
13:01marcanI don't have a strong opinion there, I guess it comes down to what that buys us
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:02svenhah :D
13:02kettenismarcan, the iop-nub,rtbuddy-v2 nodes?
13:03alyssaADT uses a lot of software nodes
13:03alyssagfx-mapper is such an ugly one..
13:03sventhe fake-iommu that really just calls back into the main kext? :D
13:04alyssadescribed in the ADT
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:24j_eykettenis: do you have any patches to m1n1? I have issues running m1n1+clang
13:24j_ey(with run_guest.py, I dont think youre using that..)
13:26yuyichao has joined #asahi
13:26jmcneillalyssa: yep! born here, moved away, and eventually returned
13:28kettenisj_ey: no (but I'm using gcc as a cross-compiler to build m1n1 and u-boot)
13:28j_eykettenis: oh
13:29ketteniswell, I have a diff to set the baudrate to 115200 but I doubt that will help you
13:30j_eyit seems to get into some kinda exception loop
13:31j_eyI'll probably just stick to gcc for now, at least my linux+clang works
13:59j_eywhat format should the initrd to u-boot be? I get 'Wrong Ramdisk Image Format' with a .cpio.gz
14:02kettenisthere should be no initrd
14:03j_eyI mean when running: booti kerneladdr initrd dtbaddr
14:03kettenisI don't know; I don't do Linux ;)
14:04kettenisI would expect u-boot to support most formats in common use
14:05j_eyme too, that's why I'm confused, maybe I'm doing something wrong!
14:06roxfanmaybe it wants raw uncompressed cpio? or u-boot image wrapped, who knows
14:06j_eyI can try this 'FIT' image thing maybe
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:10roxfanwell, it' just a little matter of programming :)
14:12kettenismy main goal with u-boot is to enable the UEFI interface
14:13j_eymakes sense
14:13kettenisso booting Linux directly from u-boot is (largely) untested
14:14kettenisI believe that with the UEFI boot path folks typically use grub and grub does the initrd loading
14:15roxfanmaybe adding tianocore to m1n1 is an easier task?
14:16kettenisalthough there is EFISTUB as well which allows you to directly load a kernel if I understand things correctly
14:16j_eykettenis: yup
14:18kettenisnot sure how initrd gets loaded in that scenario, although I have seen people mention that this relies on the EFI LoadFile2 protocol
14:21kettenisthat's a fairly recent thing in u-boot, but the code seems to be there in my fork
14:44j_eywell I finally got uboot with an initrd working, cool!
15:27svenhuh, does anyone know where the SMC firmware is stored? can't find it in the ipsw or in the preboot volume
16:08kettenismaybe it is in a ROM?
16:10svenhm, good point
16:12svencould also be some internal flash i guess if it has to come up before SecureROM
16:14zigmars has quit [Remote host closed the connection]
16:15alyssasven: i assume iBoot needs to talk to SMC very early on in the boot
16:19kettenisthe SMC might be what is starting the CPU that runs iBoot
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:10krbtgtjmcneill: oh hey, someone else from here
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
19:26jmcneillkrbtgt: you're in nb too? which part?
19:27jmcneillah never mind, answered by your hostname :)
19:28jmcneillalways surprised to see someone from around here on any irc server
19:46alyssa<--- boring ontarian
19:59alyssawe've got... uh... cheap beer!
20:00jmcneilli lived there when buck a beers were $1, and then the prices went up
20:10alyssa🀷
20:10alyssaI wouldn't know, my coding schedule relies on sobriety πŸ˜…
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:14alyssasorry, *Toronto, and nobody is from here. nobody πŸ˜‰
20:14jmcneillI have great memories of visiting Toronto when I was a kid!
20:14alyssa(also, errr, hello from m1 linux. It really bugs me how much more usable this is already than my Chromebook)
20:15alyssa(GNOME/X11/4K@60 in this case. Was testing HDMI hotplug... works fine now ☺)
20:15alyssaI wonder, do I dare experiment with type-C display out?
20:15jmcneillI'm hoping that driver gets ported to NetBSD some day :)
20:16alyssaMaybe downstream?
20:16j_eyalyssa: how 'quick' does it come up when you plug it in?
20:16alyssaj_ey: brb finding out :-p
20:16jmcneillIt will happen eventually, as long as the driver is not GPL only
20:16alyssaj_ey: about 3 seconds. but that could easily just be the monitor, nothing to do with the driver stack
20:17alyssa(switching from 1080p to 4K is also a few seconds of black...)
20:17j_eyaw, i was hoping it might just be magical and be instant :P but 3s is fine anyway
20:18alyssawhere does this "m1 display stack is magic" meme even come form
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:21alyssait's cute but doesn't have much to do with the M1 πŸ‘…
20:21alyssa* πŸ˜‹
20:23j_eyive never changed resolution or used a 2nd screen with my m1 D:
20:29krbtgtalyssa: i've seen them react quickly to external monitors on mac os
20:29krbtgtwhich is where the meme comes from
20:30alyssakrbtgt: I see.. maybe I have bad luck with external monitors then
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:48* alyssaplays with dcpext
20:49alyssait appears that on the mini, dcp = hdmi and dcpext = type-c ports
20:49alyssaOf course that raises a question already -- there are two type-c ports and only one dcpext
20:49alyssahow is that assigned?
20:49alyssamy gut says ATCPHY shenanigans
20:49alyssasven: officially not my problem anymore πŸ˜‰
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:03alyssaIf I understand the cable topology correctly, it's not
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:05alyssathat confirms my understanding of the topology. ok, good, not totally losing my mind here :)
21:09alyssato recap:
21:09alyssamini: dcp = HDMI port
21:09alyssamacbook: dcp = internal panel
21:09alyssaall: dcpext = type-c port, which one is assigned to which is configurable
21:10alyssathis has some minor implications for the driver.
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?
21:12alyssadottedmag: I think so
22:05alyssabuilding with CONFIG_SOUND shouldn't bloat my kernel too much ... I hope
22:08rossy has quit [Ping timeout: 480 seconds]
22:08rossy has joined #asahi
22:12alyssaeh, worth it for working headphones+mic over USb
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:36alyssaI've been on holiday from my day job for a few weeks πŸ˜…
22:37j_eymarcan also laid the groundwork in m1n1, and sven with rtkit ;)
22:38alyssa98% of the DCP r/e needed marcan finished by aug 1
22:38alyssaand yeah this is running on top of a giant pile of sven code
22:38alyssaso then I get time off and the stars align for display stack to come together
22:39brentr123[m]Yeah it’s my freshman year in college so I gotta take care of school work and shit
22:39alyssafirst year... ahh... 🐴
22:41brentr123[m]What the fuck is that horse emote supposed to mean
22:41alyssaπŸ˜†
22:41alyssaI dunno, first year of uni was wild for me
22:42alyssa...admittedly due to a pandemic hitting 3/4 through...
22:44j_eyfirst year of uni was zzzZZzz
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:45j_eydunno how he finds the time after all the bobsledding practise
22:46alyssaj_ey: yeah idk either
22:46alyssamad respect tho, work-life balance
22:46j_eynow that you have sound, seems pretty close to the Sep 1st goal!
22:46alyssaj_ey: "sound"
22:47alyssaactually, well, the rk3399 sound drivers have been totally broken for a while so I use that adapter there too
22:47j_eyalyssa: you can listen to wicked, what else is needed?
22:47alyssaso ... m1 sound is now at parity with my rk3399 machines? :-p
22:48alyssaj_ey: idk, Rent?
22:48j_eynever seen wicked or rent, dont hate me
23:01alyssai'm starting to feel ok about the dcp driver
23:01alyssastill aesthetically a mess but it's not fundamentally broken anymore :-p
23:03aleasto has quit [Quit: Konversation terminated!]
23:52kettenis has quit [Ping timeout: 480 seconds]
…