2021-09-20
01:19___nick___ has joined #asahi
02:13boardwalk has joined #asahi
02:37malvo has quit [Ping timeout: 480 seconds]
02:37malvo has joined #asahi
02:47PhilippvK has joined #asahi
02:51phiologe has quit [Ping timeout: 480 seconds]
03:17marvin24 has joined #asahi
03:21marvin24_ has quit [Ping timeout: 480 seconds]
03:29quarkyalice__ has joined #asahi
03:37artemist has quit [Ping timeout: 480 seconds]
03:37quarkyalice__ has quit [Ping timeout: 480 seconds]
03:41artemist has joined #asahi
03:43lemonsus[m]Hey, noob here. I was just a little confused on what Asahi is supposed to be or how it would work for a noob like me. So for example when I installed Linux on my x86 laptop, I just used a Pop!_OS ISO and was able to install it via USB. What would be different with Asahi? and what sort of caveats might there be with installing and using Linux on an M1 as opposed to x86?
03:45chadmedthe process for installing would be slightly different but there is an install helper in the works to make this as painless as possible. as for the second question, you may find that some of the software you use on a day to day basis has no arm64 binaries, so youll need to find alternatives. arm support is mature in most distros though so if you use your distro's repos you shouldnt find too many examples of this
03:47chadmedthe big show stopper is gaming of course, though i plan on trying some funky stuff with qemu-user once we have vulkan support just to see how viable it is. some dude on youtube got gta v's windows build working via rosetta 2 in a vm at 60 fps which is extremely impressive, but i fear qemu-user is a whole lot slower than rosetta
04:59phireyou might be interested in FEX. It's still a work in progress but it's aiming to be a much faster qemu-user
05:25marcanassuming it works well enough, that's something that would be preinstalled/configured in our arch images once we have them
05:27i509vcb[m]At least some stuff like the JVM has aarch64 support, I think it's a 4x performance reduction to run that through rosetta
05:27i509vcb[m]Likely because you have 2 layers of JIT compliation
05:28chadmedvirtually everything that people use every day will have aarch64 support if youre grabbing it from a big distro
05:29i509vcb[m]Until JDK 17 (GA 3 days ago) you actually had to use an early access build on macos to not use rosetta
05:29marcanlinux has much better arm64 support out of the box than macos, and likely will for at least a couple more years
05:30i509vcb[m]aarch64 on linux has definitely worked well in my experience, although kinda annoying that pi I had was faulty out of the box
05:30i509vcb[m]eh just rambling at this point
05:31marcanlet's just say it's, uh, been a long road to pis getting onboard the upstreaming/proper drivers train
05:31chadmedferal ghoulish piece of hardware, barely anything works properly without their proprietary blobs, downstream kernel and downstream binaries in their raspberry pi os repos
05:32chadmedmarcan: i spent a good few months doing *nothing* in my spare time but trying to get my pi 4 working with a completely upstream gentoo root, just gave up in the end
05:33marcanso now this unblocks upstreaming all the other drivers, and also thanks to the way this all works (much more nicely than the old clock framework), isn't really a hard dependency in any direction
05:34marcantoday let's see if I can debug that weirdo USB thing with an oscilloscope; then after that cpufreq which will be simple since it's using the same framework, just with frequency switching enabled
05:35marcanand I guess at that point, with sven sending off i2c etc, all I really have to do urgently is put together an asahi/devel testing branch or such, finally...
06:15maor26 has joined #asahi
07:05aleasto has joined #asahi
07:13tophevich[m]marcan: It's been some time seeing you kernal hacking on stream, might we get to enjoy one some time after the hardware debugging session?
07:16quarkyalice has quit [Remote host closed the connection]
07:26* tophevich[m]also hasn't seen you streaming kern_e_l hacking in a while :D
07:36marcantophevich[m]: kernel is what's next, I just keep distracting myself with hardware reverse engineering in preparation of :p
07:42tophevich[m]marcan: those poking sessions are very welcome, my comment should not invoke the perception that I would rate one over the other, just that if you do kernel hacking, I'd be interessted follow you on those as well :)
07:42quarkyalice has joined #asahi
07:42quarkyalice_ has joined #asahi
07:49tomtastic_ has quit [Quit: ZNC - https://znc.in]
07:49tomtastic has joined #asahi
07:50quarkyalice has quit [Ping timeout: 480 seconds]
08:05gabuscus_ has joined #asahi
08:07j_eymarcan: whats the likelyhood of stream today out of 10? (I would say low since its already 5pm, but you seem to mostly ignore time lol)
08:08gabuscus has quit [Ping timeout: 480 seconds]
08:26chadmed has quit [Quit: Konversation terminated!]
08:41awal3 has quit [Ping timeout: 480 seconds]
08:56marcanj_ey: low because I got distracted with pmgr stuff *again*... finally worked out what the clocks/events/power domains fields are (mostly)
08:57marcanthat now explains the massive init sequence that the pmgr driver does, it's scanning through all the tables that dump_pmgr.py prints and poking those registers (which are in a big array, somehow)
08:57marcannot entirely sure what those registers represent, seeing as they are homogeneous for devices/clocks/pds/events
08:59marcantophevich[m]: I normally stream whatever I do as long as I'm in the mood; I was actually originally planning to stream last night's thing but I ended up too tired, though I'd sleep, then couldn't sleep, then decided to hack on that driver anyway... not quite up for a stream at that point :p
09:04marcanalso I think I spent more time adding runtime PM to the serial driver (because sequencing and enable/disable mismatches and...) :p
09:07marcanthough so far most of that has been "finding out all the things I don't need to care about"
09:08tophevich[m]marcan: yes, most important is that you hit your groove, if a stream fits into that, it's only sugar on top. I'm not trying to push you to stream, just want to make sure you know it is appreciated.
09:08quarkyalice has joined #asahi
09:10quarkyalice__ has joined #asahi
09:10marcanI think to this day the most no-nonsense system I'd seen was the Wii, but that still has some memory init (that we never had to worry about because it was done by the stage 1 bootloader) and some PLL (?) and related nonsense (that we did, since we replaced the stage 2 bootloader)
09:14quarkyalice_ has quit [Ping timeout: 480 seconds]
09:15quarkyalice_ has joined #asahi
09:15marcantons of signed proprietary firmware that works, does its job, is behind IOMMUs so cannot backdoor the main system, and takes a ton of work off of Linux? I have no problem with that
09:17quarkyalice has quit [Ping timeout: 480 seconds]
09:17marcaneverything runs proprietary firmware; people don't generally complain about the blob in their mouse because it works and doesn't get in the way
09:20quarkyalice has joined #asahi
09:21quarkyalice__ has quit [Ping timeout: 480 seconds]
09:26quarkyalice_ has quit [Ping timeout: 480 seconds]
09:29frode_0xa has joined #asahi
09:36frode_0xa has quit [Quit: leaving]
09:37frode_0xa has joined #asahi
09:42tophevich[m]marcan: You hit the nail on the head with the example. I think this is something where we humans are very much intuitively wrong, as if we see something seperated (in our mind clearly seperated) it is "OK", because it is not part of the system. But in reality that seperation is quite arbitrary. If it is "part" of your system, the firmware seems to be software, if it is not it seems to be part of the hardware ... But as a system is by
09:42tophevich[m]definition created by many distinct parts, this distinction can only be made arbitrary and there our intuition will fall back to what we perceive physically as seperate. Also at which point is firmware, and at which point does it become software. What kind of firmware can be "seen" as "hardware"?
09:52dottedmagany* Linux sits on top of tons of immutable proprietary hardware. why single out firmware? (*except RISC-V on top of a OpenFPGA-chip that you have somehow manufactured manually?)
09:54dottedmagtophevich[m]: Is the distinction trully useful? I don't see practical differences between hardwired circuits, a resident blob in hardware, loadable firmware and a proprietary driver as long as it does not cause problems.
09:55dottedmagThe only kinda-useful difference is for pluggable peripherals, where you don't want to be running a proprietary driver on the main CPU, because you'll be limited in the set of machines you might plug this peripheral into.
10:05tophevich[m]marcan: What I'm saying (trying to) is that in most cases it is most likely not useful, but that we humans will do it anyways as we are "programmed "to do so. And as we know that is the case we need to remind ourselves of the fact that we do it intuitivly wrong in most/many cases, as we will do it on physical perception ...
10:14tophevich[m]I mean in general, regarding those topics you realy want to answer (or it boils down to), how much control do I have over my hardware, and how much control has my hardware over me. Be it data privacy, security, usability, availabilty ... That's what you want to have realy answered I think.
10:14tophevich[m]Or how much it can be trusted in to do as expected in those regards
10:54alyssamarcan: "all I really have to do urgently is put together an asahi/devel testing branch or such"
10:54alyssayou won't be able to automate this, and I've already sunk in the cost of dealing with this. go to gpu, do not pass go, do not collect 200 yen
11:12chadmed has joined #asahi
11:49leah2 has quit [Remote host closed the connection]
11:51leah2 has joined #asahi
12:41awal3 has joined #asahi
12:54frode_0xa has quit [Quit: leaving]
13:19jbowen has joined #asahi
13:43X-Scale has joined #asahi
13:49X-Scale` has quit [Ping timeout: 480 seconds]
14:03malvo has quit [Ping timeout: 480 seconds]
14:04malvo has joined #asahi
14:32malvo has quit [Ping timeout: 480 seconds]
14:33malvo has joined #asahi
14:56marcanalyssa: I'm not trying to automate this any more, I intend to just do some manual merges and call it a day
14:59skipwich has joined #asahi
15:06skipwich has quit [Remote host closed the connection]
15:07skipwich has joined #asahi
15:36j_eymarcan: getting this error when trying to run trace_gpio.py https://paste.gg/p/anonymous/b474259dedad4d55a02b8b786a60aed3
15:46Andalu30 has joined #asahi
15:47leah2 has quit [Remote host closed the connection]
15:47leah2 has joined #asahi
15:58j_eymarcan: heh i guess this is the mba trying to sleep? https://paste.gg/p/anonymous/81f41db9237c4b12a72b858f031611cf
16:01j_eymarcan: it's annoying it seems in gpio/pinctrl there's no interrupt enable/disable. you have to clear the the interrupt type to 0, so to enable it again you have to write the type out again, which means storing the type in the driver
16:14bdju has joined #asahi
16:43yuyichao has quit [Ping timeout: 480 seconds]
16:51Andalu30 has quit [Ping timeout: 480 seconds]
16:53yuyichao has joined #asahi
16:59quarkyalice__ has joined #asahi
17:00quarkyalice__ has quit [Remote host closed the connection]
17:52maor has joined #asahi
17:59maor26 has quit [Ping timeout: 480 seconds]
18:56svenmaz: uh. untested because i'm traveling, but https://f.svpe.de/b93eda6b0f58e082603e4deda93d1d3c2f2596fa7d084c491d500cfc789b1e60_dart-fix.patch might fix that
18:57dottedmagj_ey: It's a constant someone came up with to give Maltese people a letter for H sound (they have misused their H letter to mean "no sound")
19:08povik has joined #asahi
19:15sveninteresting that the DART just works. i couldn't get another stream of the sio dart to work properly (aes engine)
19:19alyssa(higher pitch than it should, and I think also faster .. so just skipping samples I guess?)
19:28alyssabut like -- for display, you can technically drive the display registers directly. but you're not supposed to, that's the DCP's responsibility
19:59kettenisstill need to sort out the dependencies for the various devices that aren't in marcan's device tree yet
20:49jbowen has quit [Quit: leaving]
21:47maz has quit [Read error: Connection reset by peer]
21:48maz has joined #asahi
21:57aleasto has quit [Quit: Konversation terminated!]
21:58povik has quit [Quit: Page closed]
22:01aleasto has joined #asahi
22:03aleasto has quit []
22:04aleasto has joined #asahi
22:10aleasto has quit [Remote host closed the connection]
22:13aleasto has joined #asahi
22:31aleasto has quit [Quit: Konversation terminated!]
23:02mindw0rk[m] has joined #asahi
23:06psykose has quit [Ping timeout: 480 seconds]
23:08psykose has joined #asahi
23:21yuyichao has quit [Ping timeout: 480 seconds]
23:33yuyichao has joined #asahi
23:46maor has quit [Ping timeout: 480 seconds]
23:49alyssaextracted 33MB of logs from the hypervisor. hopefully /something/ in this pile of needles proves useful..