#asahi · 2022-02-02 07:36
chadmedhttps://github.com/AsahiLinux/docs/wiki/Feature-Support#asahi · 2022-02-01 06:45
chadmedGlanzmann: wrong channel :P#asahi · 2022-01-31 23:40
chadmedonce you have m1n1 and u-boot installed its pretty trivial to go from there#asahi · 2022-01-31 23:39
chadmednsklaus: ALARM works fine, so does Artix#asahi · 2022-01-31 12:27
chadmedlibreoffice is pretty atrocious on macos but ill get over it i think. beats putting up with my A1708's stuffed battery#asahi · 2022-01-31 12:25
chadmedon one level im surprised they didnt just use a Lightning Ridge chip but on another level im not surprised in the slightest#asahi · 2022-01-31 12:23
chadmedwas hoping it would just work with no cd321x quirks and i could use my new machine for uni this semester. alas, not to be #asahi · 2022-01-31 12:22
chadmedi wish i had some DL hardware to test now, i went and forked out for a native TB4 dock with proper displayport like a sucker :P #asahi · 2022-01-31 11:49
chadmedg8rfx9wozue0e9pa3n[m]: displayport alt mode is probably a while away, but usb 2.0 works so if you have a DisplayLink docking station you might be able to use that? #asahi · 2022-01-31 11:47
chadmedemerging rust, spidermonkey and firefox is still quicker on my machine than building chromium#asahi · 2022-01-31 11:47
chadmedimagine being the kind of person who *wants* to compile chromium#asahi · 2022-01-31 01:38
chadmedcatphish: https://github.com/AsahiLinux/docs/wiki/Developer-Quickstart-2.0 <-- if this makes sense to you, you should have the skill necessary to test out linux on these machines #asahi · 2022-01-30 15:30
chadmedat that point we will have an (almost) EBBR compliant boot environment on these machines, and almost compliant is compliant enough for a generic EBBR-capable distro to install an efi bootloader#asahi · 2022-01-30 15:29
chadmedyeah pretty much#asahi · 2022-01-30 15:29
chadmedhonestly it wont be an issue once the DT is stable since its not like the machines can magically just change on us#asahi · 2022-01-30 15:28
chadmedyeah we can swap kernels, but since m1n1 is providing the dt in this instance if the dt changes youd still need to get into 1tr and build a new boot payload#asahi · 2022-01-30 15:26
chadmedand also which is why we arent anywhere near ready for end users to jump on board, even if we had a sane environment where kernels can be swapped out on the fly, we're still at a point where the dt is unstable#asahi · 2022-01-30 15:25
chadmedwhich i _think_ is the plan here#asahi · 2022-01-30 15:25
chadmedor we do that yeah, dt is statically provided by a concatenated m1n1 payload#asahi · 2022-01-30 15:25
chadmedm1n1 does not need to know about the devicetree in an EBBR environment since it's just chainloading u-boot, which is then chainloading grub, which is what will pass the dt to the kernel#asahi · 2022-01-30 15:17
chadmedqrd is distros are able to assume a uefi environment, PSCI and optionally a device tree and thus focus their boot tooling on that, rather than have to try and cater to the existing approximately eleventy grillion different embedded boot procedures#asahi · 2022-01-30 15:14
chadmedArm's "embedded" boot specification, which we are (coincidentally?) following pretty closely#asahi · 2022-01-30 15:12
chadmedhopefully we will eventually be able to add ALARM (and its forks) to the list of distros that support EBBR. will make things a lot easier to maintain and install #asahi · 2022-01-30 14:47
chadmedjannau: i think for the mid term the sanest way to handle asahi support in ALARM would be to have an AUR repo with our own PKGBUILD that sanely installs a kernel and efi bootloader. since their whole schtick is providing a barebones rootfs for power users/embedded, i cant see them rushing to actually provide a sane distro kernel and way of installing it#asahi · 2022-01-30 11:44
chadmed4K support (at least in userspace on macos) makes sense for as long as Apple intends to support their DTK/Rosetta stack#asahi · 2022-01-30 11:43
chadmedcouldnt find a similar instance in llvm-libunwind though #asahi · 2022-01-30 11:43
chadmedmps: probably a hard coded page size somewhere in the code. that was the problem with libunwind#asahi · 2022-01-30 08:17
chadmedgood evening :-P#asahi · 2022-01-30 08:16
chadmedbut you can also do that yeah ^ #asahi · 2022-01-30 08:16
chadmedin menuconfig its under Boot options#asahi · 2022-01-30 08:07
chadmedas it stands theyre all treated identically performance-wise #asahi · 2022-01-30 08:06
chadmedtwp_rules: the scheduler knows they are different but since the cpufreq driver is on hold and the dmips/mhz info in the DT was part of that commit, it cant effectively schedule between them#asahi · 2022-01-30 00:32
chadmeddepending on where in the design cycle they decided not to use it, and tsmc's yields it wouldnt make financial sense to spin a new silicon rev just to get rid of it. the validation costs alone would be ridiculous #asahi · 2022-01-30 00:31
chadmedits interesting that it doesnt power up at all. maybe it was a last minute decision to remove its functionality so they just fuse enough of it off so that it doesn't turn on?#asahi · 2022-01-29 23:08
chadmedmost people wont even read that far down tbh, as soon as the they get penguins theyre going to close the page :D #asahi · 2022-01-29 23:07
chadmedGlanzmann: thanks for picking up on the lack of --recursive in m1n1. As for the untethered booting, i think it should stay in. the point of the guide is to get developers into a kernel, and being able to do that untethered is a part of that#asahi · 2022-01-29 09:37
chadmedyeah thats the wrong recovery, you need to hold the power button down until it prompts you with boot options. you could probably try following the new guide i linked above#asahi · 2022-01-29 09:34
chadmedhow did you get to recovery mode? #asahi · 2022-01-29 09:34
chadmedyou must be in the wrong recovery mode#asahi · 2022-01-29 09:29
chadmedjannau: i did intend on replacing the old guide but wanted to get some feedback first in case i missed anything#asahi · 2022-01-29 09:20
chadmedVinDuv: that makes sense, wasnt actually aware that the boot menu was localised that specifically#asahi · 2022-01-29 07:57
chadmedhttps://github.com/AsahiLinux/docs/wiki/Developer-Quickstart-2.0 anyone wanna proofread this? I've tried to simplify the dev quickstart guide and bring it up to date, incorporating the installer script to cut out having to manually create the macos stub etc#asahi · 2022-01-29 05:12
chadmedthe kernel is uploaded to the Apple Silicon device over a serial interface m1n1 exposes on boot #asahi · 2022-01-29 05:02
chadmedbecause u-boot supports the M1 SoC you can however set up a fully functioning untethered boot since it brings up pcie automatically, something m1n1 does not do #asahi · 2022-01-29 05:01
chadmedeverything can be booted from the nvme, but for a tethered boot (the default currently) you supply a kernel to m1n1 via USB from a host machine #asahi · 2022-01-29 04:47
chadmedim going to fix up/write a new developer quickstart (Developer VERY Quickstart?) in a few minutes since the old guide is very intimidating and can be mostly replaced with the installer script#asahi · 2022-01-28 11:56
chadmedyeah i was just about to say they would 100% just give apple whatever they ask for without question #asahi · 2022-01-28 11:53
chadmedi do find it odd that broadcom would spin out a PCIe BT module specifically for these devices when seemingly none have existed so far#asahi · 2022-01-28 11:49
chadmedit probably is something that stupid though, its broadcom :-P #asahi · 2022-01-28 11:49
chadmedinb4 is akin to like "i predict x will happen" so i think ChaosPrincess is just saying it would be really funny if it were just a bog standard UART over PCIe rather than confirming that as truth