#
…

2026-01-03

00:01jannaupushed. I've not taken some of the dcp_surface setting changes (mostly because I didn't spend time on it) That might explain the broken alpha for AR30
00:04jannauI skipped the swap_id as sequence number (probably fine), the vblank workqueue removal (might introduce deadlocks, taking locks from DCP callbacks is dangerous) and I'm not using surface 0 due to its limitations
00:07hdbngr has quit [Ping timeout: 480 seconds]
00:07chadmedfair enough. i dont think vrr will ever work if we keep delivering fake/mistimed vblank events on "timed out" commits though
00:08chadmeddoesnt really matter right now though since i havent found the bits to flip to make dcp actually drive vrr anyawy
00:08chadmedsetting a "vrr" timing mode is not enough
00:09chadmedsurface 0 should be safe if we keep it as an immutable primary, at least for kwin
00:10jannauthere is a vrr related message in dcp's sys/rtkit log
00:11chadmedin such cases kwin will only ever use it as an underlay and put the primary scene on top of it, so it _shouldnt_ matter what shows through underneath the primary scene
00:11chadmedi will wait until kwin is fixed so we can test that theory though of course
00:12chadmedand im hoping that if we get the atomic sequencing more correct we can dispense with the vake vblank events entirely but given how long a swap takes im not particularly hopeful
00:12jannauthose timed out vblank events should not happen. that handling is only there as safety since some userspace (maybe X11) locked up without
00:12chadmedand my understanding of ams may be entirely wrong but i think tihs might be necessary for async/nonblocking commits anyway
00:13chadmedi dont particularly care about native x11 anymore if its going to box us into a corner on properly driving this thing
00:14jannauI think surface 0 posed some limitations on pixel formats / color spaces. possibly even on other surfaces
00:14chadmedi havent noticed anything like that
00:15hdbngr has joined #asahi-dev
00:15chadmedmy scene last night was ar30 srgb on 0, ar24 srgb on 1, nv12 bt.709 on 3 and it all worked correctly
00:15chadmed(apart from kwin trying to put 1 and 3 on the same plane)
00:18pb17 has joined #asahi-dev
00:19jannaugood night. I hope it's not too much trouble to rebase onto the new branch
00:20chadmedgoodnight, nah already most of the way through :)
00:22mixi has quit [Ping timeout: 480 seconds]
00:23hdbngr has quit [Ping timeout: 480 seconds]
00:27maor26 has quit [Ping timeout: 480 seconds]
00:28fl0_id_ has quit [Remote host closed the connection]
00:31hdbngr has joined #asahi-dev
00:33mixi has joined #asahi-dev
00:40hdbngr has quit [Ping timeout: 480 seconds]
00:48hdbngr has joined #asahi-dev
00:56hdbngr has quit [Ping timeout: 480 seconds]
00:57hdbngr has joined #asahi-dev
00:58alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
01:05hdbngr has quit [Ping timeout: 480 seconds]
01:13hdbngr has joined #asahi-dev
01:28hdbngr has quit [Ping timeout: 480 seconds]
01:30hdbngr has joined #asahi-dev
01:37alicela1n has joined #asahi-dev
01:39hdbngr has quit [Ping timeout: 480 seconds]
01:47hdbngr has joined #asahi-dev
01:55hdbngr has quit [Ping timeout: 480 seconds]
01:59chadmednull pointer deref in asahi driver on asahi-wip
02:00alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
02:03hdbngr has joined #asahi-dev
02:12hdbngr has quit [Ping timeout: 480 seconds]
02:20hdbngr has joined #asahi-dev
02:29hdbngr has quit [Ping timeout: 480 seconds]
02:34Calandracas has joined #asahi-dev
02:36Calandracas_ has quit [Read error: Connection reset by peer]
02:37alicela1n has joined #asahi-dev
02:37hdbngr has joined #asahi-dev
02:46hdbngr has quit [Ping timeout: 480 seconds]
02:54hdbngr has joined #asahi-dev
03:01alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
03:02hdbngr has quit [Ping timeout: 480 seconds]
03:11pb17 has quit [Ping timeout: 480 seconds]
03:12hdbngr has joined #asahi-dev
03:16pb17 has joined #asahi-dev
03:18tobhe has joined #asahi-dev
03:20hdbngr has quit [Ping timeout: 480 seconds]
03:25tobhe_ has quit [Ping timeout: 480 seconds]
03:28hdbngr has joined #asahi-dev
03:35hexdump01 has joined #asahi-dev
03:36hdbngr has quit [Ping timeout: 480 seconds]
03:44hdbngr has joined #asahi-dev
03:53hdbngr has quit [Ping timeout: 480 seconds]
04:01hdbngr has joined #asahi-dev
04:09hdbngr has quit [Ping timeout: 480 seconds]
04:17hdbngr has joined #asahi-dev
04:22alicela1n has joined #asahi-dev
04:26hdbngr has quit [Ping timeout: 480 seconds]
04:26hdbngr has joined #asahi-dev
04:29eluks has quit [Remote host closed the connection]
04:30eluks has joined #asahi-dev
04:34nora has joined #asahi-dev
04:35hdbngr has quit [Ping timeout: 480 seconds]
04:36nora_ has quit [Ping timeout: 480 seconds]
04:43hdbngr has joined #asahi-dev
04:51hdbngr has quit [Ping timeout: 480 seconds]
05:00hdbngr has joined #asahi-dev
05:00alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
05:08hdbngr has quit [Ping timeout: 480 seconds]
05:17hdbngr has joined #asahi-dev
05:26hdbngr has quit [Ping timeout: 480 seconds]
05:34hdbngr has joined #asahi-dev
05:43hdbngr has quit [Ping timeout: 480 seconds]
05:50hdbngr has joined #asahi-dev
05:59hdbngr has quit [Ping timeout: 480 seconds]
06:08hdbngr has joined #asahi-dev
06:13alicela1n has joined #asahi-dev
06:14alicela1n has quit []
06:14chadmed has quit [Quit: Konversation terminated!]
06:15chadmed has joined #asahi-dev
06:17hdbngr has quit [Ping timeout: 480 seconds]
06:18cremfuelled has joined #asahi-dev
06:26hdbngr has joined #asahi-dev
06:28alicela1n has joined #asahi-dev
06:33alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
06:34hdbngr has quit [Ping timeout: 480 seconds]
06:39cremfuelled has quit [Quit: cremfuelled]
06:41alicela1n has joined #asahi-dev
06:41hdbngr has joined #asahi-dev
06:50hdbngr has quit [Ping timeout: 480 seconds]
06:58hdbngr has joined #asahi-dev
07:07hdbngr has quit [Ping timeout: 480 seconds]
07:17hdbngr has joined #asahi-dev
07:25hdbngr has quit [Ping timeout: 480 seconds]
07:26hdbngr has joined #asahi-dev
07:34hdbngr has quit [Ping timeout: 480 seconds]
07:36alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
07:42hdbngr has joined #asahi-dev
07:51hdbngr has quit [Ping timeout: 480 seconds]
07:59hdbngr has joined #asahi-dev
08:00weirdtreething has quit [Remote host closed the connection]
08:00weirdtreething has joined #asahi-dev
08:01maor26 has joined #asahi-dev
08:08hdbngr has quit [Ping timeout: 480 seconds]
08:12jannauchadmed: where? any details? passed a smoke test here
08:13JamesCalligeros[m]ill grab the stack dump for you, but it was a mutex at gem object close time
08:16jannausounds like it's caused by https://github.com/AsahiLinux/linux/pull/433 then cc: chaos_princess
08:16hdbngr has joined #asahi-dev
08:18JamesCalligeros[m]that does seem like the cause. ill see if reverting that fixes it later
08:22chadmedurgh the lines got truncated
08:22chadmedall the important stuff is there though
08:25hdbngr has quit [Ping timeout: 480 seconds]
08:34hdbngr has joined #asahi-dev
08:35midou has quit [Read error: No route to host]
08:42hdbngr has quit [Ping timeout: 480 seconds]
08:44midou has joined #asahi-dev
08:45alxdrl has joined #asahi-dev
08:50hdbngr has joined #asahi-dev
08:51alxdrl has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
08:52midou has quit [Ping timeout: 480 seconds]
08:59hdbngr has quit [Ping timeout: 480 seconds]
09:07hdbngr has joined #asahi-dev
09:09svenhm.. so thinking about virtualizing sptm: i think we don't even need two separate EL1 VMs or even two separate sets of pagetables: it might be enough to "just" build a single shadow page table that has has max(gl2, el2) permissions set and fake genter/gexit transitions
09:09svenstill leaves the issue of all those other apple isa extensions that are disabled
09:10chadmedif we install stage1 m1n1 as a mach-o do they still get disabled
09:10svenno, but then we're running under SPTM
09:12chadmedoh right, idk why i thought it was its own boot policy knob
09:12chadmedprobably because thats the sane thing they should have done
09:12svenit might be its own knob but I don't think we can set it individually
09:12svenmight also be useful to reverse engineer iboot and figure out how exactly the lock out works
09:16hdbngr has quit [Ping timeout: 480 seconds]
09:17sveni also still think we can probably bring up m4 except for dcp, gpu, and other complex co-processors almost blindly without the hv :D
09:23alxdrl has joined #asahi-dev
09:23hdbngr has joined #asahi-dev
09:26jannauI suspect everything except agx might be doable with supporting the same fw version on m1 - m3 a mixture of cursing, guessing and luck
09:28jannaueven thunderbolt5 / dp 2.1 might be doable with a m3 ultra (if that hasn't the same issue as m4 systems)
09:35hdbngr has quit [Ping timeout: 480 seconds]
09:37midou has joined #asahi-dev
09:43hdbngr has joined #asahi-dev
09:44sveniirc the linux tbt driver already has usb4 support so i suspect it won't be that hard with a m3 ultra
09:44svenso i think we can have two cursed streams running in parallel: 1) bring up m4 by guessing and luck and 2) virtualize sptm on m3/m4 :D
09:45svens/usb4/tbt5/
09:52hdbngr has quit [Ping timeout: 480 seconds]
09:59hdbngr has joined #asahi-dev
10:00okb has joined #asahi-dev
10:08hdbngr has quit [Ping timeout: 480 seconds]
10:16hdbngr has joined #asahi-dev
10:23jannauI'm expecting atc-phy changes for tbt5 / dp2.1 which would be preferably figured out by tracing
10:25jannauchaos_princess: do you have any changes for agx initdata in m1n1 beyond the pull request? I'd like to get that merged soon-ish
10:25hdbngr has quit [Ping timeout: 480 seconds]
10:26chaos_princessAs far as i remember i pushed everything.
10:28hdbngr has joined #asahi-dev
10:32jannauI have at least https://github.com/jannau/m1n1/commits/bootloader-cal-blobs/ on top but unfortunately don't remember if I had anything additional
10:36jannauno, I left a comment in PR and you've already picked up my changes
10:36hdbngr has quit [Ping timeout: 480 seconds]
10:44hdbngr has joined #asahi-dev
10:45lacamar- has quit [Ping timeout: 480 seconds]
10:45svenI expect them to hide most tbt5 changes in the tunables
10:46lacamar has joined #asahi-dev
10:47okb has quit [Ping timeout: 480 seconds]
10:49lacamar_ has joined #asahi-dev
10:53hdbngr has quit [Ping timeout: 480 seconds]
10:54hdbngr has joined #asahi-dev
10:55lacamar has quit [Ping timeout: 480 seconds]
11:08nickchanm5 has its own problem that SPTM tries to run its own VM called ExcalveKit
11:13nickchanthere's some m4 exclave images in certain firmwares but i don't think they are actually used
11:15lacamar_It's exciting to see the progress on the display side, it's something I've been looking forward to for a long time
11:16lacamar_Color accuracy, wide gamut, and HDR is important to me so I'm grateful it's being worked on
11:17chadmedthe driver is really scary and held together with hopes and prayers so no one really wanted to touch it :p
11:17chadmedbut its going to need to go upstream eventually so its gonna need to be good, and we might as well make it do what it's supposed to while we're at it
11:20nickchan...and exclavekit has its own kernel and rootfs dmg
11:20nickchanruns in the GLs
11:22lacamar_I didn't really appreciate how much DCP was responsible for. Don't know how you guys do it
11:26lacamar_nickchan: what is this exclavekit for?
11:27chadmedhaving the firmware do all of the really hard stuff is actually quite pleasant. the most annoying part is that we have to bend atomic modesetting around what iomfb wants to do, and this requires some pretty heinous crimes against the atomic api
11:28okb has joined #asahi-dev
11:29nickchanthere's some minor errors but I think https://arxiv.org/pdf/2510.09272 is the most comprehensive explaination (+sptm/txm/xnu as well)
11:31lacamar_chadmed: Apple lets you have some load bearing firmware, as a treat
11:32chadmedthe uncompressed blob is 9 MB :P
11:32lacamar_Just imagine having to reimplement all that
11:33chadmedmost of it is iomfb which used to be a kext that got moved to the other side of the iommu because it was so full of security holes
11:34chadmedbut the thing has so many jobs. its used in everything from the apple watch to the apple tv
11:34nickchaniomobileframebuffer
11:34nickchanioframebuffer is gone; not a thing anymore on apple silicon
11:35chadmedso the same dinky little thing has to do 1hz vrr on a watch sized oled on one end of the spectrum, and 12 bit dolby vision with dts-ma or atmos bitstream on the other end
11:35chadmednickchan: it was reimplemented in the dcp firmware
11:35chadmedmost of the layer we interact with for all the nice features is ex-iomfb
11:36chadmedits all still called iomfb in the thing too
11:36nickchanRight IOMFB still exist I am referring to the x86 IOFramebuffer
11:36nickchanwhich is another thing
11:37chadmedunfortunately some of the limitations we have inherited from its "jack of all trades master of none" firmware are total bs
11:38chadmedim rapidly losing hope that we can actually do more than two planes for example which sucks because kwin will always just use the _one_ overlay for the cursor if it can :/
11:38nickchanDcp firmware on m2 still doesn't support to outputting to two external screens
11:38chadmedlikewise if you try to move a rectangle out of the space clipped by surface 0 you will crash iomfb
11:38lacamar_nickchan: thanks for that thesis link, I'll try to wrap my head around it
11:38nickchanthe hardware can output to two screens
11:39chadmedi feel like these are things they should probably fix because it looks rather incompetent
11:39chadmed"yes we have four surfaces but lol dont actually use them"
11:41nickchaneh it's pretty average
11:41nickchanjust take a look at most android downstream kernels
11:42chadmedyeah but apple like to present themselves as better than that, and better for media creation/consumption to boot
11:42nickchanor most x86 firmwares for that matter
11:42chadmedand yeah the latter thing is still pretty true, id rather have an apple tv than some random rebadged rockchip thing under my telly
11:42lacamar_They're hiding all their dirty secrets in this firmware blob
11:43chadmedbut come on, your desktop display controller has _one_ working plane and crashes if your cursor leaves the screen are you fucking serious
11:43lacamar_Just disable mouse input for Asahi
11:44chadmedwell we just dont expose a cursor plane for the legacy cursor ioctls
11:44chadmedkwin will happily use a "normal" overlay plane for a cursor and is smart enough to immediately fall back to a software composited cursor if an atomic check on the cursor plane fails
11:45chadmedother compositors which rely on the legacy cursor plane ioctls (e.g. mutter) will simply not see hw cursor support and ignore it
11:48lacamar_What happens in MacOS? Does it not make use of multiple planes for the desktop?
11:48alxdrl has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
11:48chadmedonly two, which is what we do in the asahi kernel right now
11:49chadmedit will put the cursor on the "top" plane and the desktop on the bottom. if theres any media that is not occluded by anything else and can be directly scanned out from the gpu or avd, it will put that on the top plane, unless the cursor is being moved
11:50chadmedbecause apple control the compositor they can make it work around whatever insane limitations exist in dcp/agx/avd however they want
11:51chadmedwe do not have that luxury. we are expected to pass certain tests and uphold the guarantees/invariants of the atomic modesetting api
11:51lacamar_That sounds like a really tough constraint to work with
11:52chadmedcompositor devs are used to display engines doing stupid things
11:52nickchanone isn't expected to have a rpc interface in the kernel either
11:52nickchanBut clearly there needs to be an exception as long as it's not @apple.com
11:52chadmedzamundaaa was working on overlay plane support as it was, but implemented a preliminary "let the cursor go on an OVERLAY instead of CURSOR" thing because we asked nicely about it
11:54chadmedbut that said, not every compositor project is going to be so open, and even so its bad manners to half-arsedly implement broken stuff and expect userspace to clean up your mess
11:55chadmedthe tricolore can get away with it because... well what choice do we have but to eat whatever slop they put in front of us
11:55chadmedhowever fair or unfair it is, we are held to a higher standard, and must do better. and we can.
11:56nickchanwhat even is the tricolore
11:56chadmedred, green blue
11:57chadmedamd, nvidia, intel
11:57chadmeddo you think if i dumped millions of lines of machine-generated register definitions into the dcp driver the drm maintainers would take the patches? probably not
11:57chadmedamd can though
11:57chadmedwhos going to tell them not to
11:58pb17 has quit [Ping timeout: 480 seconds]
11:58okb has quit [Ping timeout: 480 seconds]
12:02nickchan the macos 12.3 support be removed
12:02nickchani mean can they be
12:03chadmedi removed it in one of my test branches but i think we want to keep around at least two versions for safety
12:03chadmedeven though there should be no one at all still on 12.x firmware
12:04chadmedsome stuff changed for 14.x and i think its a little more than just the method tags
12:04chadmedbut once we have some 14.x version we can and probably should drop 12.3
12:04nickchanat this point only alt distro users would be on 12.3 fw
12:04nickchanold alt distro users
12:04chadmedeven then it will just be old old alarm users
12:05nickchanalarm is alt distro now
12:05chadmedmaybe once the installer can in-place upgrade an apfs container we can drop it
12:06pb17 has joined #asahi-dev
12:20midou has quit [Read error: No route to host]
12:25chaos_princessShouldn't actually be that hard to do, as we can run a part of the install flow, then "repair m1n1", and it should work. But no real reason to bother writing it rn
12:28midou has joined #asahi-dev
12:32JamesCalligeros[m]Yeah exactly, its a job for when a firmware upgrade becomes necessary (again)
12:33JamesCalligeros[m]Having said that i wouldnt say no to a PR
12:33okb has joined #asahi-dev
12:35integralpilot has joined #asahi-dev
12:37integralpilotdo you think supporting 14.x DCP firmware for M1/M2 will work for M3 as well, like how my newer SMC firmware support for M3 works on M1/M2 as well, or would have apple changed the DCP and firmware API in M3 even on the same base macOS version?
12:42hdbngr has quit [Ping timeout: 480 seconds]
12:44integralpilot has quit [Remote host closed the connection]
12:54hdbngr has joined #asahi-dev
12:56chadmedas long as there have been no insane soc specific changes, yes
12:56chadmedthats not guaranteed, but we dont expect there to be any
13:02alxdrl has joined #asahi-dev
13:07sberz[m] has joined #asahi-dev
13:18jannauyes, it's likely that it'll work. There were some changes necessary to get it working on M1 Pro and Max but not much between M1* and M2* (ignoring dptx for the hdmi port on desktop devices)
13:20fl0_idabout booting m3 max - is it normal that if a device tree only has cpu0, that an exception can still occur on cpu4? or could it very likely also be a HV error? (https://www.pastery.net/erjhwn/)
13:20fl0_id(I don'T mean the uarterror at the bottom)
13:26jannaum3 max has 4 efficiency cores? M3* dev start on the first performance core which would be cpu4 (from m1n1's pov). linux defines the boot cpu as cpu0 independent on device tree entries
13:30hdbngr has quit [Ping timeout: 480 seconds]
13:32hdbngr has joined #asahi-dev
13:40okb has quit [Ping timeout: 480 seconds]
13:41hdbngr has quit [Ping timeout: 480 seconds]
13:59hdbngr has joined #asahi-dev
14:07hdbngr has quit [Ping timeout: 480 seconds]
14:16fl0_idjannau right that makes sense. wasn't sure about the numbering
14:22Emma[itits][m] has joined #asahi-dev
14:26fl0_idassuming the HID14 is reg_set(SYS_IMP_APL_HID14, HID14_ENABLE_NEX_POWER_GATING); then I assume one of the chickens fails, msr(s3_1_c15_c1_5, 0x3uL); would probably be next
14:26fl0_idgonna look into that more later today
14:31fl0_id(or actually I think I checked an old branch, so the current next register may be different...will check properly later)
14:35noopwafelelr 0x200 looks very healthy.. yesterday we were reliably getting corrupted code in arm_init on an M3 pro, but it failed considerably later
14:35chaos_princessjust to make sure - which macos?
14:42noopwafelI was trying 14.8.3 (without the binary patching from integralpilot's notes, so p'rhaps expected, we were just trying to confirm what we could trap)
14:43fl0_idchaos_princess this should be 14.8.3, the one recommended by integralpilot. (as I couldn't get 14.7.7, before it was 14.6.x or so)
14:44fl0_idin case you were talking to me...
14:44noopwafelfl0_id: are you doing the binary patching (w/updated offsets), or the same situation?
14:44fl0_idthis is also without binary patching, as it was said this was only necessary for macos HV iirc
14:45noopwafelright, patching macos not very relevant for linux boot I guess :D
14:48fl0_idwell that too (bth I didn't think about what it was patching)
15:06chaos_princess14.3.X may reduce the patches needed
15:08okb has joined #asahi-dev
15:18___nick___ has joined #asahi-dev
15:19___nick___ has quit []
15:21___nick___ has joined #asahi-dev
15:24Step21 has joined #asahi-dev
15:24Step21 has quit [Remote host closed the connection]
15:26Calandracas_ has joined #asahi-dev
15:27AlyssaRosenzweig[m] has left #asahi-dev [User left]
15:28Calandracas has quit [Ping timeout: 480 seconds]
15:29hdbngr has joined #asahi-dev
15:51Calandracas_ has quit [Ping timeout: 480 seconds]
16:03pb17 has quit [Ping timeout: 480 seconds]
16:10alxdrl has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
16:25vimproved has quit [Ping timeout: 480 seconds]
16:28vimproved has joined #asahi-dev
16:29Calandracas has joined #asahi-dev
16:38pb17 has joined #asahi-dev
16:44vimproved has quit [Ping timeout: 480 seconds]
16:54vimproved has joined #asahi-dev
17:04__nick__ has joined #asahi-dev
17:07___nick___ has quit [Ping timeout: 480 seconds]
17:19jannaum1n1 #466 (gpu initdata creation) merged, thanks chaos_princess
17:21jannauI guess I'll have to start upstreaming the driver now
17:22jannaunot that there is yet much to upstream without gem-shmem and gpuvm
17:26averne has joined #asahi-dev
17:39alicela1n has joined #asahi-dev
17:42svenstill great to get started 😁
17:50alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
18:01maor has joined #asahi-dev
18:08maor26 has quit [Ping timeout: 480 seconds]
18:08pb17 has quit [Ping timeout: 480 seconds]
18:23pb17 has joined #asahi-dev
18:25okb has quit [Ping timeout: 480 seconds]
18:30alicela1n has joined #asahi-dev
18:49hdbngr has quit [Ping timeout: 480 seconds]
18:51hdbngr has joined #asahi-dev
18:58fl0_id_ has joined #asahi-dev
19:00hdbngr has quit [Ping timeout: 480 seconds]
19:09hdbngr has joined #asahi-dev
19:17Glanzmann has joined #asahi-dev
19:25troseman has joined #asahi-dev
19:31alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
19:31troseman has quit [Read error: No route to host]
19:32troseman has joined #asahi-dev
19:39jmax has quit [Remote host closed the connection]
19:39jmax has joined #asahi-dev
19:41fl0_id_hey, so I commented the two t6031 specific chickens before the init_common_everest and that got me quite a bit further afaict https://www.pastery.net/gpnjmq/
19:42fl0_id_now it fails after some pmgr stuff and with SERROR
19:47alicela1n has joined #asahi-dev
19:54pb17 has quit [Ping timeout: 480 seconds]
19:54fl0_id_as this seems to fall within VUART, could it help to add uart to the device tree?
19:55fl0_id_but prob these are not related
19:58pb17 has joined #asahi-dev
19:58hdbngr has quit [Ping timeout: 480 seconds]
20:07hdbngr has joined #asahi-dev
20:14alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
20:16fl0_id_playing around a bit more with everest chickens, nothing else seems to effect this so far. neither positively or negatively, even without any chickens it still gets to the same place in the startup sequence
20:20tobhe has quit [Ping timeout: 480 seconds]
20:20opticron has quit [Read error: Connection reset by peer]
20:20opticron has joined #asahi-dev
20:31fl0_id_the t6031 chickens were originally added by dberlin, in the commit message they also said the early uart base changed, but this is exactly where it's currently failing for me. could it be possible that this is not always the same? maybe I'll just try some other ones or it's because of some other issue...
20:31hdbngr has quit [Ping timeout: 480 seconds]
20:38fl0_id_no, seems to be correct.
20:39hdbngr has joined #asahi-dev
20:46alicela1n has joined #asahi-dev
20:48hdbngr has quit [Ping timeout: 480 seconds]
20:52fl0_id_ has quit [Remote host closed the connection]
20:55hdbngr has joined #asahi-dev
21:04hdbngr has quit [Ping timeout: 480 seconds]
21:07__nick__ has quit [Remote host closed the connection]
21:07okb has joined #asahi-dev
21:09alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
21:11hdbngr has joined #asahi-dev
21:16maor26 has joined #asahi-dev
21:20hdbngr has quit [Ping timeout: 480 seconds]
21:22maor has quit [Ping timeout: 480 seconds]
21:25alxdrl has joined #asahi-dev
21:27hdbngr has joined #asahi-dev
21:29fl0_id_ has joined #asahi-dev
21:36hdbngr has quit [Ping timeout: 480 seconds]
21:43hdbngr has joined #asahi-dev
21:47pb17 has quit [Ping timeout: 480 seconds]
21:47alicela1n has joined #asahi-dev
21:51hdbngr has quit [Ping timeout: 480 seconds]
21:54pb17 has joined #asahi-dev
21:59hdbngr has joined #asahi-dev
22:01fl0_id_ has quit [Remote host closed the connection]
22:07alicela1n has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
22:07hdbngr has quit [Ping timeout: 480 seconds]
22:16hdbngr has joined #asahi-dev
22:24hdbngr has quit [Ping timeout: 480 seconds]
22:33hdbngr has joined #asahi-dev
22:41hdbngr has quit [Ping timeout: 480 seconds]
22:42hdbngr has joined #asahi-dev
23:05hdbngr has quit [Ping timeout: 480 seconds]
23:07lyudess has quit []
23:07Lyude has joined #asahi-dev
23:12hdbngr has joined #asahi-dev
23:21hdbngr has quit [Ping timeout: 480 seconds]
23:27okb has quit [Read error: Connection reset by peer]
23:28hdbngr has joined #asahi-dev
23:32integralpilot has joined #asahi-dev
23:33integralpilotm1n1 doesn't use your linux FDT as the source of truth, it uses the ADT, so modifying the linux device tree won't change anything
23:35integralpilotalso, the reason it's happening on cpu4 is because that's just the one m1n1 picked to boot off (based on the ADT). linux will also probably be started on cpu4 by m1n1 as that's it's primary one. because linux only sees one CPU in it's FDT (cpu0) it will not try starting any other CPUs and just stay on cpu4. technically you could change the one CPU in the linux FDT to cpu4 but that wouldn't change anything
23:35integralpilotsorry, rather, that's the one iBoot loaded m1n1 on
23:37hdbngr has quit [Ping timeout: 480 seconds]
23:37jannauwe probably want m1n1 to switch to cpu0 in kboot.c
23:39alxdrl has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
23:41integralpilotwould that change anything though?
23:44hdbngr has joined #asahi-dev
23:47integralpilotbtw, when the error happens, do you see an asahi logo with some logs, or a rainbow apple logo? wondering if m1n1 has loaded yet or not
23:49integralpilot has quit [Quit: integralpilot]
23:50fl0_idright. thanks about clarifying.
23:51fl0_idI think first I see the asahi log with some logs. then m1n1 restarts
23:51fl0_idwhen experimenting sometimes I got the rainbow apple logo
23:51fl0_idI could do a video just to be sure
23:52fl0_idthe chainloaded m1n1 loaded for sure.
23:53fl0_idmmh EL1 m1n1... I think so?
23:53hdbngr has quit [Ping timeout: 480 seconds]
23:53fl0_idI'll make a video to be sure...
23:54fl0_idcan we ask dberlin what those two first chickens for t6031 were for?
23:54fl0_idif they kno
23:56lacamar[m] has joined #asahi-dev
…