#
…

2026-01-27

00:04jsk has joined #asahi-dev
00:21fl0_id__ has joined #asahi-dev
00:24hdbngr has quit [Ping timeout: 480 seconds]
00:24Card has joined #asahi-dev
00:28slendidev has quit [Read error: Connection reset by peer]
00:28slendidev has joined #asahi-dev
00:33hdbngr has joined #asahi-dev
00:41pb17 has quit [Remote host closed the connection]
00:42pb17 has joined #asahi-dev
00:47hdbngr has quit [Ping timeout: 480 seconds]
00:53fl0_id__ has quit [Read error: Connection reset by peer]
00:53fl0_id__ has joined #asahi-dev
00:54mixi has quit [Ping timeout: 480 seconds]
00:55rubano1421 has joined #asahi-dev
00:55hdbngr has joined #asahi-dev
00:55fl0_id___ has joined #asahi-dev
00:58fl0_id__ has quit [Read error: Connection reset by peer]
00:58jskhi :) when trying to boot m3, which kernel branch should one use? the device trees are not there yet, are they?
01:00jskin general, what branch is considered the main dev branch? asahi, asahi-wip? what about fairydust? thanks
01:04hdbngr has quit [Ping timeout: 480 seconds]
01:04mixi has joined #asahi-dev
01:12hdbngr has joined #asahi-dev
01:20hdbngr has quit [Ping timeout: 480 seconds]
01:26hdbngr has joined #asahi-dev
01:35hdbngr has quit [Ping timeout: 480 seconds]
01:42hdbngr has joined #asahi-dev
01:45rubano1421 has quit [Quit: Textual IRC Client: www.textualapp.com]
01:51hdbngr has quit [Ping timeout: 480 seconds]
01:58hdbngr has joined #asahi-dev
02:07hdbngr has quit [Ping timeout: 480 seconds]
02:14hdbngr has joined #asahi-dev
02:23hdbngr has quit [Ping timeout: 480 seconds]
02:27fl0_id___jsk asahi-wip is more current, but as most m3 stuff is not merged there, doesn't rly matter probably
02:28fl0_id___fairydust is only for that one specifc thing
02:28fl0_id___*not merged yet i mean
02:30hdbngr has joined #asahi-dev
02:32jskok thanks
02:33jsk has quit [Remote host closed the connection]
02:33pb17 has quit [Ping timeout: 480 seconds]
02:35jsk has joined #asahi-dev
02:36jskon another topic, when generating the pmgr from the adt, some things seem to be missing. most notably ps_sio. is that expected? how could I get that one?
02:36jsk has quit [Remote host closed the connection]
02:39hdbngr has quit [Ping timeout: 480 seconds]
02:46hdbngr has joined #asahi-dev
02:55hdbngr has quit [Ping timeout: 480 seconds]
02:59pb17 has joined #asahi-dev
03:00fl0_id___ has quit [Ping timeout: 480 seconds]
03:05hdbngr has joined #asahi-dev
03:13hdbngr has quit [Ping timeout: 480 seconds]
03:16mesa has quit [Ping timeout: 480 seconds]
03:16mesa has joined #asahi-dev
03:23hdbngr has joined #asahi-dev
03:27tobhe_ has joined #asahi-dev
03:31hdbngr has quit [Ping timeout: 480 seconds]
03:34tobhe has quit [Ping timeout: 480 seconds]
03:39hdbngr has joined #asahi-dev
03:48hdbngr has quit [Ping timeout: 480 seconds]
03:55hdbngr has joined #asahi-dev
04:02hexdump02 has joined #asahi-dev
04:04hdbngr has quit [Ping timeout: 480 seconds]
04:04hexdump0815 has quit [Ping timeout: 480 seconds]
04:11hdbngr has joined #asahi-dev
04:20andle has joined #asahi-dev
04:20hdbngr has quit [Ping timeout: 480 seconds]
04:22slendidev has quit [Ping timeout: 480 seconds]
04:22slendidev has joined #asahi-dev
04:27hdbngr has joined #asahi-dev
04:29eluks has quit [Remote host closed the connection]
04:30eluks has joined #asahi-dev
04:31hexdump01 has joined #asahi-dev
04:33hexdump02 has quit [Ping timeout: 480 seconds]
04:36hdbngr has quit [Ping timeout: 480 seconds]
04:41andle has quit [Ping timeout: 480 seconds]
04:43hdbngr has joined #asahi-dev
04:47nora_ has joined #asahi-dev
04:49nora has quit [Ping timeout: 480 seconds]
04:51hdbngr has quit [Ping timeout: 480 seconds]
04:59hdbngr has joined #asahi-dev
05:07hdbngr has quit [Ping timeout: 480 seconds]
05:14hdbngr has joined #asahi-dev
05:25hdbngr has quit [Ping timeout: 480 seconds]
05:33hdbngr has joined #asahi-dev
05:39pb17 has quit [Ping timeout: 480 seconds]
05:42hdbngr has quit [Ping timeout: 480 seconds]
05:45pb17 has joined #asahi-dev
05:50hdbngr has joined #asahi-dev
05:56lukeleppan has quit [Quit: The Lounge - https://thelounge.chat]
05:58hdbngr has quit [Ping timeout: 480 seconds]
06:00hdbngr has joined #asahi-dev
06:00lukeleppan has joined #asahi-dev
06:08hdbngr has quit [Ping timeout: 480 seconds]
06:11hdbngr has joined #asahi-dev
06:20hdbngr has quit [Ping timeout: 480 seconds]
06:26nnym has quit [Ping timeout: 480 seconds]
06:29hdbngr has joined #asahi-dev
06:37hdbngr has quit [Ping timeout: 480 seconds]
06:46hdbngr has joined #asahi-dev
06:54hdbngr has quit [Ping timeout: 480 seconds]
07:00Pokemod977362084712 has quit []
07:04hdbngr has joined #asahi-dev
07:10Pokemod977362084712 has joined #asahi-dev
07:13hdbngr has quit [Ping timeout: 480 seconds]
07:20hdbngr has joined #asahi-dev
07:27pb17 has quit [Ping timeout: 480 seconds]
07:29hdbngr has quit [Ping timeout: 480 seconds]
07:38hdbngr has joined #asahi-dev
07:44sklug_ is now known as sklug
07:47hdbngr has quit [Ping timeout: 480 seconds]
07:47pb17 has joined #asahi-dev
07:54hdbngr has joined #asahi-dev
08:03hdbngr has quit [Ping timeout: 480 seconds]
08:12hdbngr has joined #asahi-dev
08:21hdbngr has quit [Ping timeout: 480 seconds]
08:29hdbngr has joined #asahi-dev
08:37hdbngr has quit [Ping timeout: 480 seconds]
08:45hdbngr has joined #asahi-dev
08:52nnym has joined #asahi-dev
08:53hdbngr has quit [Ping timeout: 480 seconds]
08:54jannaunoopwafel: I've pushed a basic t8122 devicetree to https://github.com/AsahiLinux/linux/tree/bits/001-devicetree-m3
08:56jannaumake dtbs_check should not produce any warnings in that branch. if you want to test just a single device tree you can use `make O=_checkdtb CHECK_DTBS=y apple/t8122-j504.dtb`
08:57jannauthe latter should also work in asahi-wip. The m3 branch is merged
08:59jannaufeel free to pick stuff from https://github.com/jannau/linux/tree/t8122-j504 where the untested / unadjusted dt-bindings device nodes are
09:00alessaba_928 has quit [Remote host closed the connection]
09:01hdbngr has joined #asahi-dev
09:07nickchanperformance counter is another easy target
09:07nickchanjust need to figure out whether to use a16 events or a17 events
09:08nickchanand compare to existing m1/m2 events to see if it's possible to just add new events to the existing table
09:08nickchanor if brand new event table is needed because events are removed
09:10hdbngr has quit [Ping timeout: 480 seconds]
09:13hdbngr has joined #asahi-dev
09:22nickchanalso none the usb hpm stuff won't work right cause it's on spmi in m3
09:22hdbngr has quit [Ping timeout: 480 seconds]
09:22nickchani mean none of them would work
09:29hdbngr has joined #asahi-dev
09:38hdbngr has quit [Ping timeout: 480 seconds]
09:39hdbngr has joined #asahi-dev
09:48hdbngr has quit [Ping timeout: 480 seconds]
09:50sventhere's some commits by mildsunrise improving the upstream SPMI driver and some notes how the new pd controller works
09:51svenit's using regmap anyway so adding spmi support shouldn't be too hard
09:55hdbngr has joined #asahi-dev
10:01svenjust need sign-offs and some cleanup
10:01mildsunriseyes, it's not a complicated regmap to implement... the interrupts also go through spmi but that will work out of the box with the new driver
10:03ferdzo has joined #asahi-dev
10:04hdbngr has quit [Ping timeout: 480 seconds]
10:13hdbngr has joined #asahi-dev
10:18svenyeah, and the base (?) m3 still has the tipd chip anyway
10:21integralpilot has joined #asahi-dev
10:22hdbngr has quit [Ping timeout: 480 seconds]
10:22integralpilotsorry i wasn't able to get up to much today, there were intermittant blackouts cause the temp hit 45 celsius and everyone was running the AC!
10:23integralpilotnoopwafel: omg that's awesome, great work on WiFi!!
10:24integralpilotalso looks the working KDE on M3 annoucement took off which is great, got lots of positive comments directed at the team across the net: ~120k hits on twitter and i think it was 3rd (?) on HN for a bit
10:26integralpilotgreat job everyone working on this, i think we're making awesome progress :)
10:28svenare people asking about gpu yet without realizing just how many orders of magnitude that's gonna be more complex? :p
10:30hdbngr has joined #asahi-dev
10:31JamesCalligeros[m]integralpilot: melbourne?
10:32integralpilotsven: yep, but i think most know it's going to be pretty hard. i'm actually interested in learning about gpus so am researching it now and might start experimenting with a few things
10:32integralpilotchadmed: yeah! :)
10:32JamesCalligeros[m]Escaped back to brisbane yesterday thank god i wouldve been instagibbed by the heat today
10:33integralpilotoh that's good!
10:36chadmedgpu-wise i think we just have to keep holding the line on "its done when its done"
10:37chadmedpart of making that work is staying mum about progress until stuff _is_ actually ready
10:37svenyeah. it's also a good idea to remind people that the userspace driver alone is something like 50k lines of code
10:38chadmedmy favourite way to do that is to just mic drop working stuff in progress reports carefully timed to coincide with package releases/tags
10:38chadmedwe learnt our lesson with the speaker stuff and then again with tbt/dp alt mode
10:38hdbngr has quit [Ping timeout: 480 seconds]
10:38integralpilotyeah, basically just been saying we're working on it, but it will take some time cause there's currently no GPU specialists so we have to learn it as well
10:39chadmedyeah the gpu is scary :p
10:42chadmedif i didnt have to deal with the insane housing market id probably just quit my job and spend a couple of months tying up some loose ends
10:43chadmedbut even a couple of weeks without income is financially unviable rn
10:43integralpilotive got school starting again in 2 days so wont have much time to dedicate anymore either, but will still try when i can
10:44chadmedoh rip i thought school started back next week for vic and nsw
10:44svenimho we should focus on getting m3 support actually useable and installable before starting to put a lot of effort into the gpu
10:44integralpilotmy school starts early :(
10:44svenright now it's at the tech demo stage, and we all know that the second 80% of projects take more time than the first 80% usually :P
10:44chadmedthe installer shouldnt be too much trouble to sort out. we need to cut a release anyway
10:45chaos_princessare we sure we want the installer before the everything-except-gpu stage?
10:45svenimho no
10:46svenwe also need to commit to some firmware version before
10:46integralpiloti think that runs the risk of making bad perceptions, we only get one "M3 offically launched" PR round and we want it to be good
10:46hdbngr has joined #asahi-dev
10:46chaos_princesslike, if you want to do development, and you can't patch out the checks, you probably won't have much success
10:46chadmedi was hoping to have time to look at 14.x dcp firmware so we could at least have that, but we just fired another guy and guess who got his workload (im going to lose the plot)
10:47integralpilotPR as in public relations, not pull request
10:47sveni think it's fine to release framebuffer+llvmpipe (or dcp+llvmpipe if that's useable these days) with other hardware support similar to m1/m2
10:47svenbut ideally not before that
10:47chaos_princessfired or laid off?
10:47chadmedfired, he almost got us sued by the federal government
10:47chaos_princessdcp+llvmpipe is not usable
10:48chadmeddcp+llvmpipe sucks so hard
10:48svenhave you checked recently? because it was fine during ccc
10:48chadmedand idek why because it used to be fine :P
10:48chaos_princesschadmed: hey, it is better, at least you probably will get a replacement
10:48chaos_princesssven: yes. i too screwed up my rust install :P. But i am on j314, so it may be worse there
10:48sventhe cores were all busy at like 20-30% on my base m1 but i didn't really notice
10:49chadmedits awful on my j415, j314 and whatever the m2 max studio is called i forgor
10:49integralpilotsimilar numbers on m3 for fb+llvmpipe
10:49chaos_princessit is noticeable if you for example try to shut it down via kde ui, the screen dimming animation runs at like 5 fps
10:49svenit's gonna burn through the battery but i barely noticed lag or anything else
10:49sventhat i didn't try
10:49chadmedprobably just 100 trillion terabytes of framebuffer data being copied or something :P
10:50chadmedit scales very poorly as the damage regions get larger
10:51NickChan[m]asahi linux alpha release is a good reference
10:51NickChan[m]I think SD card reader and usb3 can be skipped even
10:51svenhard disagree
10:51svenat least about usb3
10:51chadmedyeah no we need to do better
10:52chaos_princesssd should be easy? it just hangs off the pci bus
10:52svenusb3 is likely fine as well once we have spmi + tipd
10:52chadmedsd card is whatever as long as there arent random power management serrors
10:53chadmedmvp this time around basically has to be everything except gpu/dcp imo
10:53chadmedand thats okay, we dont need to rush a release out the door
10:54chadmeddoubly so if we want to get at least some of this stuff upstream-only
10:54sveni think at least all dt-bindings we use have to be reviewed before we release anything
10:54svenbecause using unreviewed ones has been very painful in the past
10:55chaos_princessoh, i have one that will be "fun" :P
10:55hdbngr has quit [Ping timeout: 480 seconds]
10:55svensame, tbt is gonna be great as well
10:55chadmedi dont think theres any real reason to stage trivial changes downstream anymore unless the whole driver is also still downstream
10:55NickChan[m]that thing must have plenty of tunables
10:55sventbt? nope
10:56sveni think it's two additional ones for the co-processor and NHI
10:56sventhe magic all happens inside atcphy
10:57chadmedi wonder if their rf chips will be as black boxy
10:58NickChan[m]on the other hand, j180d is still not supported (who actually uses that machine)
10:58chaos_princessjan_ne has one, and the device tree
10:59chadmedlast time i checked there were single digit install attempts so....
11:00chadmedidek why they released it tbh its so obvious the studio is supposed to replace it
11:00chaos_princessprobably because they promised a full arm transition
11:00integralpilotthat's the cheese grater right?
11:00chadmedi half expected it to be a test bed for a new server platform but they never followed through on that
11:01chadmedmaybe if it had more real pcie lanes it wouldve been interesting
11:01integralpiloti wonder what apple uses for their own servers?
11:02chaos_princessgeneric linux boxes
11:02integralpilotyeah @apple.com ppl contribute a lot to like kernel core stuff, so i guess that makes sense
11:02NickChan[m]or for PCC rack m2 ultra
11:02chaos_princessand server-ized macs for "private clould compute"
11:02integralpilotthey're doing it to help their servers
11:02chadmedpretty sure their private compute stuff is rackmounted apple silicon
11:02chadmedyeah that ^
11:02NickChan[m]m2 ultra is clearly not a good fit for macpro and a fallback, and we will see about m5 ultra
11:03chadmedwell they glued on a whole second pcie controller and that still couldnt save it. i dont expect to see another cheese grater. the m5 ultra will probably go in a studio
11:03chaos_princessi don't expect anything
11:03hdbngr has joined #asahi-dev
11:04NickChan[m]i don't expect anything either other than raw specs more suitable for a macpro (but still no PCI GPU etc)
11:04chaos_princessoh, i expect that that thing fully dies. studio only from now on
11:05integralpilotis tbt pcie still not workable on newer socs?
11:05integralpilotmaybe they'll explore that prehaps
11:05jannauisp/webcam can probably a optional initial feature as well for m3 devices
11:05chadmedits not that pcie over tbt doesnt work, its that the thing doesnt support the memory model that gpus assume exists for performance hacks
11:06chadmediirc the rpi 4 suffered from a similar problem, and even with revolting disgusting amdgpu kernel driver hacks to make it "work" it was abysmally slow
11:06jannauthe base m3 macbook pro and the m3 imacs are still using i2c usb-pd controllers
11:07nickchani thought tencent had a workaround for the memory model thing
11:07chadmedthe other problem is, no one is writing a driverkit/iokit/whateverkit pcie driver for their widget unless apple pays them, and apples not going to pay them because apple's got their own hardware
11:07jannauthe mac pro is supported except for the main installer since the fedora images are too old. Will be fine with Fedora 43
11:07nickchanon marcan's socials of course which is deleted
11:08integralpilothigh performance drivers on macOS wouldn't really work either as they've "deprecated" (and made nearly impossible to guide a user to install) kernelspace drivers, and only offer a limited userspace driver api
11:08jannaunvidias kernel and user space driver work on the mac pro, I'd expect they work via thunderbolt as well
11:10jannauampere has a workaround of trapping unaligned access
11:11noopwafelintegralpilot: I have a bunch of work on the AGX tracer btw
11:11noopwafelmy intention is to do M3 gpu bringup (and the rest of this is just a distraction because I want to be able to run code :p)
11:12jannauthe m2 ultra is a little short on PCIe lanes (16 + 8) for its case / number of slots. the massive PCIe switch mitigstes that. only being PCIe 4 doesn't help either
11:12hdbngr has quit [Ping timeout: 480 seconds]
11:12integralpilotoh okay that sounds cool!
11:12integralpilotif you want to do the kenrel side of things im happy to do the userspace side of things
11:12integralpiloti really like compilers
11:12noopwafelthere is going to be more than enough to do :-D
11:13integralpilotim just curious how they changed the ISA, it's probably a lot i'm thinking
11:13nickchanray tracing
11:13nickchanthat cannot be a small change
11:14chaos_princesshas some m3 stuff
11:14noopwafelsee tellowkrinkle's applegpu fork for some more
11:14integralpilotinteresting, thank you! will take a look
11:14hdbngr has joined #asahi-dev
11:15alessaba has joined #asahi-dev
11:16integralpilotwhat does [flagged] [dead] mean on HN? i'm guessing don't click on that?
11:16chaos_princesscomment or submission?
11:17integralpilotcomment on the m3 submission that someone else made based on my bsky post
11:18chaos_princesssomeone said something that was too vile even for hn
11:18noopwafelbtw - does anyone (integralpilot) have a DT with mtp/dockchannel working?
11:19chadmedmore unsolicited advice: just avoid hn entirely. dont post there, dont go there
11:19noopwafelbefore I spend more time debugging and/or reinventing the wheel..
11:19integralpiloti'm on another computer rn but i think i uploaded it somewhere
11:19integralpilotlet me take a took
11:19noopwafeloh sorry let me jsut check logs
11:20integralpilotoh no i wasnt saying in this server, i meant to a private gist or i also have a private discord server i use as a pastebin
11:20integralpilotim just checking them now
11:21integralpilotin terms of gist there's: https://gist.github.com/IntegralPilot/74448a31fbae11a76f489d26f2a01fe7 but that's the new format not old
11:21integralpilotyou can probably just get the addresses out of there and put them in old
11:21noopwafel"it works for me" is already super useful info :)
11:22chadmedtriforce went viral on hn (i didnt even post it) and all it really led to was a bunch of "why didnt he just use AI" and a job offer from the modern day mengele himself (i said no of course)
11:22integralpilotwhen my CVEs went viral on twitter i got unsolicited email job offers from grey market companies and it was weird (ofc said no)
11:22integralpilotwell, actually, i just ghosted
11:23hdbngr has quit [Ping timeout: 480 seconds]
11:23chadmedneuralink found my work email and had some chud spam it with "come work for us" crap
11:23noopwafel(I guess this is a bit -offtopic but I also very much advocate avoiding HN)
11:23chadmedno thanks elon im not helping you brainjack my friends even if i thought i had the skills to do so
11:24j`ey_chadmed: what about the AI code review you got?
11:24chadmedlmao is it even right? something looks off about it
11:25integralpilotyeah like surely you can't just send AI unchecked on list right?
11:25chadmedi know we arent doing denormals properly in that code but thats not going to cause FIELD_PREP issues is it
11:25integralpilotthat was kinda weird when i saw it
11:25chadmedintegralpilot: unfortunately the person who did it is the hwmon maintainer and can do whatever he wants :P
11:25chaos_princessintegralpilot: you can if you work for nvidia.. cough sasha levin, cough
11:25nickchanunfortunately sanctioned ai slop is on the ML now and has been for a while
11:27nickchani already have to shot down some patches when the ai decided that the a11 mailbox support should be backported to stable
11:27chadmedi just ignore those. if sasha wants to poison gregkh's stable tree thats between them
11:27chadmedif it blows up in their faces, good maybe theyll stop doing it
11:28chadmedit keeps picking up asoc codec changes as stable backports for some reason
11:29chadmedeven though half of it is implementing entirely new features
11:30hdbngr has joined #asahi-dev
11:34Mrmaxmeier1 has quit [Quit: The Lounge - https://thelounge.chat]
11:35Mrmaxmeier1 has joined #asahi-dev
11:35Mrmaxmeier1 has quit []
11:39hdbngr has quit [Ping timeout: 480 seconds]
11:46hdbngr has joined #asahi-dev
11:49noopwafelintegralpilot: (also .. 'new format'? is there a tree/series somewhere?)
11:49integralpilotbut also that format is being iterated on again to make it not an interrupt controller and instead a mailbox
11:50noopwafelthank you :)
11:51integralpilotoh and if you use the new rewritten driver i made, it only supports keyboard and not trackpad so far FYI
11:52svenkernel is probably 10% of the work for m3 gpu, userspace will be easily 90%
11:52jsk has joined #asahi-dev
11:54jannauis smc already working? iirc that's mtp dependency. I guess it is when wifi works
11:55integralpilotthat's how i wrote the SMC power driver as i only have m3 :D
11:55jannauah, that too
11:55jsk has quit [Read error: Connection reset by peer]
11:55hdbngr has quit [Ping timeout: 480 seconds]
11:56jannaufor bringup I'll just go with existing mtp/dockchannel "bindings" and driver
11:57jsk has joined #asahi-dev
11:57jsk has quit [Read error: Connection reset by peer]
11:58jannaunot sure how to handle m3 dt changes for downstream drivers though. they should not live in bits/001-devicetree-m3
11:59chadmedcan they be squashed into the normal dt branch?
11:59ferdzoi have one maybe boring question
11:59ferdzofor you guys
11:59ferdzobut how far away is working usb over hdmi on m1?
11:59sven*sigh*
12:00ferdzohahaha thats why i sad boring for you :p
12:00noopwafeljannau: would it be helpful to PR a commit with j613 and/or pieces which are supported upstream but aren't yet in that minimal DT?
12:00svenno, annoying
12:00ferdzoyeah i know
12:00svendo you want me to kickban you?
12:00ferdzoi just got here to say this is one of the coolest projects i've ever seen tho
12:00ferdzosven: wow
12:00jannauchadmed: we try to avoid cross branch dependencies
12:01jannaunoopwafel: yes please. that was the intention of the branch
12:03jannauPRs either against asahi-wip or bits/001-devicetree-m3 directly
12:04hdbngr has joined #asahi-dev
12:09integralpilot has quit [Remote host closed the connection]
12:09integralpilot has joined #asahi-dev
12:24hdbngr has quit [Ping timeout: 480 seconds]
12:32hdbngr has joined #asahi-dev
12:32andle has joined #asahi-dev
12:40hdbngr has quit [Ping timeout: 480 seconds]
12:41integralpilot has quit [Quit: integralpilot]
12:47pb17 has quit [Ping timeout: 480 seconds]
12:48hdbngr has joined #asahi-dev
12:56hdbngr has quit [Ping timeout: 480 seconds]
13:01hdbngr has joined #asahi-dev
13:14pb17 has joined #asahi-dev
13:39mixi has quit [Ping timeout: 480 seconds]
13:41hdbngr has quit [Ping timeout: 480 seconds]
13:52kloenk has quit [Remote host closed the connection]
13:53mixi has joined #asahi-dev
13:55kloenk has joined #asahi-dev
14:04Shizferdzo: happy it's useful for you :)
14:11mixi has quit [Ping timeout: 480 seconds]
14:17lukeleppan has quit [Quit: Ping timeout (120 seconds)]
14:21lukeleppan has joined #asahi-dev
14:24mixi has joined #asahi-dev
14:32slendidev has quit [Read error: Connection reset by peer]
14:36mixi has quit [Ping timeout: 480 seconds]
14:38mazis anyone running upstream with lockdep on? I'm seeing a splat at boot time coming from the SMC driver (DEBUG_LOCKS_WARN_ON(lock->magic != lock)) which is a bit worrying.
14:39chaos_princessi've got lockdep complaints from drm drivers, but not smc
14:39mazcoming from apple_smc_probe(). that's on M2pro mini.
14:39mazI'll investigate once I find the regression I have introduced in NV...
14:39mazsven: ah, that'd be it!
14:41mazwonder why that wasn't sent as a fix to Linus.
14:41jannaumaz: 414f65d67363 in next
14:41sventhat one took a while to be picked up for some reason :/
14:44jannaumostly me being annoyed by the discussion about commit message style and then forgetting about it
14:44jannauI originally sent it in september
14:47mazhuh. Elfring in the loop. no wonder you got annoyed...
14:50mixi has joined #asahi-dev
14:53chadmed has quit [Remote host closed the connection]
14:53chadmed has joined #asahi-dev
14:58john-cabaj has joined #asahi-dev
15:03mixi has quit [Ping timeout: 480 seconds]
15:07hdbngr has joined #asahi-dev
15:16mixi has joined #asahi-dev
15:24fl0_idbtw tried to get some more cpufreq debug output last night, but it didn't really help much. It seems like the ecpu switches pstates successfully, then directly after, before I can get any output from the loop that would work on the pcpu, it reboots/resets.
15:25fl0_idand for reference, this is my t6031 wip branch. https://github.com/step21/linux-asahi/tree/t6031-draft
15:26fl0_idbased on asahi-wip
15:45JoshuaPeisach[mds]fl0_id: i see the framebuffer0 mentioned in the dt, i don't think the other dt's have the framebuffer specifically lined out (or is the M3 different?)
15:57fl0_idThe ones I used as comparison from other ppl working on m3 had it. This is WIP, so it won't stay like this most likely
15:58fl0_id(but others can probably also answer this better than me)
16:14chadmed has quit [Read error: Connection reset by peer]
16:15chadmed has joined #asahi-dev
16:20charlie has joined #asahi-dev
16:21pb17 has quit [Ping timeout: 480 seconds]
16:41pb17 has joined #asahi-dev
16:44charlie has quit [Quit: charlie]
16:55hdbngr has quit [Ping timeout: 480 seconds]
16:59hdbngr has joined #asahi-dev
17:14hdbngr has quit [Ping timeout: 480 seconds]
17:25hdbngr has joined #asahi-dev
17:34hdbngr has quit [Ping timeout: 480 seconds]
17:35hdbngr has joined #asahi-dev
17:38yanovskyy has joined #asahi-dev
17:40yanovskyy has quit [Remote host closed the connection]
17:43hdbngr has quit [Ping timeout: 480 seconds]
17:52hdbngr has joined #asahi-dev
17:57Yushi has quit [Ping timeout: 480 seconds]
18:01hdbngr has quit [Ping timeout: 480 seconds]
18:07hdbngr has joined #asahi-dev
18:12jgoyvaerts has joined #asahi-dev
18:13pb17 has quit [Ping timeout: 480 seconds]
18:15lukeleppan has quit [Ping timeout: 480 seconds]
18:16jgoyvaertsstupid question, what are the odds of bricking my macbook/data loss on my mac partition if i start playing around with asahi ? (it's an M4, i know that's not supported yet)
18:18sventhe worst that can realistically happen is data loss. even if you completely erase the ssd and the nor flash you can still recover with a dfu revive
18:18pb17 has joined #asahi-dev
18:18fl0_idso for example don't mess with SEP
18:19fl0_idas that could trigger need for dfu from what I understand
18:24tpw_rulesnoting that a dfu revive requires some effort and another computer, but it's not bad
18:25svenyeah, if you have an Apple Store nearby they’ll also do it for you
18:25jgoyvaertsI'm a digital nomad, currently in south america, so Apple stores aren't around unfortunately.
18:25svensecond computer then. Another Mac makes is easier but Linux with libidevicerestore also works
18:26jgoyvaertsaight thanks
18:33hdbngr has quit [Ping timeout: 480 seconds]
18:33tpw_rulesalso devil's advocating again, it's not too hard to screw things up to require this state, deleting or modifying the wrong partition will do it easily. but it is indeed the worst that can happen, there's no way to damage it badly enough that a dfu revive won't fix it
18:34tpw_rulesodds of bricking: 0%, odds of data loss: if playing around with an unsupported configuration, high enough you want a time machine backup or to not care
18:35andle has quit [Remote host closed the connection]
18:41hdbngr has joined #asahi-dev
18:42freetolga has joined #asahi-dev
18:43Glanzmann has left #asahi-dev [#asahi-dev]
18:46freetolgahas anyone tested the oldest version of macos capable of running on an m4
18:46freetolgadoes that have any hope of speeding up hardware RE
18:47svenI don’t see how that would help
18:47Yushi has joined #asahi-dev
18:47freetolgapotentially seeing some early build that doesnt have the restrictions
18:47JoshuaPeisach[mds]what restrictions?
18:48JoshuaPeisach[mds]I don't think we're trying to do like.. voltage glitching \:P
18:48svenrandom guessing doesn’t help here
18:48svenif you have a good reason to believe that feel free to check it out yourself
18:49freetolgaoh i forgot that the thing making m4 bringup annoying was i-boot
18:49freetolganot the macos itself
18:49cyberheadis m4 still not booting?
18:49freetolgabtw is macos 15 out of support?
18:49svenplease stick to #asahi for these non-development discussions
18:50hdbngr has quit [Ping timeout: 480 seconds]
18:50cyberheadfreetolga: macos 15 updates are still being released
18:50JoshuaPeisach[mds]anyways.. so I noticed that camera doesn't work on J316. (unless cheese is lying to me). any specific troubles i can maybe look at?
18:54cyberheaddoes the ability for macOS to make macOS virtual machines somehow aid reverse engineering?
18:54cyberheadj`ey_: it seems much more rightly bound to hardware than any other hypervisor available
18:55hdbngr has joined #asahi-dev
18:56chaos_princesscyberhead: macos runs a different kernel build when run in a vm, Virtualization.framework emulates a generic arm64 system, not a mac
18:58john-cabaj has quit [Remote host closed the connection]
18:58cyberheadchaos_princess: i genuinely thought it was about binding mac VMs to hardware
18:59chaos_princessJoshuaPeisach[mds]: from what i remember, it is a case of cheese lying, that specific program had some issue that made it not work with mac cameras
18:59chaos_princessi think it should be fixed soon-ish
18:59john-cabaj has joined #asahi-dev
19:00lukeleppan has joined #asahi-dev
19:00JoshuaPeisach[mds]good! (in terms of completion but not me trying to find a way to be helpful with my device everyone has had for five years)
19:02chaos_princessyea, j31{4,6} is our second most popular machine or something
19:02e9 has joined #asahi-dev
19:04emptynine has quit [Ping timeout: 480 seconds]
19:05jannaudoes idevicerestore work on m4? at least sometimes new devices/macos versions don't work from the get go. m4 is probably safe by now
19:07jannauJoshuaPeisach[mds]: with pipewire 1.4.10? prior to that gstpipewiresrc is known broken with the isp webcam driver
19:09sveniirc m4 is supported at this point
19:11hdbngr has quit [Ping timeout: 480 seconds]
19:12hdbngr has joined #asahi-dev
19:21hdbngr has quit [Ping timeout: 480 seconds]
19:22aditya has joined #asahi-dev
19:25SunWuKung has joined #asahi-dev
19:27SunWuKung has quit [Remote host closed the connection]
19:27john-cabaj has quit [Read error: Connection reset by peer]
19:28hdbngr has joined #asahi-dev
19:30SunWuKung has joined #asahi-dev
19:38lukeleppan has quit [Quit: The Lounge - https://thelounge.chat]
19:40yukaCan confirm idevicerestore (recent enough versions) work on M4 Mac Mini
19:45lukeleppan has joined #asahi-dev
19:50hdbngr has quit [Ping timeout: 480 seconds]
19:55john-cabaj has joined #asahi-dev
20:09pb17 has quit [Ping timeout: 480 seconds]
20:09ece314378925355451680698427415 has joined #asahi-dev
20:12pb17 has joined #asahi-dev
20:35SunWuKung has quit [Remote host closed the connection]
20:40john-cabaj has quit [Read error: No route to host]
20:40SunWuKung has joined #asahi-dev
20:49mixi has quit [Ping timeout: 480 seconds]
20:58yanovskyy has joined #asahi-dev
20:59yanovskyy has quit []
21:01mixi has joined #asahi-dev
21:04SunWuKung has quit [Remote host closed the connection]
21:06SunWuKung has joined #asahi-dev
21:10Artingl has joined #asahi-dev
21:11john-cabaj has joined #asahi-dev
21:18charlie has joined #asahi-dev
21:18charlie has quit []
21:21hdbngr has joined #asahi-dev
21:28michaelrostom has joined #asahi-dev
21:30hdbngr has quit [Ping timeout: 480 seconds]
21:32aditya has quit [Quit: Connection closed for inactivity]
21:32Artingl has quit [Ping timeout: 480 seconds]
21:32SunWuKung has quit [Remote host closed the connection]
21:35michaelros has joined #asahi-dev
21:35michaelrostom has quit [Quit: Konversation terminated!]
21:36SunWuKung has joined #asahi-dev
21:36Artingl has joined #asahi-dev
21:39hdbngr has joined #asahi-dev
21:39Artinglhi everyone. i was wondering about posting my findings over the RE of ans on M3. I have made some posts on reddit, and a person suggested to write a documentation over my findings and things I did for NVMe to work on my M3 with last firmware. Should I post it on #asahi-re or here? Not sure, and seems like the RE chat doesn't have much activity. New to IRC!
21:40chaos_princessideally, send a PR :P. but sure, you can post there
21:41Artingli did RE based on kext, and was told that's generally not recommended and better to make a doc if done this way
21:41Artinglso decided to ask :)
21:41chaos_princessgoes in -re in that case
21:41Artinglgot it, thanks
21:50pb17 has quit [Ping timeout: 480 seconds]
21:51hdbngr has quit [Ping timeout: 480 seconds]
21:53noopwafelfinally got touchpad working (DT is hard), this is.. honestly very usable.
21:58john-cabaj has quit [Read error: No route to host]
21:58john-cabaj has joined #asahi-dev
21:58pb17 has joined #asahi-dev
22:37hdbngr has joined #asahi-dev
22:46fl0_id___ has joined #asahi-dev
22:48john-cabaj has quit [Read error: No route to host]
22:49john-cabaj has joined #asahi-dev
23:08john-cabaj has quit [Ping timeout: 480 seconds]
23:10SunWuKung has quit [Remote host closed the connection]
23:28michaelros has quit [Quit: The Lounge - https://thelounge.chat]
23:48pb17 has quit [Ping timeout: 480 seconds]
23:50pb17 has joined #asahi-dev
23:55Artingl has quit [Quit: Textual IRC Client: www.textualapp.com]
23:56hdbngr has quit [Ping timeout: 480 seconds]
…