#
✕ nick:fl0_id
#asahi-dev · 2025-05-28 13:54
fl0_idsry for the OT and confusion
#asahi-dev · 2025-05-28 13:53
fl0_idpodman, with or without desktop but on macos. that's why I only asked if this person was here sometimes originally...
#asahi-dev · 2025-05-28 13:48
fl0_idthis it at least also still the state described in podman documentation
#asahi-dev · 2025-05-28 13:48
fl0_idchadmed not for asahi, but afaik it is needed for allowing container access to the gpu (not the raw gpu, but still) I know it is OT, which is why I originally only asked if someone knew this person, as he also seemed to be involved with asahi based on their blog
#asahi-dev · 2025-05-28 13:44
fl0_id(I use "ported" very losely here)
#asahi-dev · 2025-05-28 13:43
fl0_idchadmed well, yes, it is for a year old mesa. I kind of / maybe (needs more testing) ported the patches to a slightly newer mesa used in ubuntu 24.04 lts. but if they are almost upstream I would rather use that of course
#asahi-dev · 2025-05-28 13:38
fl0_idor is that also upstream=
#asahi-dev · 2025-05-28 13:38
fl0_idalyssa thx, but I think this is a different one. I was referring to https://copr.fedorainfracloud.org/coprs/slp/mesa-krunkit/package/mesa/ which mainly seems to align some shmem parts along 16k boundary and things like that
#asahi-dev · 2025-05-28 13:32
fl0_iddoes anyone know if slopezpa / sinrega is here sometimes or what the status of upstreaming their mesa patches for apple vgpu in containers is?
#asahi-dev · 2025-05-21 16:34
fl0_idoh well guess i can wait
#asahi-dev · 2025-05-21 16:34
fl0_idstarted compiling with only one core... oops
#asahi-dev · 2025-05-21 14:36
fl0_idthx
#asahi-dev · 2025-05-21 14:22
fl0_idI was looking for it on github, but didn't see it
#asahi-dev · 2025-05-21 14:21
fl0_idwithout having asahi installed, is there an easy way to get the asahi kernel config? (for compiling elsewhere for testing purposes)
#asahi-dev · 2025-05-21 09:20
fl0_idmmh they're gone again. I could also assist with running things on m3. though tbh I didn't bother with stage2 anything yet
#asahi-dev · 2025-05-04 17:40
fl0_idsven thx. let's take it one step at a time ;)
#asahi-dev · 2025-05-04 17:40
fl0_idsven ok
#asahi-dev · 2025-05-04 16:42
fl0_idok thx for the pointers. I would have to get a diff device tree then the one linked above anyway, as I only have the m3 max
#asahi-dev · 2025-05-04 16:42
fl0_idyeah understanding would be good
#asahi-dev · 2025-05-04 16:41
fl0_idsven i haven't tried that yet but could maybe do that this week. right now I am just kind of sick and trying to distract myself haha
#asahi-dev · 2025-05-04 16:38
fl0_idsven for now I would just be happy to play around with it haha
#asahi-dev · 2025-05-04 16:37
fl0_idsven I have "confirmed" it in so far that with that, the dumping and other things work in m1n1. But I don't know enough to say if that introduces some weird errors or similar, that's why I am asking. If I remember correctly, mischa85 who did some m4 work also had to do a similar fix.
#asahi-dev · 2025-05-04 16:34
fl0_idsven yeah that's what I thought
#asahi-dev · 2025-05-04 16:22
fl0_id?
#asahi-dev · 2025-05-04 16:22
fl0_idalso wanted to check out booting a basic linux - but m3 device trees like this one https://github.com/a-ramses/linux/commit/f069376766475460a58c66d029c5dc7bb9086c6a haven't been merged in asahi-linux kernel yet, right=
#asahi-dev · 2025-05-04 16:21
fl0_idgetting back to this - https://github.com/AsahiLinux/m1n1/issues/449 does it make sense to do a PR for this, or does this need some other ADT processing patches?
#asahi-dev · 2025-04-24 12:05
fl0_idnice
#asahi-dev · 2025-04-24 12:03
fl0_idimpressive for sure. was just wondering how man ppl were hacking on it or using it
#asahi-dev · 2025-04-24 12:03
fl0_idthanks for the explanation.
#asahi-dev · 2025-04-24 11:44
fl0_idis there? (honestly curious)
#asahi-dev · 2025-04-12 18:26
fl0_idjannau oh ok, sorry
#asahi-dev · 2025-04-12 18:23
fl0_idklausklaus is lina/marcan the same person or why did you mention them both?
#asahi-dev · 2025-04-04 10:55
fl0_idyeah, not saying I'm unique haha
#asahi-dev · 2025-04-04 10:44
fl0_idmain issue for me is time and that my m3 is also my work machine, soo I cannot boot it into m1n1 that often
#asahi-dev · 2025-04-04 10:43
fl0_idyeah for sure
#asahi-dev · 2025-04-04 10:28
fl0_idsure. thx for explaining
#asahi-dev · 2025-04-04 10:21
fl0_idsven yeah deep sleep states would be rly bad :/
#asahi-dev · 2025-04-04 10:18
fl0_idand these just happen to be important bits I guess
#asahi-dev · 2025-04-04 10:17
fl0_idthx
#asahi-dev · 2025-04-04 10:17
fl0_idah ok.
#asahi-dev · 2025-04-04 09:40
fl0_idwhy do you think they even still allow raw / custom boot objects, if they apparentyl locked down M4 so tightly?
#asahi-dev · 2025-03-29 18:26
fl0_id(though not directly relevant, except for how packet logger works)
#asahi-dev · 2025-03-29 18:24
fl0_idthere is also https://www.youtube.com/watch?v=3uILiFL83v4
#asahi-dev · 2025-03-29 18:18
fl0_idjannau so if I read this correctly, there isn't any consensus in bluez yet, on how to implement this?
#asahi-dev · 2025-03-29 12:58
fl0_idjannau no I hadn't thanks. I was just going based on wiki info
#asahi-dev · 2025-03-29 12:57
fl0_idchaos_princess thx. I found that, but then wasn't sure of that was only for sending to apple and it required rebooting and it was late...
#asahi-dev · 2025-03-29 02:46
fl0_idmmh I thought I maybe had an old version, but it seems the packet logger binary stayed the same, still a 2022 version number
#asahi-dev · 2025-03-29 02:33
fl0_idyes
#asahi-dev · 2025-03-29 02:33
fl0_idnicolas17 well that's a next step. but it would be weird if it doesn't decode anything.
#asahi-dev · 2025-03-29 02:31
fl0_idI was experimenting with the bluetooth packet logger on macos for testing resume etc - is there a secret to use that app or is it know that only some combinations of software/hardware firmware work? It just doesn't give any output. kinda like this https://developer.apple.com/forums/thread/761623

plus ›