2026-06-24
00:08tjemke778 has joined #asahi-dev
00:11aites[m]fl0_id_afk: Yeah it's connected to the internet so I think that shouldn't be a blocker ??? 😭
00:12aites[m]I at some point thought the assets might've been blocked by my university's firewall? Tried using my phone's mobile data through hotspot and that didn't work either
00:16tjemke77 has quit [Ping timeout: 480 seconds]
00:16tjemke778 is now known as tjemke77
00:39hdbngr has joined #asahi-dev
00:47hdbngr has quit [Ping timeout: 480 seconds]
00:57aites[m]And I have also now tried the mist installer but that didn't work either so I think it must be an issue with signing ? Where does it list whether or not a version is signed?
01:15pb17 has quit [Ping timeout: 480 seconds]
01:17pb17 has joined #asahi-dev
01:33StanfordAppliedCyber[m]debugging the sep has to be the worst part of this hypervisor, when it doesn't work we have no way to tell why it doesn't work
01:33StanfordAppliedCyber[m]apparently i have a pretty big regression somewhere because i can't even get to windowserver anymore, can't access the encrypted userdata
01:36hdbngr has joined #asahi-dev
01:37StanfordAppliedCyber[m]and for some reason reverting to a known good commit still has the error?
01:37StanfordAppliedCyber[m]these machines, sigh
01:43Cardpira- has joined #asahi-dev
01:45hdbngr has quit [Ping timeout: 480 seconds]
01:48Card has quit [Ping timeout: 480 seconds]
01:52aites[m]<aites[m]> "And I have also now tried the..." <- hm yea reading the install error logs it claims I have no space but this is not true I have a lot of space
01:58StanfordAppliedCyber[m]check if crashlogs are filling it up
01:58StanfordAppliedCyber[m]i burned through 200gb of space because coredumps + crashlogs used all of it
01:58msimonelli has quit [Quit: we out (of) here]
02:00yurix has quit [Remote host closed the connection]
02:00yurix has joined #asahi-dev
02:03StanfordAppliedCyber[m]well the solution is just to delete them
02:03StanfordAppliedCyber[m]uhhhhhhhhhhhhhhhhhhhhhhhh check diskutil?
02:03StanfordAppliedCyber[m]this shouldn't be hard to figure out
02:03StanfordAppliedCyber[m]worst case flash the real kernelcache, boot into real macos, then just look at the disk
02:05* aites[m]uploaded an image: (68KiB) < https://matrix.org/oftc/media/v1/media/download/Ad6BCjMUBLOmy0lahbFVMkrRfK2Dx6m2vzmExNzPxJGggotW5Zu0vklDQlS33uFE9OEFXW5ioTBGEmCfbidVqDNCefP3l1VwAG1vemlsbGEub3JnLzA0NTE2MjllMWIyYWE2YzljMGZhNDI2OTYwYTBlMTQ2M2VkNjI5YjAyMDY5NjAyODc1OTQzNjgyMDQ4 >
02:07integralpilot has joined #asahi-dev
02:09integralpilotjannau: looking at the logs, i think we (me, you, sven) decided to do it as a mailbox on 2026-01-25
02:10integralpilotbut if you think it would be better in another subsystem happy to do that, i don't really mind, i think it's a bit of a weird thing and could fit in many places
02:10integralpilotbtw, thank you for your feedback, i'll get around to addressing that soon! :)
02:19msimonelli has joined #asahi-dev
02:24tobhe_ has joined #asahi-dev
02:28StanfordAppliedCyber[m]also i'm looking at the possibility of virtualizing exclaves, they don't contain, from a very stupid python script, anything fun, ie, apple custom instructions, weird sysreg accesses, etc
02:28StanfordAppliedCyber[m]in fact it looks like a very normal arm kernel/user space despite running in gl1/0
02:31tobhe has quit [Ping timeout: 480 seconds]
02:34StanfordAppliedCyber[m](this is in contrast to sptm btw, which has lots of both)
03:02tjemke772 has joined #asahi-dev
03:06lacamar has joined #asahi-dev
03:08tjemke77 has quit [Ping timeout: 480 seconds]
03:08tjemke772 is now known as tjemke77
03:10averne_ has joined #asahi-dev
03:11pb17 has quit [Ping timeout: 480 seconds]
03:11lacamar_ has quit [Ping timeout: 480 seconds]
03:15averne has quit [Ping timeout: 480 seconds]
03:20pb17 has joined #asahi-dev
03:45hdbngr has joined #asahi-dev
03:53hdbngr has quit [Ping timeout: 480 seconds]
04:01Card has joined #asahi-dev
04:06Cardpira- has quit [Ping timeout: 480 seconds]
04:07integralpilot has quit [Quit: integralpilot]
04:09Cardpira- has joined #asahi-dev
04:12Card has quit [Ping timeout: 480 seconds]
04:29eluks has quit [Remote host closed the connection]
04:30eluks has joined #asahi-dev
04:36gargantua has joined #asahi-dev
04:41hdbngr has joined #asahi-dev
04:44integralpilot has joined #asahi-dev
04:50integralpilotjust pushed new version of MTP addressing the feedback, thanks again for it :)
04:52hdbngr has quit [Ping timeout: 480 seconds]
04:58hdbngr has joined #asahi-dev
05:10jannauintegralpilot: I don't think there is kernel API which would be a better fit. mailbox isn't too bad for HID. only annoyance is the missing control of the incomming message size
05:24nela has quit [Ping timeout: 480 seconds]
05:25nela has joined #asahi-dev
05:26integralpiloti think with the fixes i just worked on, it should be okay at dealing with lots of tiny uart messages. if it coalesces writes into chunks that will be fine, but if every byte is a mailbox message that wouldn't be ideal
05:34integralpilotmy thoughts are that for now, where HID is the only one we really know fully about and have working, its okay to get it working through the mailbox system. when we get around to uart, we can try out the mailbox system for that, but if it doesn't work, then we can look into alternatives (but, i think it should work for uart with the TX workqueue gone and no more per-RX kmalloc etc. which I've done)
05:34integralpilotand thank you for those ideas on how to improve it so uart would (in future) work better without as much modifications!
05:37JamesCalligeros[m]yuka wanted to work on a serial driver for dockchannel like nowish
05:38JamesCalligeros[m]if mailbox isnt gonna fly we can do what we did for rtk mailbox and just make it a not-mailbox mailbox driver :P
05:44integralpiloti think mailbox *should* be fine now for serial too, but not 100% sure
05:47integralpilotoh wait * isn't italtics, its _ - i forgot sorry!
05:52JamesCalligeros[m]I dont think the markdown stuff works from the irc bridge at all lmao
05:55integralpilotoh doesnt matter then lol!
05:55integralpiloti still keep thinking about it and i can't decide if mailbox is right
05:56integralpilotif we do upstream HID now with mailbox, and then it doesn't work for serial with whatever reason, when serial is downstream we can kinda just do whatever. but if serial wanted to go upstream, would they accept a) moving the already existing driver or b) having a seperate lightweight tty driver for dockchannel serial uses vs mailbox for other stuff
05:57jannaudockchannel-uart works in m1n1 (using kisd). The main concern I have for uart is the mailbox tx queue length of 20 and irqs for every submitted byte
05:59croissant` has quit []
05:59jannauwe want dockchannel-uart upstream. the fallback solution for uart would be to use the dockchannel fifos directly
05:59croissant has joined #asahi-dev
06:00Pokemod977362084712818330 has quit []
06:01integralpilotwould it be fine upstream to have the DockChannel mailbox driver for HID, and then a seperate TTY/serial driver that will access hardware regs directly for serial?
06:01JamesCalligeros[m]They dont need to share infrastructure, it would just be Proper if they do. Upstream might grumble about it though.
06:02integralpiloti guess the other option is we make a DockChannel TTY/UART controller driver, and then the HID driver consumes it through serdev
06:02integralpilotthat might actually be the neatest solution but maybe i'm missing something
06:03integralpilotthough that would make things a lot more complex
06:04integralpilotso i guess we got 2 options:
06:04integralpilot1. mailbox for HID. for serial: either coalesced mailbox, or just access raw hardware regs directly in the TTY driver (upstream might not like, but if justifiable for speed might be ok)
06:05integralpilot2. have a TTY driver for DockChannel. and then the HID driver accesses that through serdev. more complex though.
06:05integralpiloti am honestly fine with either but probably leaning towards #1 just as its cleaner and gives us more options later when we do serial, hb you guys?
06:07JamesCalligeros[m]Upstream will likely be fine with it if there’s a decent justification. Having to handle an irq on every single byte if we use mailbox is a fine justification.
06:09svencan we just try UART and see what happens? we have kisd and all the infrastructure now and a simple UART driver that uses mbox shouldn’t be hard
06:10nela has quit [Quit: Ping timeout (120 seconds)]
06:11nela has joined #asahi-dev
06:11Pokemod977362084712818330 has joined #asahi-dev
06:12integralpiloti'll try it out later tonight
06:13gargantua has quit [Ping timeout: 480 seconds]
06:13nela has quit []
06:14nela has joined #asahi-dev
06:20JamesCalligeros[m]I need to have another crack at colour pipelines. I think iosurface might have space for a per-surface clut but im not sure
06:20JamesCalligeros[m]Either way we need to hook up the eotfs
06:21JamesCalligeros[m]And then colourspaces when those land in the api
06:22apc has quit [Quit: The Lounge - https://thelounge.chat]
06:22apc has joined #asahi-dev
06:24nela has quit [Quit: Ping timeout (120 seconds)]
06:24sofus has joined #asahi-dev
06:25apc has quit []
06:25apc has joined #asahi-dev
06:25hdbngr has quit [Ping timeout: 480 seconds]
06:26hdbngr has joined #asahi-dev
06:32mattia013 has joined #asahi-dev
06:35apc has quit [Quit: The Lounge - https://thelounge.chat]
06:35apc has joined #asahi-dev
06:35hdbngr has quit [Ping timeout: 480 seconds]
06:48hdbngr has joined #asahi-dev
06:59dextaa69 has quit []
07:00dextaa69 has joined #asahi-dev
07:08hdbngr has quit [Ping timeout: 480 seconds]
07:28Cardpiraya has joined #asahi-dev
07:35Cardpira- has quit [Ping timeout: 480 seconds]
07:43chadmed has quit [Quit: Konversation terminated!]
07:43chadmed has joined #asahi-dev
07:45chadmed has quit [Read error: Connection reset by peer]
07:45chadmed_ has joined #asahi-dev
07:49mripard has joined #asahi-dev
07:53yukaI then got stuck on a bunch of design decisions like is each channel its own device tree node
07:53chadmed_sofus: re the quirks system, given the combinatorics involved here and the pathways in which we need to use them, it may be better to write hw-specific versions of the functions and specify which one each avd variant must use in its match data or an ops struct
07:53chadmed_so instead of having to evaluate each quirk every time in the hot path, you just do something like avd->hw->push(...)
07:57integralpilotyuka: are you sure you want a uart driver? there's no baud/termios/modem state etc. for dockchannel (at least to my knowledge), which i think uart_port needs
07:57integralpilota plain TTY driver is probably better
07:58chadmed_ is now known as chadmed
07:59integralpilotyes, i believe so
08:00yukaI think we want the line discipline (echoing back characters etc) in this case and we can ignore the baudrate change things
08:02yukaso I interpret this as two sides, the tty is where you are on the "typewriter" side (where the user is sitting in front of), and the uart side is on the machine the "typewriter" is connected to
08:02yukaSo in our case the tty part is implemented in kisd in userspace, and the other side needs to be a uart driver
08:05integralpiloti think with uart drivers, implementing (which you would have to fake) baud, line control, a `struct uart_port` is required, not optional (unlike tty) and you would have to implement a lot of meaningless functions like set_termios, tx_empty, get_mctrl etc.
08:06integralpiloti might be remembering wrong though!
08:06integralpilotand i think faking etc. is not really ideal for upstream
08:07integralpilotand with tty the faking and implementing meaningless functions isnt needed
08:10integralpilotis that not ideal?
08:11rosalyntg has quit [Ping timeout: 480 seconds]
08:16sofuschadmed: makes sense thanks, although im still playing with the idea of generating/writing instructions on the cm3
08:18rosalyntg has joined #asahi-dev
08:20chaos_princessnow you are thinking like a vendor
08:26JamesCalligeros[m]Ideally the cm3 runs fw that exposes a unified interface to linux (or at least an interface for each codec) and we deal with instruction dispatch to the ffu on the cm3 i agree
08:26integralpilotokay i am testing my dockchannel tty driver (that uses the mailbox) now. will report back how it goes
08:26integralpilotjust finished the first draft
08:26JamesCalligeros[m]And id still spin our own because pulling apple’s out of the kext will suck
08:26integralpilot*dockchannel-uart tty driver
08:27integralpilot has quit [Quit: integralpilot]
08:27chaos_princesssofus: just a joke on how many vendors like to put as much as possible into the firmware and not the driver
08:29chaos_princessneutral
08:32chaos_princessthat is one of the reasons vendors like to do it
08:34WindowPain has quit [Quit: ( ´・・)ノ]
08:36WindowPain has joined #asahi-dev
08:37chadmedyeah, and we're not going to have a 3-line driver with static void decode_frame(void *enormous_command_buffer) a la vendor drivers
08:38chadmedi mean tbh i think dealing with the quirks in the driver _is_ fine in theory and wont get us NACKed or anything, but if we get 7 more AVD variants for 3 more socs.... it's gonna be a bit silly
08:40integralpilot has joined #asahi-dev
08:40chaos_princessthe ultimate vendor driver consists of a multi-mb firmware blob, multi-mb userspace blob, and a kernel driver with functions to map/unmap memory and exec a command stream
08:40integralpilotSobek[m]: its an apple custom FIFO
08:41integralpiloton M2+ it is used to talk to the inbuilt keyboard and trackpad on macbooks
08:41integralpilotit is also used for a weird serial protocol we call "dockchannel uart", though its not really full uart
08:51sofusdid anyone test avd on t8103? Im kinda hoping it has the same issue as t6000 but is more verbose about it
08:55integralpilot has quit [Quit: integralpilot]
09:08r0ni has joined #asahi-dev
09:26msimonelli has quit [Quit: we out (of) here]
09:28chadmedok so while i wait for a kernel build on t8103, on t8112 `mpv ~/Videos/E26.mp4` results in ~1.4 W above background (1280x720 dbza ep 26 from archive dot org)
09:29chadmed`mpv -hwdec=v4l2request_copy -vo=dmabuf-wayland ~/Videos/E26.mp4` results in ~700 mW above background
09:29chaos_princessmind doing a 4k yt video?
09:35chaos_princessare you using yt-dlp
09:36chaos_princessuse the web_safari client
09:47chadmedmaybe interchange buffers will help a bit, but it _should_ be zerocopy with `-hwdec=v4l2-request -vo=dmabuf-wayland`
09:47msimonelli has joined #asahi-dev
09:53chadmedi would have liked to test direct scanout but its 8pm, im not hacking janky colourop support into dcp now :P
09:57mattia013 has quit [Remote host closed the connection]
09:58JamesCalligeros[m]No more dcp work until the surface caps stuff lands anyway, i have too many dcp-related m1n1 and kernel branches
10:35donaldh has joined #asahi-dev
10:53integralpilot has joined #asahi-dev
10:56integralpilotsven: seems mailbox works fine for dockchannel-uart, at least with the quick test i just did
10:57integralpilotso looks like mailbox for HID is perfect and fine then
10:57integralpilotyuka: don't really need anything for HID, its not really blocked on -uart anymore! thank you though :)
11:00integralpilotHID looking good then, cause mailbox is fine now, so i just think waiting on if there's anymore feedback from jannau and then sven's feedback on the weekend (thank you) and can maybe be sent upstream sometime next week?
11:01jannauchadmed: I'll merge the dcp surface caps for v7.1 (curently blocked on rust changes breaking our drivers)
11:02jannausofus: have you seen https://www.collabora.com/news-and-blog/news-and-events/rk3588-and-rk3576-video-decoders-support-merged-in-the-upstream-linux-kernel.html ?
11:02integralpilotsven: code still in the same place, i forced pushed the updates to that branch. https://github.com/IntegralPilot/linux2/pull/1
11:02integralpilotthanks again!
11:05jannauintegralpilot: I plan to send more M3 dts / dt-binding changes as soon as v7.2-rc1 is tagged.
11:05integralpilotyuka: it was just a really rough tty driver and i only tested it a bit (just to confirm the concept of loading from mailbox was OK), but if you'd like to look remind me tomorrow, i shut off my laptop for the night sorry but i can push then
11:07integralpilotoh interesting, cool work!
11:07flokliI successfully booted it into this quite minimal kernel which previously did crash pretty reliably
11:09integralpilotawesome!! really great work guys
11:10integralpilotsuper cool m4 is being done now too
11:12jannauchadmed: there's https://gitlab.freedesktop.org/sree/mesa/-/commit/5955e6eb0a03fdd0804b9b3ecf98d8681187c189 as well if can ignore the slop (I haven't really looked at it)
11:13svenwould move the enum to a header and add yield like will suggested, but looks good otherwise
11:17JamesCalligeros[m]Oh my 66kloc of slop
11:20kitlith has quit [Read error: Connection reset by peer]
11:20kitlith has joined #asahi-dev
11:21flokliyuka: so the less minimal kernel config still crashes somewhat reliably without maxcpus=1. Maybe there's some other place using wfi, which we didn't catch with this patch?
11:23yukaI don't think the other crashes are immediately related to wfi, they are just dependent on some race condition (some code running on the secondary core?)
11:28floklisorry, was missing the 'unable to handle kernel write' line. more logs of another boot: https://paste.linuxlounge.net/PMTU4BIEOV4UPN55VPS2V6OSBY
11:31flokliso it correlates with the number of cores that are running. i wasn't able to successfully boot at all with all 12 cores. but i was able to boot up with maxcpus=2 just now
11:33yukawhich either is the piece of code which crashes, or a piece of code which runs on the core before and messes things up
11:34flokliyeah, so the higher I set maxcpus=, the less likely the chance for the bootup to succeed. maxcpus=4 is a bit hit and miss, any more cores than that I wasn't able to boot up the kernel without oopsing
11:37flokliLarstiQ: i'd need to probably do a lot more reboots to give you a somewhat confident answer to that ;-)
11:39LarstiQflokli: heh, just musing about which thing makes it work after booting and what are the bits that might get scheduled on another core before that
11:41integralpilot has quit [Quit: integralpilot]
11:42flokliBut this machine has 12 cores, so fairly high chance it reproduces whatever race there is easily without restricting.
11:57sofusi tried doing the same as https://lore.kernel.org/all/20250508-rkvdec-iommu-reset-v1-1-c46b6efa6e9b@collabora.com/
12:01enverbalalic has joined #asahi-dev
12:02enverbalalicI have a t6041 that i want to start poking around, who's repo / branch is the most up to date for m4 stuff right now ? yuka ?
12:03yukajust m1n1 main and linux 7.1 or linux-next should be a good starting point to test your own device tree if you want to write one
12:07jannausofus: might be an apple-dart quirk. if you push your branch I can take a look. I would start with tracing dart-avd and HVLOG prints around the domain switching
12:38flokliConsidering there's also t602x-common.dtsi, that's how it might end up getting upstreamed anyways
12:39enverbalalicthat would be great if you can
13:09mattia013 has joined #asahi-dev
13:20enverbalalic has quit [Ping timeout: 480 seconds]
13:28enverbalalic has joined #asahi-dev
13:43enverbalalic has quit [Ping timeout: 480 seconds]
13:51enverbalalic has joined #asahi-dev
13:53jannausofus: messages with "HVLOG:" in the HV uart are passed through to the HV log. see 093f59ea ("hv_vuart: Pass through "HVLOG: ..." messages to the main console")
14:13enverbalalic has quit [Ping timeout: 480 seconds]
14:15enverbalalic has joined #asahi-dev
14:19enverbalalicyes i'm on 26.6b2, out of curiosity, did anyone try 27.0b2 ?
14:19enverbalaliclet me know if it's worth it :D
14:20enverbalalici can try later as well
14:24enverbalalicyuka: yes, i ran the experiment from mischa85's t6041 m1n1 branch, fiq_ena_probe.py, it was writable
14:25enverbalalicalso for WFI, boot core retains state
14:32yukafyi the fiq_ena_probe.py smells like partially llm written, based on the assumption that no one would write 50loc for something that is a single liner in the shell
14:37enverbalaliccould be :/ i just found something to run while i was testing my setup, i'm just getting into hacking on these and saw he has a branch for t6041 in irc logs
14:43enverbalalichow necessary is a hardware serial like central scrutinizer ? I'm guessing since we're already booting into m1n1 not that much
15:22enverbalalic has quit [Ping timeout: 480 seconds]
15:29enverbalalic has joined #asahi-dev
15:36pb17 has quit [Remote host closed the connection]
15:36pb17 has joined #asahi-dev
15:37svenso do we still have any machine where SYS_IMP_APL_VM_TMR_FIQ_ENA_EL2 isn't writable with some beta?
15:38chaos_princesst6040? there was a thing where it is different between 0 and 1. And idk if anyone tested m5
15:41enverbalalic has quit [Ping timeout: 480 seconds]
15:49enverbalalic has joined #asahi-dev
15:54floklijust tested `msr((3, 5, 15, 1, 3), mrs((3, 5, 15, 1, 3)))` on t6040 with latest beta, still broken :-/
15:57enverbalalic has quit [Ping timeout: 480 seconds]
16:05enverbalalic has joined #asahi-dev
16:16enverbalalic has quit [Remote host closed the connection]
16:16enverbalalic has joined #asahi-dev
16:22enverbalalicis serial over an m1 machine with macvdmtool working or is hardware truly necessary. I tried it with an m2 air that i have and i can reboot the m4, but either the serial output isn't working or i'm doing something wrong
16:24lowspoly[m] has joined #asahi-dev
16:26enverbalalici'm trying to figure out if i can use another machine and not have to order 5 PCB's of central scrutinizer from jlcpcb for serial output. the m2 air is on 26.5.1, the m4 i have running m1n1, is iboot/xnu serial possible via this ?
16:27enverbalalici'm really just looking at this page here https://asahilinux.org/docs/hw/soc/serial-debug/, none of the usb-c breakouts for the arduino way are obtainable in bosnia so i'm trying to see if i can do it without extra hardware
16:28enverbalalics/obtainable/easily obtainable/
16:28enverbalalicok, should work is good enough, i'll see what i'm doing wrong
16:28enverbalalici'm also using a tb4 cable so that shouldn't be an issue either
16:30fl0_id_afkenverbalalic depending on where you are, I could send you mine, don't need it any time soon
16:30fl0_id_afk is now known as fl0_id_
16:31Ami[m]Apologies for interrupting y’all - but are there any low hanging fruit issues I can work on with M3 Pro to contribute to that aspect of the project ? And if so - where can I view them? Thanks :)
16:31enverbalalic has quit [Remote host closed the connection]
16:33enverbalalic has joined #asahi-dev
16:40enverbalalicsven: it's very weird, just doing reboot serial will say vdm failed when putting target into serial. (0x05ac80d2)
16:41enverbalalicif i attach picocom to tty.debug-console first, then do it, it will be fine 9 out of 10 times (no error), but it will not show anything
16:47rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
16:47Guest11756 has quit [Quit: Bridge terminating on SIGTERM]
16:51pb17 has quit [Ping timeout: 480 seconds]
16:51rhysmdnz has joined #asahi-dev
16:52Guest11915 has joined #asahi-dev
17:00enverbalalicit's the tb4 cable i use for my display, i know it works and it's a full fat cable
17:00yukathe only way to know for sure that this cable has all the pins connected is seeing the serial output ;)
17:04enverbalalicmacvdmtool will put it into dfu no problem, i see it in apple configurator in dfu mode, so ports are fine, macvdmtool reboot also works, debugusb works, just the serial :'(
17:05yukaeverything you described works with any normal usb3 capable cable, only serial requires a full-fat cable
17:05enverbalalicokay let me dig out more cables
17:05enverbalalici'll be very surprised if this one is not a full-fat one
17:11svenbut if your display works with that cable i'm pretty sure it will have SBU connected because the DP AUX channels is on those lines
17:11enverbalalicyeah that's what i'm thinking as well... and it's not like i'm running a 1080p screen from it, it works for 4k@144
17:18r0ni has quit [Ping timeout: 480 seconds]
17:31gargantua has joined #asahi-dev
17:31WindowPain has quit [Read error: Connection reset by peer]
17:32WindowPain has joined #asahi-dev
17:35pb17 has joined #asahi-dev
17:42enverbalalicok... i tried 2 more thick cables, still no serial. I'm inclined to say that something software-wise is not working here with the combo i'm using. I'm tempted to try to update the m2 to 26.6b2 as well
17:43enverbalalicwould this give iboot output normally, or is this just m1n1/xnu/linux serial ?
17:44xarkes has quit [Remote host closed the connection]
17:44xarkes has joined #asahi-dev
17:45hdbngr has joined #asahi-dev
17:47hardy94 has quit [Remote host closed the connection]
17:56sofus has quit [Quit: Lost terminal]
18:06hdbngr has quit [Ping timeout: 480 seconds]
18:07hdbngr has joined #asahi-dev
18:15sofus has joined #asahi-dev
18:16hdbngr has quit [Ping timeout: 480 seconds]
18:17hdbngr has joined #asahi-dev
18:25sofus has quit [Quit: Lost terminal]
18:39mini has quit [Quit: The Lounge - https://thelounge.chat]
18:39mini has joined #asahi-dev
18:40hdbngr has quit [Ping timeout: 480 seconds]
18:46dextaa69 has quit [Ping timeout: 480 seconds]
18:53sofus has joined #asahi-dev
18:54enverbalalic has quit [Quit: enverbalalic]
18:54hdbngr has joined #asahi-dev
18:56enverbalalic has joined #asahi-dev
19:32os has quit [Quit: Ping timeout (120 seconds)]
19:32os has joined #asahi-dev
19:32yukaOkay, I can actually reproduce the M4 crashes deterministically using jannau's switch_boot_cpu PR
20:02svenwe should see the difference in chickens then, shouldn't we? we can still read sysregs, we just can't write them
20:02svenif we complain about this we better be sure there's a difference or apple will just ignore us i guess
20:04hdbngr has quit [Read error: Connection reset by peer]
20:07hdbngr has joined #asahi-dev
20:07yukaIf this behavior is indeed directly caused (or prevented) by chickens, we can compare the following:
20:07yukaGood: A18 Pro boot core / A18 Pro E-Core secondary / A18 Pro P-Core secondary / M4 Boot Core
20:09svenjust sounds like something where creating a simple reproducer is going to be rather annoying :D
20:10r0ni has joined #asahi-dev
20:14gargantua has quit [Ping timeout: 480 seconds]
20:26sofus has quit [Read error: Connection reset by peer]
21:18jannauchaos_princess: do you have an idea idea how pmp works on multi-die? Not having to override power-domains for Ultra devices is a reason to look into it
21:19chaos_princessno idea, i don't have any multi-die devices
21:20chaos_princessbut there is something weird about avd specifically, as there is a avd-specific pmp thing
21:32enverbalalic has quit [Ping timeout: 480 seconds]
21:49yukaI can run this, it returns, and as expected it's totally useless (it sets up the pagetables but does not do anything with them).
21:50yukaI played around with the values used for SCTLR_EL1, MAIR_EL1, TCR_EL1, tried the same values used by m1n1 mmu init, and it still doesn't return
21:53yukaI tried all bits of SCTLR_EL1 individually to see which of them broke it, and arrived at SCTLR_M
21:54yukaSadly, I don't get any exception handler output even though I commented out the VBAR_EL2 write
22:18enverbalalic has joined #asahi-dev
22:21hdbngr has quit [Ping timeout: 480 seconds]
22:24txmxn[m] has joined #asahi-dev
22:28pb17 has quit [Ping timeout: 480 seconds]
22:30hdbngr has joined #asahi-dev
22:34gargantua has joined #asahi-dev
22:36enverbalalic has quit [Ping timeout: 480 seconds]
22:36txmxn[m]Hello everyone, I'm currently working on the Keyboard layout cleanup task from the Help wanted section. I use a Macbook Pro M4 Max with german ISO-Layout and made a table for every Shift, Option, Option/Shift combination, then compared it to de(mac). There are many differences on Level 3 and 4 (looks like de(mac) mostly has the normal PC-German mappings, not the macOS ones) which made me curious. Is it that way on purpose because some of
22:36txmxn[m]the symbols are just not useful and were left out intentionally before? I'm trying to mirror EXACTLY every combination of MacOS to de(mac) but is that even the goal? Or would that better be a new variant instead of changing de(mac)? It would be my first contribution ever and i thought maybe thats a good task to start with. So I'm a bit worried I'm missing something and would rather ask first than do something wrong. Thanks for any answers
22:39hdbngr has quit [Ping timeout: 480 seconds]
22:43pb17 has joined #asahi-dev
22:45fl0_id_ is now known as fl0_id_afk
22:57Deewiant_ has joined #asahi-dev
23:01Deewiant has quit [Read error: Connection reset by peer]
23:13mattia013 has quit [Remote host closed the connection]
23:14enverbalalic has joined #asahi-dev
23:19milek7 has joined #asahi-dev
23:20milek7 has quit []
23:22milek7 has joined #asahi-dev
23:22milek7 has quit []
23:23milek7 has joined #asahi-dev
23:27enverbalalic has quit [Ping timeout: 480 seconds]
23:36enverbalalic has joined #asahi-dev
23:50enverbalalicokay so... on t6041 with the linux branch for j773s that flokli posted today, his dtb for j773s it boots to a shell ?
23:50enverbalalici thought it crashes early, or is that after enabling more things
23:53enverbalalici used maxcpus=1, config from the linux-asahi pkgbuild
23:53hdbngr has joined #asahi-dev
23:54enverbalalicyeah, so that's the catch then
23:56enverbalalicgot it, thanks! time to figure out something to get a serial console