#
…

2021-05-27

02:26phiologe has joined #asahi
02:29PhilippvK has quit [Ping timeout: 480 seconds]
02:55bgb_ has joined #asahi
02:57bgb has quit [Ping timeout: 480 seconds]
03:18marvin24_ has joined #asahi
03:21marvin24 has quit [Ping timeout: 480 seconds]
04:43artemist has quit [Ping timeout: 480 seconds]
04:49TypoKign[m] has joined #asahi
05:07artemist has joined #asahi
05:14s-urabe[m] has joined #asahi
05:26VinDuv has joined #asahi
06:07hir0pro has quit [Ping timeout: 480 seconds]
06:19VinDuv has quit [Quit: Leaving.]
06:23hir0pro has joined #asahi
06:51pugguu has joined #asahi
07:03pugguu has quit [Ping timeout: 480 seconds]
07:44beej has quit [Quit: Connection closed for inactivity]
08:15bps has joined #asahi
10:31choozy has joined #asahi
10:36pcm720 has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
10:36pcm720 has joined #asahi
10:44choozy has quit [Remote host closed the connection]
11:16brentr123[m]What happened to the stream?
12:24marcanbrentr123[m]: starting now :) https://youtu.be/l4fp_nBRNfw
12:24brentr123[m]Sorry I’m so impatient, I’m kind of addicted to them 😂
12:37j_eyis part of the thing that got merged the 'pmgr' and 'acpie' in the mmio output?
12:38_jannau_marcan: looks like the buffer overflow I saw on mac os
12:38_jannau_marcan: try disabling the mmio addr lookup
12:51svenmarcan: uh, does it always run on the same core?
13:01bradfier has joined #asahi
13:06_jannau_lookup_all is not used
13:07branon has joined #asahi
13:20cadubentzen has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
13:35leah2 has quit [Quit: trotz alledem!]
14:18hir0pro has quit [Ping timeout: 480 seconds]
14:18svensimd in pmgr :D
14:21_jannau_SIMD not disabled via compile flags and auto vectorization?
14:23svenfor MMIO reads/writes?
14:23svenor maybe it's not MMIO but some shared memory region for one of the subprocessors?
14:34jeh has joined #asahi
14:35jeh is now known as Guest141
14:36Guest141 has quit []
14:39jehh has joined #asahi
14:39jehh has quit []
14:40jehh has joined #asahi
14:42skali has joined #asahi
14:43_whitelogger has joined #asahi
14:47kettenismarcan: the pcie initialization code that's now in m1n1 might make macos unhappy
14:53kettenisI had u-boot hang if I repeated some of the initialization steps that m1n1 now does
14:53kettenisso I removed that code from u-boot
14:54hir0pro has joined #asahi
14:54kettenisit may make sense to only do the pcie_init later when booting a "kernel"?
14:58kettenisgood enough I'd say ;)
15:01hir0pro has quit []
15:03jkc has joined #asahi
15:04jkc has left #asahi [#asahi]
15:09jkc has joined #asahi
15:43choozy has joined #asahi
15:44jnnice work on booting to login!
15:44thunfischnice work man!
15:44thunfischthat was fun to watch :)
15:46thunfischaw yeah, rainbow apple <3
15:46jnvery nice :)
15:49skali has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:52kettenisyou're lucky that the GPU uses main memory instead f VRAM out on the PCI bus
16:00pcm720 has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
16:01pcm720 has joined #asahi
16:02arekm has joined #asahi
16:03arekm has quit []
16:03arekm has joined #asahi
16:03pcm720 has quit []
16:04pcm720 has joined #asahi
16:05arekm has quit []
16:06arekm has joined #asahi
16:06arekm has quit []
16:07arekm has joined #asahi
16:07arekm has quit []
16:07arekm has joined #asahi
16:12jixmarcan: the map_hw call still has reg.addr instead of addr (you missed undoing that one)
16:12jixmarcan: (also I think the map_sw at the top should be a map_hw, at least you said that while writing it)
16:24Andalu30 has joined #asahi
16:29jannaupmp[17] overlaps with sgx
16:37armarcan: sysctl hw.ncpu
16:43VinDuv has joined #asahi
16:51jixmarcan: missing space at the start of the string appended to the end I think
16:55Izumoo has quit [Ping timeout: 480 seconds]
16:59arhm. "networksetup -setairportpower en0 off" should disable wifi, but i'm not sure if it's gonna be permanent
17:03aralso, sysctl machdep.cpu.brand_string shows "Apple M1" here
17:03kettenismarcan: the snapshot stuff might be because the kernel panic'ed
17:04aroh, yeah, and after 3 kernel panics on shutdown it *might* want to go into a "reinstall macos" screen on next boot
17:04armarcan: ^
17:04ah-[m]interesting, it runs on one of the efficiency cores?
17:04ar(it happened to me on my work mbp13 m1)
17:07armarcan: command shift 3
17:16jehh has quit [Quit: Konversation terminated!]
17:35jannaujust kick wifi off from the ADT
17:37bps has quit [Ping timeout: 480 seconds]
17:39Andalu30 has quit [Ping timeout: 480 seconds]
17:46Andalu30 has joined #asahi
17:51Fanfwemarcan: I didn't actually mean to push you to implement the m1racles mitigation right away :-P
17:51marcantoo bad :p
17:52FanfweAt least you now have a good story to tell: Revealing the vuln, and the next day publishing software that allows to mitigate the problem
17:53Fanfwe(as long as you don't need all of your M1 cores)
17:54pugguu has joined #asahi
17:55pugguuHello stupid question but will i be able to run asahi linix on a 256gb m1 mac mini
17:55Emantorpugguu: pretty sure you can, setting it up at the moment.
17:56EmantorI'll update you when the second mac os installation is finished and m1n1 is running.
17:56j_eypugguu: that's probably the one marcan has
17:57EmantorNote that this is only interesting if you want to do driver development/hardware investigation/testing for Asahi Linux. Not really useful for general purpose computing yet.
17:58pugguuI am waiting for the boot selection menu so that i can use m1n1 but still use macos welst waiting for general purpose stiff
17:58j_eypugguu: that already works
17:59pugguuWait so i dont need a secondary computer
17:59EmantorYou'll need a second computer to run the shell/m1n1 proxy.
17:59EmantorOne could probably hack HID support into m1n1 and use the framebuffer…
18:01jnEmantor: you'd still need a machine to run the python side of m1n1
18:01jnAFAIUI
18:02jnnot a beefy machine, and not a mac (with the recent USB-ACM driver), but still something
18:03jnwhen doing something interactive with m1n1
18:07Emantormarcan: src/hv_wdt.c:5:10: fatal error: cpu_dbg_regs.h: No such file or directory
18:08Emantorbfe8c94c adds the include but not the file itself :-)
18:30hir0pro has joined #asahi
18:39h_ro[m] has joined #asahi
18:41hir0pro has quit [Quit: Konversation terminated!]
18:41hir0pro has joined #asahi
18:42hir0pro has quit []
18:48hir0pro has joined #asahi
18:50Izumoo has joined #asahi
19:02pugguu has quit [Read error: Connection reset by peer]
19:03pugguu has joined #asahi
19:05pcm720 has quit [Ping timeout: 480 seconds]
19:11hir0pro has quit [Ping timeout: 480 seconds]
19:29marcanoh that's a derp, I never used that
19:29marcanjust remove the include
19:38choozy has quit [Ping timeout: 480 seconds]
19:41EmantorYe, I found that too. Unfortunately it now refuses to boot m1n1 with a failure to boot and reverts to macOS recovery D:
19:54Andalu30 has quit [Ping timeout: 480 seconds]
20:02Andalu30 has joined #asahi
20:06choozy has joined #asahi
20:07pugguu has quit [Ping timeout: 480 seconds]
20:09EmantorNo, I am just too tired. curl <host>:8000/m1n1.macho > m1n1.macho will happily put the 404 into m1n1.macho, and kmutil does not even check whether the file your setting up for boot is a valid macho. Turns out a 404 error can't boot.
20:10* hell__can't avoid reading "macho" in Spanish (which means "male")
20:11Emantorpython3 -m http.server seems to serve nice 404 error pages, I don't remember python2 -m SimpleHTTPServer doing that.
20:11emilazyit's a deliberate pun, macho is a word in english too
20:12hell__oh, lmao
20:12jannauwould it make sense to make a CI build m1n1.macho available? https://github.com/AsahiLinux/m1n1/pull/64
20:13EmantorI am wrong, python2 also serves an error page…
20:14bps has joined #asahi
20:14jannaua little annoying that 90% of the build time is spent installing the cross compiler
20:15svensounds good to me. in the worst case it provides a sanity check that only code which actually compiles is merged. in the best case it makes someone's life easier :)
20:16Emantor17 seconds to install the cross compiler sounds fine to me.
20:16EmantorIf you want to speed this up you can probably create a container which includes the cross-compiler and have github spin this up instead.
20:16jnhell__: "Macho" has also found its way into the german language, meaning "someone who is aggressively, stereotypically male"
20:17j_eyjn: same in english
20:17jannaubuilding m1n1 just takes 3 second. let's hope azure gets Ampere Altra nodes soon
20:18VinDuvI think I remember a story about some software whose auto-updater replaced itself with a 404 page, and the resulting binary would actually cause bad things when executed
20:26pcm720 has joined #asahi
20:27hell__jn: yeah, it can also mean this in Spanish
20:28jninteresting
20:29jn(as a somewhat useless side-note, i pronounce the file format differently, as makh-o)
20:38emilazyI believe makh-o is the correct pronunciation, since it's Mach-O after all
20:38emilazybut it obscures the pun :p
20:42Andalu30 has quit [Quit: Konversation terminated!]
20:48VinDuv has quit [Quit: Leaving.]
20:58yrlfI pronounce it as in "Mach One" (as in the speed of sound), which probably is the intended association
21:00balrogit's Mach Object
21:00balrogbut maybe?
21:01balrogand yeah, emilazy I agree, I believe makh-o is correct, since it comes from the Mach kernel, and object file, back from the NeXT days
21:11Ferluci[m] has joined #asahi
21:18pinskia has joined #asahi
21:22fff has joined #asahi
21:24fffhello all
21:24fffwhat do we know about the SEP?
21:24fffparticularly the interface it exposes
21:26jnthe first step would be to document the interface :)
21:27jnnot sure how much documentation exists at the moment
21:35fffwell i am curious if in fact, one day, i will be able to use it from linux to e.g. hold ssh keys
21:35fffi guess that's still an open question then
21:35sventhat's the goal at least
21:35svenit should be possible since you can use the SEP from mac os for ssh keys
21:43fffand the current state is that there's some memory-mapped region presumably for communication with the SEP and not much more known that that?
21:43fff*than that
21:43svenpretty much. i've seen some slides about the mailbox protocol though
21:44svenbut that's the easy part
21:45fffwhere can i find those slides? :)
21:45svendon't remember, sorry :-)
21:45fffthat's okay
21:45svenbut iirc i googled for secure enclave mailbox or something like that
21:46svenbut the registers looked very simple. it's probably obvious how to send messages from looking at a single mmiotrace
21:50pcm720 has quit [Ping timeout: 480 seconds]
21:50fffthese would be the slides probably
21:50fffalthough i might prefer reading mmiotraces to reading slides
21:50ah-[m]what's the hard part?
21:51svenfiguring out the protocol itself and then figuring out how to nicely integrate that into the whole gpg/ssh/etc. ecosystem
21:52svenand yeah, those look like the slides
22:02fff has quit [Quit: Page closed]
22:07rkjnsn[m]Just out of curiosity, I see that the goals for Asahi include not just hardware functionality but also polish.
22:07rkjnsn[m]Is, e.g., taking advantage of the P3, 500nit display for HDR playback in scope as part of that polish?
22:11mjg59rkjnsn[m]: The state of HDR in Linux overall isn't great at the moment
22:12mjg59Other than the extent that there's GPU support required, I think it's probably out of scope
22:12choozy has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
22:23kettenis_ has joined #asahi
22:25kettenis has quit [Ping timeout: 480 seconds]
22:35pcm720_ has joined #asahi
22:55yrlfI guess that if they find out how the needed GPU support for HDR works, they'll add it to the driver, but toolkit and application support for HDR is very "not there" yet on linux so I don't expect that to get further soon
22:56emilazycolour management on linux is very bad :(
22:56emilazywayland may improve it at some point in the future
22:57emilazythe only thing you can really do is assume every application is in sRGB unless you have good reason to believe otherwise
22:59yrlfthere is a work in progress protocol specification for color management for wayland
23:00yrlfthough that specification is still missing details for HDR, mostly color space stuff until now
23:08arlast time i tried wayland (sway and gnome3 around february), i hit a lot more serious bugs than "colorspace management is wrong"
23:08arlike, with multiple monitors connected, menus in some apps ended up waaaay off
23:35emilazycolourspace management being wrong can be pretty bad
23:35emilazyit means that linux gui is inevitably super oversaturated and weird looking on many displays
23:35emilazywayland's multi-display story is ... in theory better than X's by quite a lot
23:35emilazybut Xwayland probably has issues with it I imagine
23:36aralso, does wayland still have 24bit colorspace hardcoded?
23:37ari vaguely remember it being the case that 8b/ch/pixel was hardcoded in the protocol around 2 years ago
…