#
…

2022-08-22

00:31benpoulson has joined #asahi-dev
00:56jluthra has quit [Remote host closed the connection]
00:56jluthra has joined #asahi-dev
02:05benpoulson has quit [Remote host closed the connection]
02:21marcanjannau: apparently the reason those PRs were ignored is because there was something wrong with them
02:21marcanand the maintainer's approach to that is to just... ignore them?
02:21marcan"I fixed and committed the 16k PRs, but this will be the last time that I do so." (direct quote)
02:22marcanthis... does not give me confidence about this upstream :(
02:22marcanI hope he reconsiders and tries to work with us, or I might be seriously tempted to move to Fedora or something... we can't work with "if your PR is wrong it gets ignored" :(
02:35amarioguy has quit [Remote host closed the connection]
02:35amarioguy has joined #asahi-dev
02:41gff has joined #asahi-dev
02:44gff_ has quit [Ping timeout: 480 seconds]
02:45alyssa has quit [Quit: leaving]
03:17PyroPeter_ has joined #asahi-dev
03:18PyroPeter has quit [Ping timeout: 480 seconds]
03:27a_plastic_bag has joined #asahi-dev
03:30jialixu[m] has joined #asahi-dev
03:38a_plastic_bag has quit [Quit: WeeChat 3.6]
03:58benpoulson has joined #asahi-dev
04:06benpoulson has quit [Ping timeout: 480 seconds]
04:22nehsou^ has quit [Remote host closed the connection]
04:22nehsou^ has joined #asahi-dev
04:42kettenis has joined #asahi-dev
05:18benpoulson has joined #asahi-dev
05:20chadmedsuddenly glad i took the time to get gentoo working properly(tm) then...
05:20chadmedwhat an awful attitude
05:26benpoulson has quit [Ping timeout: 480 seconds]
05:35paulywog has joined #asahi-dev
05:43jannauI fear it's short-sighted strategy to deal with too much work. it might also work long-term by driving users away
05:45jannauI'm still confused why everyone seems to be happy with support for a different architecture is another distribution
05:46chadmedthe arch community is just like that
05:46chadmedits user base exists in spite of its hostile and insular community, not because of it
05:47the_lanetly_052 has joined #asahi-dev
05:47chadmedthe arch heavyweights who make these decisions probably just think arm is "soy" or whatever these types are saying about anything-that-isnt-a-pc-with-dwm systems these days
05:48paulywog^^ people who haven't yet left a twitch stream running on battery overnight and come back to their laptop still solidly charged
05:49chadmedno dude a thinkpad with an 800mhz centrino in it is more chad and based ok dont ask questions it just is
05:50paulywoganyone know what's been "started" with the hwmon driver in the yak shaving section? It's likely something I could poke at but I don't know if someone has mostly completed it and just has it stashed on some branch
05:51chadmedhavent heard anything on that front since the person edited the page initially
05:51chadmedit should be simple enough to do even as an exercise if you want to, we already have SMC support you just need to grab the keys out of it and tell hwmon what each of the keys are in terms of sensor readings
05:52paulywogyeah I've already looked at macsmc_power, looks pretty straightforward
05:53mpschadmed: on alpine we are trying to work equally on all 7 arches, and now also riscv
05:53paulywogare these still the best guesses we have for smc keys? https://github.com/AsahiLinux/docs/wiki/HW:SMC
05:54chadmedmps: same with gentoo
05:54chadmedcheck the python stuff in m1n1 for the most up to date list of keys
05:54mpschadmed: it doesn't always work well, and some arches have some problems but we don't ignore these problems
05:54mpsyes, I know that gentoo people also does same
05:55paulywogthanks for the lead chadmed, that'll be helpful
05:55fp has joined #asahi-dev
05:55paulywogfigured there was likely to be something more
05:56chadmedyou can make m1n1 dump out the keys with their current values so that will probably be the best place to start for finding which is which for stuff not listed on the wiki
05:58veloek has joined #asahi-dev
06:01paulywoginteresting, I thought m1n1 was a bootloader, but it's clear there's more to it
06:03fp1 has joined #asahi-dev
06:07fp has quit [Ping timeout: 480 seconds]
06:08pjakobsson has joined #asahi-dev
06:12paulywog has quit [Quit: leaving]
06:17the_lanetly_052__ has joined #asahi-dev
06:23the_lanetly_052 has quit [Ping timeout: 480 seconds]
06:45Dementor[m]marcan: did he say what was wrong with it? Or give you chance to fix it?
06:46marcannope, he just fixed them himself so I guess now we get to diff the original PR and what was committed and learn from the diff...
06:47marcanmy email was about helping out because I thought he was overworked and that's why the PRs hadn't been looked at in 5 months, and he fired back with that. I'm concerned.
06:49marcanI'd go with Gentoo but "compile everything yourself" just isn't practical for the average user, and I'm not going to sign up to maintain a golden /etc/portage and binhost
06:49jannauthe rust and jemalloc changes were indeed wrong since we forgot that alarm supports armv7-a as well
06:50marcandoesn't really matter *why* they were wrong if he doesn't tell us... and we can't work with a "submit a PR, and guess it might be wrong if it doesn't get merged in 2 weeks" dynamic
06:50marcanI really, *really* hope he changes his approach, because if not I'd much rather pull the rug out under our users now and switch distros than do it years down the line
06:50jannauI'm also not overly impressed with the handling of PRs/commits. if you look at the commit that resolves marcan's grub PR https://github.com/archlinuxarm/PKGBUILDs/commit/15b480acd04092052205b7580e3c976d41ad524d
06:51marcanyeah, not acknowledgement either, which is *shrug* given the triviality of the patch but not nice
06:52jannauthe only change was changing pkgrel to 1.1 instead of 2 but it's a new commit by kmihelich although it's otherwise the same commit
06:52marcanI don't think the pkgrel thing is even documented?
06:53jannauand I think most PRs are resolved in that way
06:56jannauthe commit that closes the libunwind PR with the unreleased dynamic page size support removes something unrelated too
07:14marcanGlanzmann: I occassionally have to deal with Debian packaging for a side gig and I have no interest in making it part of my main job, sorry ;)
07:14GlanzmannWorth a try.
07:15marcanplus Fedora have been the first and so far only distro to offer to support these platforms officially, and that is *very* important
07:15marcansince our goal is to cease to exist
07:15marcan(that said, I've never used Fedora, so I'd have to try it)
07:16marcan(OTOH I *did* have to mess with Fedora packaging once for a Ceph PR, and that was not too painful)
07:16dottedmagGlanzmann: That process took me 2 years
07:16dottedmagGranted, it was a long time ago
07:17marcanmy project lead spidey-sense points towards Fedora too right now, for whatever that's worth (but I think it's served me well so far ;)
07:17mpsiirc I was few times on debian new maintainer process but didn't finished any, too burauecratic
07:17marcanyeah, bureaucracy is the last thing we need
07:18mpsI would say that alpine because it is similar to arch, but alpine uses musl so I think most people will feel not comfortable with it
07:19Glanzmannmps: I considered once to become a Debian maintainer, but than dropped it. But I have a good friend who would sponser me, if I want to go ahead with it.
07:20marcantoo niche for desktop use and we don't need even more exotic choices that can cause software to break (sorry Ariadne)
07:20mpsmarcan: yes, I agree
07:20marcanAsahi isn't supposed to be opinionated about anything. Heck I went with Arch because it basically isn't, it's largely just unmodified upstream packages.
07:21mpsand also I wouldn't be pleased to work on help to newcomers who want ready-made big DEs
07:21marcanGentoo is not practical, so that leaves Debian and Fedora really, unless I forget about some other major distro
07:22mpswell, imo arch is quite fine
07:23marcanarch is quite fine if we can get things upstreamed and work with the maintainers. apparently, that might be a problem..
07:24mpswell, I fear you will meet same or similar with other distros, sooner or later
07:24marcanso far every Fedora person who has talked with me has been nice, and they've shown *active* interest in supporting these platforms, which is a far cry from ignoring PRs
07:25marcanALARM is basically just one guy running the show, and if that one guy doesn't want to work with us, we have a problem :(
07:25mpsime debian is too slow for accepting new things and changes
07:25marcanbut I bet at least they'd fix bugs faster than 5 months
07:28mpsGlanzmann: yes, debian people are good ones. but process and rules, uhm
07:31mpsoh I forgot, postmarketOS people works on using apple silicon also, didn't looked much how far they are now
07:32marcanthat's an alpine derivative
07:33marcanand apparently focused on phones
07:33mpsyes, but they added these different DEs
07:34marcanwe're not going to chain off of a second-level distro, that makes even less sense
07:34mpsand not only on phones, but also on arm notebooks
07:35mpsalarm is also some kind of second level distro
07:36mpsbut yes, I agree that for anything based on musl will make a hassle
07:38nehsou^ has quit [Ping timeout: 480 seconds]
07:38nehsou^ has joined #asahi-dev
07:42dottedmagmarcan: the only another large first-level distro (that is, coming with its own package repository - you mean that by first-level, right?) is openSUSE, everything else seems very niche. So yeah, looks like Fedora is the only viable candidate.
07:44marcanyeah, I forgot about SUSE :)
07:44marcanbut then again, one of the people pushing for Fedora support for us is... on the OpenSUSE board... so I'll take that as a sign that we should go with Fedora
07:53as400[m]Guys, is decision of changing a distro already taken ? Or it's just discussion ?
07:53kazukih[m]What about Manjaro?
07:55kazukih[m]Then you can just use the pkgbuilds you made for alarm without changing much
07:55AdryzzOLEDEdition[m]11manjaro relies on ALARM
07:56kazukih[m]Huh, I thought they had different maintainers
07:57as400[m]The only thing that would be lost going with Fedora would be ALARM rolling characteristics
07:58kazukih[m]Ah looks like a big chunk of Manjaro-arm stuff is based on alarm, my bad
08:03marcanFedora does have Rawhide and apparently updates mid-cycle for the most part, even in the regular releases
08:04marcanas400[m]: Discussion
08:06as400[m]marcan: ok, asking out of curiosity. I do know the pain though.
08:08marcanbut it really does come down to Kevin's handling of this situation, because if we're going to switch base distros, I'd much rather do it now than a year down the line when we have an even bigger userbase
08:08marcanso let's hope he reconsiders his PR strategy, and otherwise, I'm going to start looking into Fedora
08:11as400[m]Everything you wrote above in this discussion is perfectly understandable. And if you're forced to do a switch, doing it early as possible would be beneficial for sure.
08:15Chainfire has quit [Remote host closed the connection]
08:20conradev8 has quit [Quit: -]
08:21conradev8 has joined #asahi-dev
08:26leitao has joined #asahi-dev
08:28benpoulson has joined #asahi-dev
08:35dottedmagHopefully year down the line the switch will be "remove the distro bits, all upstreamed" :)
08:37marcanyup, that's the hope
08:37marcanand Fedora already has a PR for adding the upstreamed Asahi bits to their kernel, so that's a start!
08:38marcanthough we'll probably forever be a bleeding edge repo anyway, so the switch will be more like "you can now drop the asahi repo if you want a stable distro"
08:38marcanand we'd probably only offer the non-asahi image in the installer, and users can add the extra asahi bleeding edge repo if they want
08:38marcanmuch like asahi and asahi-dev today
08:48benpoulson has quit [Remote host closed the connection]
08:48benpoulson has joined #asahi-dev
08:52Dcow[m]I personally like Fedora and been using it for long time. Gentoo is one love, but it too time consuming.
08:52Dcow[m]But what about fedora on ARM? it is binary distro, so we have to consider richness of the repo?
08:52chadmedits as mature as alarm is and better maintained
08:54as400[m]chadmed: does fedora have something similar to aur ? Or any user maintained repos ? I haven't used it for years now.
08:54Dcow[m]Fedora Workstation is default to Gnome, how about that?)
08:54chadmedbesides the more important thing right now is willingness to cooperate on repo maintenance. if the maintainers are more proactive and hospitable with their merge policy, then growing the repo wont be too much of an issue
08:55chadmedyou can use rpm fusion on fedora which is basically the proto-aur anyway
08:55chadmedand there are also spins of fedora with all the major DEs so its not like you _have_ to use gnome
08:55chadmeditd be the first thing i yeet off my system if i ever migrated
08:55chadmedbut i spent all that time on gentoo enablement for a reason
08:58c10l has quit [Quit: Bye o/]
08:58as400[m]looking at the fusion repo it has huuge number of packages so nothing to worry about
08:58Dcow[m]>> and there are also spins of fedora with all the major DEs so its not like you _have_ to use gnome
08:58Dcow[m]I am OK, it was more a joke targeted marcan, since he is so much KDE fan =)
08:59chadmedi imagine he will end up dailying gentoo on these machines sooner or later regardless
09:00marcanI would probably still ship the desktop image with KDE preinstalled because I'm that kind of person ;)
09:00joske has joined #asahi-dev
09:00j`eyhow much is KDE paying you? :P
09:01joskewhat about manjaro? Or will that have the same issues? (been using that since October)
09:01c10l has joined #asahi-dev
09:01marcanmanjaro is just arch plus breakage
09:01benpoulson has quit [Remote host closed the connection]
09:01benpoulson has joined #asahi-dev
09:03joskehahaha oops
09:03Dcow[m]Linus using Fedora AFAIK, so one more point to it
09:03as400[m]yep - manjaro is hopeless
09:03joskeI used to use redhat until 1999 or so, now fedora you even need to reboot to install updates!
09:03marcanLinus' distro choice is largely irrelevant to us, but yes, that is a convenient bonus
09:05benpoulson has quit [Remote host closed the connection]
09:07benpoulson has joined #asahi-dev
09:09Dcow[m]joske, well you don't have to
09:10chadmedthe standard fedora images arent immutable
09:10chadmedonly silverblue is
09:11marcanchadmed: I honestly wonder whether I'll end up on Gentoo or not, it depends on what's available. e.g. ALARM actually had more proaudio stuff than Gentoo sans overlays.
09:11marcansometimes it gets tiring fixing the weekly build problems on my buildhost
09:11chadmedtrue actually, theres still no ebuild for carla in the main gentoo tree
09:12chadmedmight have to fix that on the holidays...
09:12marcanso there's a chance I'll get used to Fedora or what have you... though I probably will keep Gentoo on the servers because I'm comfortable with that (and my server binhost chroot is the least troublesome one, since it's not ~amd64 and has much fewer packages/USE flags)
09:13marcanALARM's carla crashes opening zynaddsubfx, I found that out yesterday, but a source build works fine. OTOH, it's not saving the zyn/drumkv1 preset data... I feel like somehow Carla is always broken for me in some way
09:13marcan(not saving plugin data, not saving the patchbay layout, *something*)
09:13marcanI'm supposed to be a maintainer for the gentoo audio-overlay, but these days I have ~zero time for that...
09:13marcanalready dropped proxymaint for the couple packages I had because I just can't attend to bugs
09:20marcanthe main benefit of gentoo for me right now on desktop is ease of patching, but if I can figure out Fedora package builds, that doesn't really matter for fixing things broken today. that leaves "long-term" patches
09:20DmitrySharshakov[m]Why did you drop openSUSE from the discussion?
09:21marcanlooking around my /etc/portage... it's all build fixes or things I don't care about, except for one specific patch: a hack for kwin to disable Night Color on external outputs, so it doesn't affect my stream (a problem I had early on)
09:21marcanI can probably figure out how to make that a properly developed setting/patch and upstream it in less time than I spend babysitting my desktop binhost, tbh
09:21leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:22marcan(or maybe once I move to M1 there will be enough free CPU to just do the stream capture/forwarding in software rather than hardware)
09:22marcan(ooh, cute idea: thunderbolt support for efficient computer-to-computer screen capture)
09:22marcan(dma-buf over thunderbolt anyone?)
09:23DmitrySharshakov[m]I have sometimes looked at it and it's great for custom builds (OBS), also pretty beginner-friendly. I use Fedora on my computers, but am looking at openSUSE MicroOS as a great distro for some future systems. Overall openSUSE Tumbleweed should be a decent alternative to Arch, as Fedora Rawhide is not a rolling distro but a testing platform
09:23marcanmostly because no openSUSE people have showed up to propose Asahi support, while Fedora people have :)
09:24DmitrySharshakov[m]`(dma-buf over thunderbolt anyone?)` I've seen network over TB in default Linux. I guess it used some sort of shared memory thing
09:24marcanupstream interest matters a *lot* here
09:24DmitrySharshakov[m]Well, yes, that's true
09:25_jannau_fedora has handled the libglvnd BTI fix in a timely manner: https://bugzilla.redhat.com/show_bug.cgi?id=2111900
09:27DmitrySharshakov[m]marcan: it appears thunderbolt-net is a real RDMA-over-Thunderbolt. https://github.com/torvalds/linux/blob/master/drivers/net/thunderbolt.c#L593
09:27marcanyes, I'm aware
09:27marcanhence dma-buf over thunderbolt
09:28DmitrySharshakov[m]If memory is unified then passing a GPU memory BO shouldn't be a problem
09:28marcanthere's no such thing as GPU memory, it's unified
09:28DmitrySharshakov[m]Yes, I meant memory object related to GPU work
09:30DmitrySharshakov[m]Can it be possible for at least compute workloads running on eGPU? I heard that the issue is like lack of GTT support in M1/M2 PCIe controller?
09:30DmitrySharshakov[m]Or what is lacking for it to work really?
09:31marcanthe issue is there is no mapping GPU memory as normal memory
09:31marcanwhich is going to affect compute workloads even worse most likely
09:32marcane.g. you can't use unaligned loads/stores on VRAM, no cache, etc.
09:32mpsheh, interesting discusion about distro. didn't knew so much problems exit. could be because I use alpine which works out of the box from the beginning and don't have these problems ;p
09:32DmitrySharshakov[m]So textures/other buffers have to be copied since they cannot be placed into a memory area usable for both SoC and GPU?
09:33chadmedthe only real distro-related issue ive had in the past like 6 years is having to sed -i s/unwind/llvm-libunwind/ the samba ebuild every system update
09:33chadmedbut thats my fault for not reporting upstream that it works and they can stop hard depending on libunwind
09:33leitao has joined #asahi-dev
09:34dottedmagmarcan: Any ideas already what to look at for local patching on Fedora? I was looking for setting up a way for Gentoo- or NixOS-like local customizations, but with a more mainstream distro.
09:34dottedmagmarcan: Or rather, please share if you find anything usable or make one.
09:35marcansilverblue is also a point for fedora, since several people have asked about a macOS-like secureboot setup for Linux, and that's never going to happen with ALARM
09:35marcanbeing able to just drop that in and build a neat little secureboot setup when we get there would be *really* cool, even if not that many people actually use it
09:35marcan(macOS-like as in immutable system volume)
09:35marcan(obviously we will support more traditional secureboot setups for everything, relying on FDE for security)
09:36mpschadmed: oh, I have issues ofc, but I try to find bugs, fix, report upstream etc
09:36marcanso far I've only had problems getting things upstreamed with ALARM, and funny enough, Arch itself, though my sample size there is 1
09:37marcanGentoo depends on who the package maintainer is, but they will usually take PRs pretty quickly
09:38mpsbtw, for pkgs I maintain in alpine I often look in alarm and Arch to find some ideas or solutions
09:38DmitrySharshakov[m]`macOS-like secureboot` - like setting up an immutable volume with dm-verity etc? Yes, that's quite a great concept
09:38DmitrySharshakov[m]marcan: I also wanted to chat a bit about some ideas about secure boot
09:39mpsif that issue with Kevin could be solved in fine manner I don't see strong reason to change
09:40marcanlet's see what his reply is
09:40chadmedyeah but... can it?
09:40marcaneither way, my intent was always to have several official supported distros, and regardless of whether #1 on the list is ALARM or not, I am interested in seeing Fedora get more official support
09:41DmitrySharshakov[m]Secure boot trust chain can have various implementation and that also makes a factor for distro choice: how breaking would out secure boot policy changes be
09:41marcanthe secureboot chain hands off to m1n1 and after that we can do/trust whatever we want
09:41DmitrySharshakov[m]Probably with some U-Boot patches it can be made to support sort of true UEFI-standard secure boot
09:42DmitrySharshakov[m]The root of truct is m1n1-1 baked into boot policy
09:42chadmedideally and eventually it will be the SEP
09:42marcanthe SEP is involved in FDE but not really secureboot
09:43chadmedwe couldnt use it to store keys/hashes of payloads?
09:43DmitrySharshakov[m]Well, but I guess reversing the SEP is less trivial and might take a long to be really secure and more important - reliable
09:43marcanI'm not sure UEFI-standard secure boot is necessarily the best idea here... at the point where you have a fully integrated secureboot distro, it might make sense to just start bundling up m1n1-stage2+u-boot+kernel+initramfs into one image, signing that to be loaded by stage1, and calling it a day
09:43DmitrySharshakov[m]But quite a great security can be accomplished even without any SEP driver
09:44DmitrySharshakov[m]marcan: Yes, it can be like that
09:44marcanchadmed: not really, it requires the xARTS stuff for storage and I don't see us putting an APFS driver in u-boot
09:44chadmedoh yeah of course
09:44marcanSEP is primarily useful for protecting mutable user data
09:44marcanit is not really involved in secure boot beyond the bootpolicy stuff
09:44the_lanetly_052__ has quit []
09:45DmitrySharshakov[m]Since emulating all the MOK dances can be quite demanding and it's easy to do something wrong implementing that spec
09:45marcanUEFI secure boot is a shitshow, and the nice thing about this platform is we can bypass that
09:45marcanyou'd want a locked down u-boot that just boots an embedded kernel and that's it
09:45marcanno USB or NVMe drivers
09:46DmitrySharshakov[m]But we want to retain the GRUB/sd-boot I guess, so not welding m1n1-2+u-boot+kernel+initrd, as if kernel update breaks something I'd like to be able to choose previous one
09:46marcanthen the only secureboot-relevant component before the kernel is m1n1, and that's why that part of the code is written in Rust
09:47marcanthat's a fair point, but a bit tricky... and at that point, it might actually make sense to make m1n1-stage1 able to boot multiple stage2s. That also, conveniently, solves the device tree incompatibility problem, by allowing separate DTs for each kernel.
09:47marcanadding a little menu that just looks for files in /m1n1/ would be pretty trivial, and can be done securely in the Rust code
09:47DmitrySharshakov[m]Also I've once opened a question issue on GH whether booting m1n1 test builds on emulators would be easy enough. That'd help interested people without hardware (like me huh) to do hw-independent stuff and maybe autotests and fuzzing
09:48marcanit isn't, because m1n1 relies heavily on Apple-specific features
09:48marcanits entire purpose is to deal with all the Apple-isms
09:48DmitrySharshakov[m]marcan: And then conventional bootloader is gone completely? So m1n1-1 -> choice -> m1n1-2 -> u-boot + kernel + initramfs bundle is the boot sequence?
09:49DmitrySharshakov[m]marcan: Well, like I expected. feel free to close or I can do that
09:49chadmedits easy enough to build a new stage2 from userspace that this really isnt the hinderance that it used to be with all the kmutil nonsense
09:49chadmedupdate-m1n1-secureboot or some such
09:50marcanyeah, though for a "distro-managed" secureboot distro, the distro would do that in a single package anyway, and ship it pre-signed
09:50marcanfor a "user-managed" mode they'd keep their own private key, but then we need some way for the installer to securely pass that into the installed OS, which is at least a little bit tricky
09:51marcan(unless SEP is involved, but I don't see pulling that off from macOS being easy...)
09:51DmitrySharshakov[m]So probably for now we need that bootpicker in m1n1 and a more generic package for handling all the userspace stuff. Well, an utility like sbsign or update-grub which will weld m1n1-2 and all the subsequent parts together, then go to ESP, ask user's password to decrypt the private key, sign and store things
09:51marcansomething like that, yes, for a user-managed version
09:51DmitrySharshakov[m]marcan: Was going to write my ideas
09:51benpoulson has quit [Remote host closed the connection]
09:51marcanif using distro-managed public keys it'd be done by the distro
09:51marcan(like apple does)
09:52benpoulson has joined #asahi-dev
09:52DmitrySharshakov[m]We can use AES + password-derived key I guess. recoveryOS part of the installer generates the keypair, burns pubkey into m1n1-1, and encrypts private one to be stored in the ESP
09:53DmitrySharshakov[m]Or gpg can be bundled into the part 2 of the installer to accomplish the job
09:54DmitrySharshakov[m]This way we get a machine-owner-password-encrypted private key for signing. On updates machine owner has to confirm the action by entering their password
09:55DmitrySharshakov[m]Or some keyslot madness can be implemented, so in case multiple users are present they all can unlock the keyfile
09:56benpoulson has quit [Remote host closed the connection]
09:56marcanthat's a bad idea, it lowers the security guarantees of the platform
09:56DmitrySharshakov[m]Can we run a custom Rust binary in recoveryOS for the sake of simplicity?
09:56leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:56DmitrySharshakov[m]marcan: What of those exactly?
09:57marcanit's not possible to guarantee secure erasure of such a key file (this is why apple have effaceable storage), and therefore you potentially forever tie the security of secureboot to the user password, even if they change it
09:57marcanLUKS at least *tries* to be a bit better than doing it the naive way by hashing a bunch of random data IIRC
09:57marcanbut if we can do SEP-backed FDE that's much better and solves this problem
09:58marcanideally we figure out some SEP voodoo to allow wrapping the key file with that in macOS in a way that is then accessible again from Linux, but I'm not entirely sure that's possible, though it ought to be, since FileVault works like that?
09:58marcanthis needs more research
09:59leitao has joined #asahi-dev
09:59marcanand it doesn't help that we can't hit raw SEP APIs from macOS as far as I know, only the public ones
09:59DmitrySharshakov[m]Hmm, so we can have separate profiles (like full and reduced security)
10:00marcanit's possible that the ticket ends up being creating a tiny FileVault-enabled volume in the stub partition, sticking the key material in there, and then reading it from linux
10:00DmitrySharshakov[m]full security just enforces use of distro-provided kernel+initrd, will require support from distro
10:00marcanthat should definitely work, doesn't require any funny primitives from macOS, etc
10:00marcanit just means we need to support APFS and SEP enough to mount FV-enabled volumes
10:01DmitrySharshakov[m]and reduced security is for those who want custom builds, they have a password-protected key story
10:01marcaneither way, this is relatively far in the future :)
10:01marcanwe'll see once SEP support starts taking shape
10:02DmitrySharshakov[m]`it just means we need to support APFS and SEP enough to mount FV-enabled volumes` are you sure SEP container stuff doesn't restrict that? Or it'll be like encryption of an external drive?
10:02marcanit does not, pretty sure you can log in and mount a separate OS's Data volume as long as you can log in as a valid user
10:03chengsun_ has joined #asahi-dev
10:03marcanI think they are stricter on iOS though
10:03DmitrySharshakov[m]marcan: Couldn't we do some sort of secure boot (with a password-protected key) to improve quality now and then replace it by SEP-backed hardware security?
10:04marcanah, but wait, FV requires full security, doesn't it? :/
10:04marcanwell, maybe it doesn't for non-OS volumes
10:04marcanI guess this needs testing
10:07chengsun has quit [Ping timeout: 480 seconds]
10:08isoriano has joined #asahi-dev
10:11DmitrySharshakov[m]At least that 'first approach' I suggested gives the same degree of security as custom sb keys on PC platforms. Btw you could also store the key on external media or do a secure erasure of the key material when changing the password
10:11fp2 has joined #asahi-dev
10:14marcan"secure erasure" isn't a thing on SSDs
10:14DmitrySharshakov[m]and when a better approach is ready (SEP-backed wrapping), then you free up some space in the container, do a trip through recoveryOS and enroll the new m1n1 then wrap its key in a new fashion
10:14marcanhence apple's effaceable storage stuff
10:16DmitrySharshakov[m]Well yes. But the risk is still low enough for casual users and attacker will have to desolder NAND to take a look at lost fragments of a broken cryptocontainer (which first has to have a compromised password or cryptography)
10:18fp1 has quit [Ping timeout: 480 seconds]
10:18DmitrySharshakov[m]And for high-value cases a config option can be set to store the key on external media which can be wiped better
10:22chengsun_ has quit [Quit: Quit]
10:22chengsun has joined #asahi-dev
10:22joske has quit [Remote host closed the connection]
10:37benpoulson has joined #asahi-dev
10:38leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
10:41leitao has joined #asahi-dev
10:44benpoulson has quit [Remote host closed the connection]
10:45benpoulson has joined #asahi-dev
10:52nehsou^ has quit [Ping timeout: 480 seconds]
10:52nehsou^ has joined #asahi-dev
10:54yrlf has joined #asahi-dev
11:17leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:32leitao has joined #asahi-dev
11:35benpoulson has quit [Remote host closed the connection]
11:37benpoulson has joined #asahi-dev
12:02leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
12:10leitao has joined #asahi-dev
12:11the_lanetly_052 has joined #asahi-dev
12:23isoriano has quit [Remote host closed the connection]
12:32svenso i've wondered for a while why DP mode seems to have less tunables in the ADT than all the other modes
12:32sventurns out it's because for some reason Apple decided to just put the "missing" DP tunables directly into the kext
12:33mia_ has joined #asahi-dev
12:34arDP as in displayport?
12:37povikwhy did i expect a reply like that
12:37mia_ has quit [Remote host closed the connection]
12:39mia_ has joined #asahi-dev
12:39povikcan't we just shove these <150 lines in kernel and be done with it?
12:42Ariadnemarcan: i mean, i don't disagree?
12:43Ariadne(though i think on an architecture like aarch64, the need to care about compatibility with GNU/Linux is largely irrelevant)
12:45marcanpovik: :/
12:46marcanAriadne: :)
12:50povikyeah it's not going in
12:50povikso i guess that goes in my _archive/
12:50Ariadnemarcan: my only problem is when for-profit companies decide to slag alpine to get customers for their image lobotomization product ;)
12:51Ariadne(or when the same people did this years ago to sell ubuntu advantage)
12:51marcanI know, I know :)
12:52Ariadnealpine is designed from the position that people are already quite familiar with unix-like systems, so using something that is more straightforward means less work is needed to polish it
12:52* Ariadneshrugs
12:57leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
12:59leitao has joined #asahi-dev
12:59leitao has quit [Remote host closed the connection]
13:01mpsAriadne: also I wouldn't like idea that alpine evolve to next ubuntu
13:01Ariadnei do not think you have to worry about that happening
13:02mpsI hope so ;)
13:06qcyrdqcpzg[m]is the apple cli tool "powermetrics" reliable? specifically the ANE metric?
13:17Glanzmannmarcan: +1 for putting a boot picker in m1n1.
13:43povikthat's in consideration?
13:44AdryzzOLEDEdition[m]11there are no manuals
13:44AdryzzOLEDEdition[m]11oh it says tomorrow
13:46Glanzmannpovik: It wasn't and we were never going to do that until I read todays backlog. But I often thought about doing it myself but than said it is wasted time because marcan would never merge it.
13:47GlanzmannBut that would solve our choose the right dt for the kernel issue and would allow us to have multiple kernels installed with different dts.
13:47marcanin *principle* that shouldn't be required once the DT stabilizes, but it can help in the early days. but I'm more interested in it for secureboot.
14:01fp3 has joined #asahi-dev
14:02leitao has joined #asahi-dev
14:03leitao has quit []
14:04povikmarcan: did you catch that i sent you the rebased/updated audio branch?
14:04poviknot pushing, just making sure you saw it
14:06fp2 has quit [Ping timeout: 480 seconds]
14:17_jannau_and there's a libglvnd release with the BTI fix in the case someone likes their branches protected on M2
14:17Glanzmannjannau: Nice.
14:19_jannau_povik: marcan was considering using github pull requests as reminders without intention to merge them
14:20povik(to branches protected)
14:21_jannau_i.e. a PR against the bits/audio branch with the conflicting new state. if devicetree are required, just mention that and branch/commit in the PR description
14:22_jannau_povik: gcc switch to enable it is '-mbranch-protection=...`
14:30___nick___ has joined #asahi-dev
14:31poviklet me try the fake PR workflow then
14:31povikpossibly diffs will still work
14:32___nick___ has quit []
14:34___nick___ has joined #asahi-dev
14:35nehsou^ has quit [Remote host closed the connection]
14:37leitao has joined #asahi-dev
14:39povikdidn't like how slow github's UI was, i guess because it's struggling with the size of the repo/its network
14:40Dcow[m]povik: looks like you have already implemented amp limit and normalizing on the probe. What other danger endpoints there yet to be fixed?
14:40povikalso silly me put the cs42l84 schema in sound/soc/codecs/
14:40povikDcow[m]: also the codec highpass is set on tweeters
14:40povikpossibly none
14:40povikmarcan may test it now
14:42DmitrySharshakov[m]I guess MacBook Air's also need some sort of capping functions, but as those are not present now (at least weren't there yesterday) driver will refuse to probe. Quite a smart solution to protect everything :)
14:42Dcow[m]povik: Thanks for update!
14:44DmitrySharshakov[m]I guess when somebody sets those for MBA then audio is ready to be shipped by default and for MBP will have to either ship asahi-audio PipeWire configs or wait for WirePlumber patches
14:45DmitrySharshakov[m]Will probably ping somebody of WirePlumber maintainers to review parts necessary
15:03Race has quit [Ping timeout: 480 seconds]
15:09the_lanetly_052 has quit [Remote host closed the connection]
15:09the_lanetly_052 has joined #asahi-dev
15:13leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:17leitao has joined #asahi-dev
15:25___nick___ has quit []
15:37leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:02benpoulson has quit [Remote host closed the connection]
16:03leitao has joined #asahi-dev
16:08mia_ has quit [Remote host closed the connection]
16:11benpoulson has joined #asahi-dev
16:14benpoulson has quit [Remote host closed the connection]
16:25chengsun has quit [Ping timeout: 480 seconds]
16:27leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:28leitao has joined #asahi-dev
16:30jannaupovik: mac studio m1 ultra (j375d), m1 max should be identical trace_codecs.log
16:31jannauwould it be useful to do something with the headphone jack on unkown cs42l84 devices?
16:31chengsun has joined #asahi-dev
16:39chengsun has quit [Ping timeout: 480 seconds]
16:47chengsun has joined #asahi-dev
16:48mia_ has joined #asahi-dev
16:58chengsun has quit [Ping timeout: 480 seconds]
17:00chengsun has joined #asahi-dev
17:12robher has joined #asahi-dev
17:19hir0pro has joined #asahi-dev
17:26mia_ has quit [Remote host closed the connection]
17:29mia_ has joined #asahi-dev
17:30TheLink has quit [Quit: ZNC 1.8.2 - https://znc.in]
17:33TheLink has joined #asahi-dev
17:37TheLink has quit []
17:37TheLink has joined #asahi-dev
17:44TheLink has quit [Quit: ZNC 1.8.2 - https://znc.in]
17:44TheLink has joined #asahi-dev
17:47zzywysm has joined #asahi-dev
17:47the_lanetly_052 has quit [Ping timeout: 480 seconds]
17:50chengsun has quit [Ping timeout: 480 seconds]
17:51chengsun has joined #asahi-dev
17:57marcanpovik: I did, will merge as soon as I get a chance :)
18:00mia_ has quit [Remote host closed the connection]
18:00mia_ has joined #asahi-dev
18:01leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:02hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:04chengsun has quit [Ping timeout: 480 seconds]
18:05mia_ has quit [Remote host closed the connection]
18:06chengsun has joined #asahi-dev
18:11hir0pro has joined #asahi-dev
18:11mia_ has joined #asahi-dev
18:20mia_ has quit [Remote host closed the connection]
18:20mia_ has joined #asahi-dev
18:22mia_ has quit [Remote host closed the connection]
18:25mia_ has joined #asahi-dev
18:28chengsun has quit [Ping timeout: 480 seconds]
18:36benpoulson has joined #asahi-dev
18:37hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:38chengsun has joined #asahi-dev
18:40duban has quit [Quit: I'm out]
18:41duban has joined #asahi-dev
18:47benpoulson has quit [Remote host closed the connection]
18:51povikjannau: is there some trace_codecs.log you took?
18:52povikabout cs42l84 i am curious if you can report the driver working
18:52povik(once it makes its way to 'asahi')
18:52poviknot sure i put in the node for mac studio
18:53jannauI thought I posted that trace
18:54jannauI put the node (disabled) in the dts
18:54jannaunot sure about the cs42l84
18:55benpoulson has joined #asahi-dev
18:55jannauI can add it myself if needed
19:02povik404, i think it's private
19:03j`eypovik: works for me
19:03j`ey'hv/trace_codecs.py log for Mac Studio M1 Ultra
19:05povikah client on mobile not copying the full link
19:05povikthere, i see it
19:06jannauit was secret but I thought that just means that it is not visible from my profile
19:08povik# [I2CTracer@/arm-io/i2c1] [audio-speaker] REG: W.8 CHNL_0 = 0x28 (CDS_MODE=0, AMP_LEVEL=0x14)
19:09povikso it sets the same as on the macbook pros i think
19:17poviknot actuaĺly, higher
19:18yamii has quit [Quit: WeeChat 3.6]
19:19yamii has joined #asahi-dev
19:26benpoulson has quit [Remote host closed the connection]
19:29benpoulson has joined #asahi-dev
19:32chengsun_ has joined #asahi-dev
19:34chengsun has quit [Ping timeout: 480 seconds]
19:51benpoulson has quit [Remote host closed the connection]
19:56benpoulson has joined #asahi-dev
20:02f423[m] has joined #asahi-dev
20:03top has joined #asahi-dev
20:19top has quit [Quit: By ircgo.org]
21:02hir0pro has joined #asahi-dev
21:23jeffmiw has joined #asahi-dev
21:24jeffmiw has quit []
21:25jeffmiw has joined #asahi-dev
21:26hir0pro has quit [Ping timeout: 480 seconds]
21:27mia_ has quit []
21:31jeffmiwpaulywog: about hwmon, I have been looking into it, ramping very slowly due to limited time. I do not have anything useful to share yet as started from zero knowledge on hwmon and smc.
21:36benpoulson has quit [Remote host closed the connection]
21:36benpoulson has joined #asahi-dev
21:54benpoulson has quit [Remote host closed the connection]
21:54benpoulson has joined #asahi-dev
22:00benpoulson has quit [Remote host closed the connection]
22:00benpoulson has joined #asahi-dev
22:05amarioguy has quit [Remote host closed the connection]
22:06benpoulson has quit [Remote host closed the connection]
22:07benpoulson has joined #asahi-dev
22:11jeffmiw has quit [Ping timeout: 480 seconds]
23:24Race has joined #asahi-dev
23:44jnn has joined #asahi-dev
23:45jn has quit [Ping timeout: 480 seconds]
23:53chadmedDmitrySharshakov[m]: no way are we packaging a beta branch of wireplumber just to jump the gun by a couple of months. as julian points out in that note, it will be released in a couple of months, so we can just wait.
23:54chadmedfor one, i dont want to write an ebuild for it, and for another i dont want to deal with "why does wireplumber work on all my other machines but is janky on asahi" type support questions that come with forcing unstable testing branches on users who are not prepared to deal with them
23:55chadmedthe time is better used testing the proposed features ourselves and smoothing out the experience
23:56chadmedsomething something ethical hacking et cetera and so on and so forth
…