2021-10-14
00:11doggkruse has joined #asahi
00:11robinp has joined #asahi
00:21doggkruse has quit [Ping timeout: 480 seconds]
01:53chadmed has joined #asahi
02:23PhilippvK has joined #asahi
02:26phiologe has quit [Ping timeout: 480 seconds]
02:53nskl has joined #asahi
02:58nsklaus_ has quit [Ping timeout: 480 seconds]
03:26marvin24_ has joined #asahi
03:29marvin24 has quit [Ping timeout: 480 seconds]
03:56kov has quit [Quit: Coyote finally caught me]
03:56kov has joined #asahi
04:22everslick_ has quit [Remote host closed the connection]
04:22everslick_ has joined #asahi
06:30marcanit's pretty much pick something that piques your interest and roll with it (e.g. how povik just picked up audio)
06:31marcankernel programming isn't particularly strange as far as systems programming goes, you get used to the style fairly quickly
06:48skali has joined #asahi
07:04skali has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:14svenyeah, if you know systems or similar low-level programming it's just a matter of getting used to how the kernel and the development process works
07:53nskl has quit [Ping timeout: 480 seconds]
07:58povikdoes linux really need to put a license-identifier on a makefile which is basically a file listing?
08:06Nspace has joined #asahi
08:15Nspace has quit [Quit: Nspace]
08:39povikworking in linux repo i cant specify just 6 characters of commit hash like i am used to :O
09:12VinDuv has quit [Ping timeout: 480 seconds]
09:24marcannow I can largely just make all the review feedback changes in my working tree, run that and rebase -i, and be done with the next version
09:30nobodynadamarcan: cool, thanks! I don't have any particular area of interest right now, but I suppose I can get it booting, poke around to learn how stuff works, and then pick something to work on
09:31nobodynadait'll probably be a fair bit of work until an M1X even boots, won't it? like it'll at least need new device trees and chicken bits and stuff
09:32VinDuv has joined #asahi
09:37nskl has joined #asahi
09:58marcanmostly just new DTs, adding chickens to m1n1, fixing any hardcoded device issues (e.g. if UART0 moved), and driver changes where incompatible changes happened
10:01chadmedonly real difference for bring up _should_ be more firestorm cores afaik. i sincerely doubt apple will bother changing anything else that does not need to be changed, especially given their knack for maintaining hardware compatibility
10:03chadmedyeah im talking just "M1X" here. pretty sure M2 will be blizzard/avalanche replacement for the M1
10:13nobodynadamakes sense! I should have been in bed 4 hours ago so I'm going to sign off for tonight, but thank you and I hope I can be at least somewhat useful :)
10:16nobodynadaI've been astounded by the rapid progresss you all have been making, and this sort of low-level programming is sort of an aspiration of mine so I'm super excited for the opportunity to learn & contribute
10:16nobodynadaTake care
10:16nobodynada has quit [Quit: leaving]
10:28marcanso apparently there's this *other* performance config framework called "interconnects" intended for memory bandwidth and such
10:29marcanalyssa: did you have the DISP0 regs handy somewhere? I want to just kill the framebuffer in m1n1 (to remove it from the bandwidth equation for testing)
11:23chadmedpovik: i might be wrong (im really stupid) but i think that is to mark the time the cpu was stolen from the m1n1 guest
11:33povikotherwise i can run outside of hv, and if i run in hv, i now know not to pay attention to stuttering
11:57alyssamarcan: don't know the DISP0 reg to kill the framebuffer the right way. powergating is probably easier.
12:32marvin24 has joined #asahi
12:35marvin24_ has quit [Ping timeout: 480 seconds]
12:58aleasto has joined #asahi
13:46jbowen has joined #asahi
13:55yuyichao_ has quit [Ping timeout: 480 seconds]
14:19jmr has joined #asahi
14:20jmr has quit [Remote host closed the connection]
14:20jmr2 has joined #asahi
14:20jmr2 has quit [Remote host closed the connection]
14:21yuyichao_ has joined #asahi
14:55psykose has quit [Remote host closed the connection]
14:55psykose has joined #asahi
15:00marvin24_ has joined #asahi
15:03marvin24 has quit [Ping timeout: 480 seconds]
15:28yuyichao has joined #asahi
15:32yuyichao_ has quit [Ping timeout: 480 seconds]
15:48bps has quit [Ping timeout: 480 seconds]
15:48yuyichao_ has joined #asahi
15:52yuyichao has quit [Ping timeout: 480 seconds]
16:34jbowen has quit [Remote host closed the connection]
16:39jbowen has joined #asahi
16:53marcanso far I found one geekbench subtest where it shows a ~8% performance gain, and I'm not so confident about it not being just noise
17:04marcan(I was going to redo it on the stream today, but I wanted to get bandwidth numbers... spent a ton of time learning that apparently the M1 is *50% slower* doing memory ops if you unroll more than 4 stp/ldp per iteration?!)
17:04marcan(then after that it turned out the bandwidth was the same either way, including on macos)
18:34Nspace has joined #asahi
18:37yuyichao has joined #asahi
18:40yuyichao_ has quit [Ping timeout: 480 seconds]
18:55Nspace has quit [Quit: Nspace]
18:58Nspace has joined #asahi
19:03Nspace has quit []
19:09houlton[m] has joined #asahi
20:00landscape15[m]marcan: Maybe it's a stupid question, but i'm curious to know why you are using Python to develop the asahi-insaller.
20:01bps has joined #asahi
20:01landscape15[m]Well, I would use C because it's more "friendly" with the hardware and there are useful libraries.
20:02jbowen has quit [Quit: leaving]
20:03landscape15[m]alyssa: I mean that it wold be easier to implement in a GUI application.
20:03landscape15[m]*would
20:05mjg59landscape15[m]: The Fedora GUI installer is written in Python. There's no need to use C for this kind of thing.
20:08landscape15[m]mjg59: Yes i agree. It's only that i don't like a lot how Python works. I'm more a Java fan for the GUI
20:09svenwe'll happily make a java (or whatever) gui installer the default if someone implements and maintains it
20:10landscape15[m]sven: Yeah but as you said it's more a pre-installer. The good part comes after.
20:13landscape15[m]psykose: It's only a prejudice. I usually think at Python as an ML language. I must learn it sometimes :)
20:13* tophevich[m]can't get "happily make default" and "a lightweight installer to have jre as a dependency" to compute
20:14sventhe "lightweight" installer needs to download 1gb or so of data anyway. it truly doesn't matter.
20:15tophevich[m]I thought java is quite "borked" on macOS
20:15nobodynada has joined #asahi
20:16landscape15[m]sven: As i saw, the installer extract the entire IPSW, but it doesn't take a long time. Only my connection is quite slow.
20:28Nspace has joined #asahi
20:34landscape15[m]I personally like Java GUI. I don't find it so terrible...
20:35landscape15[m]Moreover it works very well with OOP
20:35kovI'll say this though: starting a new project in C in 2021 should be considered a crime against humanity, especially now that we have Rust
20:35kovit doesn't make sense to choose something that lets you shoot your foot so easily at this point
20:37landscape15[m]kov: So why XNU, the Linux kernel and other OS parts are built in C? I thin it's still the more efficient for low level programming.
20:37kovon a slightly less off topic note, is there a recommended repo/branch for testing with an M1 Air?
20:39landscape15[m]j_ey: Yeah but it would be a pain to make a full transition, wouln't it...
20:39_aliceI think for a fancy GUI installer on macOS of all platforms, wouldn't Obj-C + Cocoa, or Swift + SwiftUI make the most sense?
20:39kovI was looking for something more pret-a-manger for a quick validation of my setup, then I can do that cherry-picking
20:40landscape15[m]j_ey: Yeah i'm off topic. I mean for low level programming it's still quite solid.
20:40_aliceI think it'd be pretty neat to have a fancy install flow that pre-stages the distribution installer for the next reboot after step2.sh, kinda like how there were Windows GUI installers for Linux back in the day
20:41_alice(but I think for now, the python installer is fine, given that Python is already available in the base system)
20:41j_eykov: but you can try https://gitlab.arm.com/linux-arm/jg-open/-/commits/m1-keyboard/ just to try something
20:43kovj_ey, cool, thank you, I'll give this a go over the weekend more likely, will report back if I get to a many-hacks + Air keyboard branch
20:44j_eykov: many-hacks or whatever her branch is has the pinctrl code, so you only need to cherry-pick a few from the very start of my branch
20:56j_eythose corellium ones seem pretty stable in terms of 'no-one is working on them', and then hopefully it can be replaced later on with a cleaner driver
20:58j_eyyou need https://gitlab.arm.com/linux-arm/jg-open/-/commit/c568dc078e90af2f1b6518ef9517f518d6166e9b on top
20:58j_eyand their SPI driver commit also contains the dts files, so you'll want to modify it to not include that (like https://gitlab.arm.com/linux-arm/jg-open/-/commit/0449db2db86a70cef334d7a070e6425f79b0e48a)
21:02bps has quit [Ping timeout: 480 seconds]
22:48Nspace has quit [Quit: Nspace]
22:53aleasto has quit [Quit: Konversation terminated!]
22:56yuyichao has quit [Ping timeout: 480 seconds]
23:52lonjil has joined #asahi