ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
ourdumbfuture has joined #asahi-dev
mlp has quit [Read error: Connection reset by peer]
mlp has joined #asahi-dev
JohnP has joined #asahi-dev
nicolas17 has joined #asahi-dev
gabuscus has quit []
odak_ has joined #asahi-dev
gabuscus has joined #asahi-dev
odak_ has quit [Quit: odak_]
odak_ has joined #asahi-dev
ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
odak_ has quit [Quit: odak_]
odak_ has joined #asahi-dev
JohnP has quit [Ping timeout: 480 seconds]
maria has quit [Remote host closed the connection]
maria has joined #asahi-dev
JohnP has joined #asahi-dev
<marcan>
building new kernel/mesa with the fixes from alyssa/lina from yesterday
<marcan>
I think I'll push the kernel straight to stable since it's a strict bugfix; mesa will go to asahi-dev for a bit, please smoke test and I'll push it to stable later today
<marcan>
packages in asahi-dev now
JohnP has quit [Remote host closed the connection]
<jannau>
no apparent regressions on m1 ultra or m2
systwi has quit [Ping timeout: 480 seconds]
cylm has joined #asahi-dev
nicolas17 has quit [Quit: Konversation terminated!]
hightower2 has quit [Ping timeout: 480 seconds]
systwi has joined #asahi-dev
nsklaus has joined #asahi-dev
<mps_>
also works on m1pro macbook. I don't 'see' any issue for now
odak_ has quit [Quit: odak_]
eiln has joined #asahi-dev
nimprod3l has joined #asahi-dev
eiln has quit [Quit: WeeChat 3.8]
cylm has quit [Ping timeout: 480 seconds]
midou has joined #asahi-dev
roxfan has joined #asahi-dev
ncopa has joined #asahi-dev
midou has quit [Ping timeout: 480 seconds]
midou has joined #asahi-dev
roxfan2 has quit [Ping timeout: 480 seconds]
roxfan has quit [Ping timeout: 480 seconds]
roxfan2 has joined #asahi-dev
roxfan has joined #asahi-dev
roxfan2 has quit [Ping timeout: 480 seconds]
cylm has joined #asahi-dev
mkurz has quit [Quit: Konversation terminated!]
mkurz has joined #asahi-dev
eiln has joined #asahi-dev
nimprod3l has quit [Quit: Leaving]
bps has joined #asahi-dev
bps2 has joined #asahi-dev
bps has quit [Ping timeout: 480 seconds]
hightower2 has joined #asahi-dev
cylm has quit [Ping timeout: 480 seconds]
djorz has quit [Ping timeout: 480 seconds]
mps_ is now known as mps
hightower3 has joined #asahi-dev
hightower2 has quit [Ping timeout: 480 seconds]
ourdumbfuture has joined #asahi-dev
cylm has joined #asahi-dev
ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
ourdumbfuture has joined #asahi-dev
hightower3 has quit [Ping timeout: 480 seconds]
<marcan>
no complaints, guessing it's safe to push :p
ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<mps>
my uptime after reboot is 5 hours now and everything I tested works
<mps>
now I will go to coffee break and check on j293 while enjoying coffee
ourdumbfuture has joined #asahi-dev
<mps>
fine, j293 also boot and looks like it works fine
odak_ has joined #asahi-dev
chadmed has quit [Remote host closed the connection]
chadmed has joined #asahi-dev
<marcan>
sven: what's the state of your USB3/ATCPHY rework, ignoring alt modes?
<marcan>
people keep reporting fail related to that, but it sounds like a waste of time to debug the current state of affairs
<marcan>
so maybe we should try merging just the core USB3 rework soonish
<sven>
uh, I’d have to extract the usb3 part from the thunderbolt mess
<sven>
the tipd side is mostly done
mlp has quit [Read error: Connection reset by peer]
mlp has joined #asahi-dev
ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
ourdumbfuture has joined #asahi-dev
odak_ has quit [Quit: odak_]
odak_ has joined #asahi-dev
eiln has quit [Quit: WeeChat 3.8]
ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
hightower2 has joined #asahi-dev
sid-linux has joined #asahi-dev
<sid-linux>
marcan: I have a regression to report. After going from 6.3.0-asahi-7-1 -> 6.3.0-asahi-8-1 my (hardware accelerated) chromium does not work any more
<sid-linux>
I had installed this chromium via pacman
<sid-linux>
I'm on a M2 air
sid-linux has quit []
sid-linux has joined #asahi-dev
<sid-linux>
Chromium 113.0.5672.126 Arch Linux ARM
<sid-linux>
(the current version on ALARM pacman)
sid-linux has quit []
odak_ has quit [Quit: odak_]
odak_ has joined #asahi-dev
<dottedmag>
It will help if "does not work" could be a bit more detailed.
nimprod3l has joined #asahi-dev
sid-linux has joined #asahi-dev
<sid-linux>
dottedmag: sorry -- dont have much time (gotta go). But the problem manifests itself via a blank white screen where chromium window is. stderr has a whole bunch of messages which I haven't investigated
sid-linux has quit []
<mps>
oh, I have same as sid-linux though on alpine, not asahi
<mps>
firefox works fine
<mps>
that is on X, on wayland chromium works fine
ourdumbfuture has joined #asahi-dev
odak_ has quit [Quit: odak_]
<jannau>
there are shader link errors on chromium startup
<psykose>
deleting the cache and/or the disable-whatever-arg in the thread may or may not work
<psykose>
but it could also not be the same issue
<psykose>
even though only the kernel changed it still sounds mostly like that
sid-linux has joined #asahi-dev
<sid-linux>
yes, as jannau pointed out, there are shader linker errors. e.g. [99923:99923:0615/210547.839434:ERROR:shared_context_state.cc(77)] Skia shader compilation error
<sid-linux>
My wayland chromium is not working (not tried in x)
<sid-linux>
`chromium --disable-gpu-bug-workarounds` works ! Thanks for the bug link psykose !
mkurz has quit [Ping timeout: 480 seconds]
nimprod3l has quit [Quit: Leaving]
sid-linux has quit [Quit: User exited]
mkurz has joined #asahi-dev
bps2 has quit [Ping timeout: 480 seconds]
rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
Guest2821 has quit [Quit: Bridge terminating on SIGTERM]
Jamie has joined #asahi-dev
rhysmdnz has joined #asahi-dev
Jamie is now known as Guest3184
<jannau>
deleting the chrome/chromium shader cache (~/.config/{google-chrome,chromium}/Default/GPUCache) fixes it as well
<psykose>
iirc it also goes for any electron apps (also a named cache), ..
<mps>
hm, on my j293 chromium works also with X
<mps>
s/with/under/
ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<jannau>
psykose: it wasn't just kernel changes. the mesa changes are more substantial
<psykose>
ah
mkurz has quit [Remote host closed the connection]
ourdumbfuture has joined #asahi-dev
<jannau>
2 disabled extensions: GL_ARB_texture_barrier and GL_EXT_multisampled_render_to_texture
cylm has quit [Read error: Connection reset by peer]
ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
aafeke_ has quit [Quit: aafeke_]
aafeke_ has joined #asahi-dev
ourdumbfuture has joined #asahi-dev
<sven>
nice work from agraf as usual :-) now someone just needs to reverse engineer and implement that para virtualized gfx framework :D
<milek7_>
would it require some metal-to-mesa layer?
<sven>
unclear, depends at which level their para virt works I guess
<sven>
marcan: anyway, I ripped out the thunderbolt mess and things still seem to work. I’ll clean up a bit but then I should have something ready on the weekend
mkurz has joined #asahi-dev
Tomdownsouth has joined #asahi-dev
roxfan2 has joined #asahi-dev
roxfan has quit [Ping timeout: 480 seconds]
aafeke_ has quit [Quit: aafeke_]
aafeke_ has joined #asahi-dev
aafeke_ has quit [Quit: aafeke_]
aafeke_ has joined #asahi-dev
hightower2 has quit [Remote host closed the connection]
sid-linux has joined #asahi-dev
<sid-linux>
newbie question. m1n1 has a hypervisor also as I understand it which can run macOS. What advantage would porting qemu's (new) vmapple machine type to work on Asahi?
<sid-linux>
*to work on Asahi bring
roxfan has joined #asahi-dev
<j`ey_>
run macOS vms
<sid-linux>
but m1n1 also has a hypervisor mode that runs macOS in a VM as a i understand...
<j`ey_>
yes but not from inside linux
<sid-linux>
ah
<sid-linux>
j`ey +1
<sid-linux>
Now if m1n1 is able to run macOS in a VM, surely it should be possible to write similar code to run the VM within linux? KVM gets in the way? Some other complexity?
roxfan2 has quit [Ping timeout: 480 seconds]
<ChaosPrincess>
you need to actually virtualize the hardware
<ChaosPrincess>
m1n1 passes through almost everything
Tomdownsouth has quit [Ping timeout: 480 seconds]
<sid-linux>
so basically m1n1 does not need to do the tough part of virtualizing (sharing machine between host and VM) because there is only 1 VM and it "owns" everything
<sid-linux>
ChaosPrincess: your explanation was helpful -- thanks
<sid-linux>
Another newbie question. I see references to Apple rtkit and apple mbox in very many places in code -- can someone tell me what its role is very generally.
<j`ey_>
mbox/mailbox is IPC / a way to send messages between co processors
<ChaosPrincess>
rtkit is a rtos that is used in a bunch of coprocessors
<j`ey_>
rtkit is a framework or something that is built on top of that
<j`ey_>
rtkit in linux is the api that talks via mailbox
aafeke_ has quit [Ping timeout: 480 seconds]
<sid-linux>
So rtkit in linux communicates with coprocessors running the rtkitos via the mailbox
<sid-linux>
protocol
<sid-linux>
what about dockchannel and mtp? Once I have a mental model of what these things are, it becomes easier to understand the code
<sid-linux>
(mtp = mailbox transfer protocol?)
<ChaosPrincess>
dockchannel is a fifo protocol
<ChaosPrincess>
mtp = multitouch transfer protocol probably
<ChaosPrincess>
or just multitouch protocol
<sid-linux>
mtp = multitouch touchpad on your keyboard?
<ChaosPrincess>
yes
<ChaosPrincess>
mtp/dockchannel is how the m2+ multitouch controller communicates with the main soc
<ChaosPrincess>
m1/m1x go over spi
<sid-linux>
sounds like dockchannel is a bus
<sid-linux>
but it does not seem to be listed in /sys/bus
<sid-linux>
like spi or i2c etc are
<ChaosPrincess>
point to point, not a bus and maybe?
<agraf>
sven: Yup, still looking for volunteers :)