#
…

2021-02-07

01:01choozy has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
01:21amw has quit [Ping timeout: 272 seconds]
01:28amw has joined #asahi
01:28klaus has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
01:36amw has quit [Ping timeout: 265 seconds]
01:42marshmallow has quit [Ping timeout: 272 seconds]
01:44marshmallow has joined #asahi
03:23phiologe has quit [Ping timeout: 260 seconds]
03:24phiologe has joined #asahi
03:33Tokamak has quit [Ping timeout: 246 seconds]
03:37Tokamak has joined #asahi
04:06marvin24 has quit [Ping timeout: 240 seconds]
04:06marvin24 has joined #asahi
05:52Tokamak has quit [Ping timeout: 240 seconds]
05:53Tokamak has joined #asahi
05:58Tokamak has quit [Remote host closed the connection]
06:16Tokamak has joined #asahi
06:36VinDuv has joined #asahi
06:56Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:16klaus has joined #asahi
07:24maor26 has joined #asahi
08:12thestr4ng3r has joined #asahi
08:14thestr4ng3r_ has quit [Ping timeout: 256 seconds]
08:38arndnever_released: indeed, most of the setup code looks like it should just go into the bootloader, there is no reason for Linux to care about that. For a lot of SoCs, we end up with that stuff in the driver so we can support devices that ship with an unknown bootloader, but if we can just modify the loader here there is no need for that
08:42Bublik has quit [Ping timeout: 272 seconds]
08:50FanfweSo, according to Tom's hardware's article from 3 days ago about the Apple M1, "Apple’s I2C has a custom firmware that uses an exclusive protocol, which thwarted using the USB Type-A ports." lol
09:00jkao[m] has quit [Quit: Idle for 30+ days]
09:00fl35[m] has quit [Quit: Idle for 30+ days]
09:00hotsndot[m] has quit [Quit: Idle for 30+ days]
09:19Tokamak has joined #asahi
09:27Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:28marcanarnd: I want to bring up as much PHY stuff as I can in m1n1, to avoid pushing those hideous register poke blobs downstream into the linux fdt
09:29marcanbut yeah that depends on how deep a sleep we go into and how much state is lost in that case
09:30marcanthis is m1n1's entire reason to exist, to take care of as many apple-isms as it can before handing off to linux, u-boot, or whatever
09:31marcangiven how macos lasts for ages on battery... if it isn't ever going into deep enough sleep to need those PHY reinits, then I say we don't need to either
09:32marcanI think part of apple's motivation for pushing all that crap into macos is simply to keep iBoot small and simple, because it's a higher security boundary - not because it *has* to be macos doing these things
09:33marcanbut we should be able to introduce this at a later stage anyway; no deep sleep for now, if it turns out we need phy blobs to resume from deep sleep states we want to use, we make m1n1 pass those through, and until then this keeps the drivers and DT bindings simpler and more reviewable for the initial versions
09:38bostjan has joined #asahi
09:41bgb has joined #asahi
10:34bgb has quit [Ping timeout: 256 seconds]
11:06acelogic has quit [Remote host closed the connection]
11:13KindOne has quit [Ping timeout: 272 seconds]
11:15KindOne has joined #asahi
11:40klaus has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:44klaus has joined #asahi
12:06bostjan has quit [Quit: Leaving]
12:58kettenismarcan: that might work as long as m1n1 will continue to do this even if you pass on the blobs
12:58kettenisbut it means you'll have to deal with clock (un)gating in m1n1
12:59never_releasedkettenis: the PCIe controller on M1 Macs provides an ECAM
12:59never_releasedso you might even be able to get away without a driver
12:59kettenisnever_released: yes
13:04kettenisthe AIC would ave to handle MSIs though like arnd suggested
13:38Bublik has joined #asahi
14:17choozy has joined #asahi
15:16choozy has quit [Ping timeout: 258 seconds]
15:30the-mentor has quit [Quit: The Lounge - https://thelounge.chat]
15:35the-mentor has joined #asahi
15:40modwizcodeQuestion about SMP startup, from M1N1's code it seems that there's some sort of power management control interface and there's a register you can write to set the reset vectors for each core, and another two registers for poking the cores to start, and a third that maybe ungates the IRQs is that accurate?
15:41modwizcodeI emulated a (slightly wrong) but functional copy of something doing that but I still had to hack up the code in M1N1 a bit, but I get SMP startup. Linux breaks though I think I need to connect all of the cores timer's to their FIQ inputs not just one of the cores.
15:42never_releasedthe reset address is locked by iBoot
15:42marcannever_released: only for the boot core
15:42marcanwhich is already running
15:42marcanwhich makes it irrelevant
15:42never_releasedyou can turn off the boot core
15:43never_releasedit's not irrelevant
15:43modwizcodeTurning off CPUs is what I was going to ask about
15:43modwizcodedoes clearing the bits in the turn on register turn them off
15:43marcancan you? why would you ever do that?
15:43marcanthese cores support retention wfi
15:43marcanwhich power gates the core but when it comes back it keeps pc/sp
15:43never_releasedmarcan: retention WFI is when you turn off a core individually
15:43never_releasedbut you can turn off a whole complex
15:44never_released(which preserves 0 state)
15:44modwizcodeDoes retention WFI only keep PC/SP and no other registers?
15:44marcanmodwizcode: yes
15:44marcannever_released: does macos ever actually do that for the e-complex?
15:44modwizcodeyes on clearing the bit or yes about the registers
15:45marcanmodwizcode: the registers
15:45marcanbut you can configure it to only clock gate, and then it keeps state
15:45never_releasedthat it's not always
15:45choozy has joined #asahi
15:45never_releasedit's an heuristic somewhere, not guaranteed that the registers are wiped
15:45marcanthere are three settings
15:45marcanalways power down, never power down, let the heuristic decide
15:45modwizcodeInteresting
15:45marcanm1n1 sets it to never power down, so linux doesn't need any weirdo wfi hook like corellium did
15:46marcanand then a cpuidle driver can set it to always or heuristic, and deal with it there
15:46modwizcodeThat's kind of strange though, how would you handle that inconsitency with the heuristic? Wouldn't you have to assume it lost state in case it did?
15:46marcanit checks
15:46modwizcodeOh it can check
15:46marcanif lr == 0, it knows it was deep
15:46marcanotherwise it can just return
15:46modwizcodethat's simple of courase
15:48modwizcodeDo we know anything besides what the dev tree tells us about memory map?
15:48modwizcodeLike is ROM mapped at 0 or is that kind of thing pulled out of the address space after startup
15:48modwizcode(if it was ever mapped in)
15:48never_releasedmodwizcode: you don't have access to ROM
15:48never_releasedpermanently so
15:49modwizcodeWell that's probably ideal for my needs then
15:58klaus has quit [Quit: Textual IRC Client: www.textualapp.com]
16:00stylefish[m] has quit [Quit: Idle for 30+ days]
16:00kingwill101[m] has quit [Quit: Idle for 30+ days]
16:00newmerck[m] has quit [Quit: Idle for 30+ days]
16:00hipboi[m] has quit [Quit: Idle for 30+ days]
16:08clover[m]is suspend-to-ram working with asahi?
16:10jn__not at this point
16:12modwizcodeI've been meaning to look into how suspend-to-ram is implemented.
16:13clover[m]is it S3? (ACPI)
16:15jn__there's no ACPI in apple firmware/software on the M1
16:22clover[m]Trusted Firmware-A can implement suspend-to-ram via PSCI (ARM power state coordination interface)
16:23j`eyno PSCI either
16:23zopieux has quit [Quit: zopieux]
16:26modwizcodeWhat was the deal with alternate SMP startup methods on linux?
16:26j`eypsci vs spin-table?
16:28modwizcodeThere was a mention of it on the mailing list
16:28modwizcodebut the M1 doesn't have PSCI...
16:28modwizcodeBut I saw a patch to linux about emulating it or something weird. Didn't fully parse the code out to figure it out
16:29clover[m]could m1 be ported to use TF-A?
16:29j`eythere was some mention of some EFI related stuff, that Ard wrote a patch for, but I didn't look at it either
16:29modwizcodeIt doesn't have EL3
16:29modwizcodeYeah the UEFI mention seemed a little annoying tbh
16:29modwizcodenot sure why it would matter with a platform like this that doesn't need UEFI in the pipeline
16:30Bublik has quit [Ping timeout: 272 seconds]
16:35clover[m]do we understand how macOS pulls off deep sleep?
16:40kettenisI don't see why psci-as-a-firmware-call should be tied to UEFI
16:42kettenisa device tree binding that provides the entry point that lives in memory reserved by the bootloader (m1n1) would work just as well
16:52kettenisbut I don't see a benefit over using spin-table unless m1n1 would want to implement other psci functionality
16:52clover[m]does psci-as-a-firmware call necessarily need to be tied to TF-A?
16:52clover[m]a device tree binding that provides the entry point that lives in memory reserved by the bootloader (levinboot) might work just as well
16:53kettenispsci was never tied to TF-A
16:53never_releasedPSCI can't be in the same exception level as the OS
16:53kettenisU-Boot provides an implementation for some boards
16:53never_releasedthat's the catch
16:53never_releasedon 🍎M1, PSCI would mean running the OS at EL1 instead of EL2
16:54never_released(because no EL3 in HW)
16:54never_releasedthat's possible? Yes. Is that sane? No.
16:54kettenisindeed you either need smc which implies EL3 or hvc which implies EL2
16:54never_releasedbecause you lose virt
16:55modwizcodeThis is basically what I thought
16:55never_releasedmaybe arm64 needs some kind of PALcode
16:55never_releasedbut too late for that now I'd bet
17:06never_releasedmodwizcode: > PALcode (Privileged Architecture Library code) is the name used by DEC for a set of functions in the SRM or AlphaBIOS firmware, providing a hardware abstraction layer for system software, covering features such as cache management, translation lookaside buffer (TLB) miss handling, interrupt handling and exception handling
17:06Tokamak has joined #asahi
17:06never_releasedso that it's abstracted away in an SW layer
17:09ys0seri0us has joined #asahi
17:14Tokamak_ has joined #asahi
17:14Tokamak has quit [Ping timeout: 246 seconds]
17:15zopieux has joined #asahi
17:18marcanmodwizcode: there was some talk on #armlinux about implementing PSCI over UEFI
17:18marcanI might look into trying that out if the scaffolding required isn't too much trouble
17:18never_releasedmarcan: it's not too much trouble imo
17:19never_releasedlooked at implementing it
17:19never_releasedI'd just like it to be a standard instead of a thing cooked for Apple Si
17:19marcanit's intended to be standard (on linux at least), AIUI
17:19never_releasedas other SoC makers will look at it and want to use such an interface afterwards
17:20marcanwell for SoCs with EL3 they already have it anyway
17:20never_releasedI meant for a new PSCI conduit over UEFI
17:20never_releasedshould be standardised somewhere
17:20never_releasedwait, will talk about it with arm folks
17:21marcanI'd be happy to have something standard-ish like that that m1n1 can provide, because then we can hide even more nonsense away from linux, like proper full suspend and dealing with initialization functions on resume
17:22never_releasedmarcan: there's also a new upcoming ECAM over PSCI interface for PCIe
17:22marcandoing all confing accesses over PSCI?
17:23never_releasedmore geared towards ECAM accesses
17:23never_releasedused to workaround hardware erratas
17:24marcankettenis: u-boot provides UEFI, right? can it enhance an existing UEFI implementation, i.e. add services?
17:24marcan(how much of UEFI does it do?)
17:24never_releasedmarcan: it is the UEFI implementation
17:24never_releaseda pretty basic one without acpi
17:24never_releasedbut runs Grub fine
17:25ys0seri0us has quit [Ping timeout: 240 seconds]
17:25marcanI'm wondering if I can e.g. provide all the hardware-related init stuff in m1n1, then let u-boot provide the boot sequence and disk/FS services
17:25never_releasedwhy not have it as a U-Boot SPL
17:26marcansure, but m1n1 already exists
17:26marcanI mean if you want to throw all the code into SPL, that works too
17:26marcanbut it's not like 3-bootloader chains are rare on arm
17:27marcanand it gives us some flexibility while avoiding duplication of responsibilities
17:28never_releasedat the end, m1n1 should never launch a kernel directly
17:28marcanfor most users, probably not
17:28never_releasedbut be just a stub for u-boot/tianocore/whatever
17:28bylaws<never_released "used to workaround hardware erra"> Stuff like that bug on t194?
17:28modwizcodeInitially it seemed you were opposed to uboot in some ways?
17:28marcanbut it should be *capable* of doing that :)
17:28never_releasedbylaws: Yes. t194 was one of the reasons for it being created.
17:28marcanmodwizcode: me?
17:28marcannot at all
17:30marcanI said I don't want to have u-boot as a hard dependency in order to boot linux *at all* because being tied to piles of bootloader code makes it harder to do back to basics tests and I do like being able to throw kernels at m1n1 and play around in a small codebase
17:30marcanbut I very much expect the production version of Asahi Linux to end up looking like m1n1 -> u-boot -> grub -> kernel, for end user installs
17:30marcanor something along those lines
17:31modwizcodeI guess the problem with long bootloader chains is more points of failure, and more complexity
17:31marcanwell, kind of, but the thing is it also makes it more modular
17:31marcanwhich makes it easier to debug the next stage by loading at the previous one
17:31never_releasedand you'll need a bunch of complexity anyway
17:31never_releasedfor NVMe, FS access
17:31marcane.g. m1n1 makes an excellent "boot and throw things at it via serial" loader, for almost literally anything because of the python rpc interface
17:32modwizcodeDoes NVMe offer no simplified storage access protocol?
17:32never_releasedin practice, almost no one has serial, marcan
17:32marcannever_released: I'll be fixing that next week
17:32marcanalso plenty of people have two M1s
17:32modwizcodeSerial is helpful for qemu work c;
17:32marcanI actually want to try writing a minimal NVMe driver, I don't expect it to be that hard?
17:32marcanmost "complex" devices are only complex to implement all features of
17:32kettenismarcan: U-Boot already does too much UEFI ;)
17:32vilhalmer has quit [Read error: Connection reset by peer]
17:33never_releasedkettenis: it does too little UEFI :P
17:33modwizcodeI guess the complexity for NVMe I'm assuming is that I assumed you have to get PCIe working
17:33never_releasedto the extent that ACPI is part of UEFI
17:33never_releasedmodwizcode: NVMe isn't over PCIe of those
17:33marcanmodwizcode: it's not PCIe
17:33modwizcodeit's not related at all then?
17:33marcannot at all
17:33modwizcodeOkay I've been misled
17:33winocmoh man, ghettohci
17:33marcanunless you're running a corellium kernel, then it's PCIe because they faked a PCIe bus for it
17:33winocmthat’s nostalgic
17:33marcanwhich is completely insane
17:33modwizcodewhat the heck is this file
17:33modwizcodeI don't think I've ever seen this
17:34modwizcodeYeah but is this even
17:34vilhalmer has joined #asahi
17:34modwizcodeIt's not in the orig wii repo I don't think
17:34marcanwe used that on the Wii U to get mini (yes the same python RPC protocol and codebase as m1n1) working
17:34modwizcode(I've only ever paid much attention to that because I never had a Wii u
17:34marcanbecause there was no good debug port
17:34marcanno serial
17:34modwizcodeinteresting
17:34modwizcodeThat's annoying having to do a USB stack to get anything
17:34marcanso the first version was output only
17:34marcanit bitbanged RS-232 over the sensor bar
17:34marcanas in turning it on and off
17:34modwizcodeLOL I remember reading about that I think
17:35marcanthen I debugged that ghettohci thing using that
17:35modwizcodeWhen I read about the Wii stuff the thing I'm most amazed about is finding the test points for the gpios and mapping them back to a register :p
17:35modwizcodeAnyway that's offtopic, but NVMe isn't PCIe based good to know
17:36vilhalmer has quit [Read error: Connection reset by peer]
17:36marcanI'll be adding a platform/DT binding for the NVMe driver once I get to that, shouldn't be hard
17:36marcanthen we can instantiate it properly
17:36marcansame as every other driver that has both versions, e.g. xHCI
17:37modwizcodeDo you expect it to be fairly similar to other NVMe stuff? Or completely different?
17:37marcanit's the standard apple nvme
17:37marcanwhich linux already has quirk workarounds for
17:37marcanjust not over PCI
17:37marcannot sure if there are any other quirks, if there are they should be trivial to work around
17:37modwizcodeI'm thinking about if I'll be able to reuse the NVMe code in qemu :p
17:37modwizcodestorage code is like a different area with concerns I've not paid attention to yet
17:37vilhalmer has joined #asahi
17:37vilhalmer has quit [Read error: Connection reset by peer]
17:37marcanwould need to implement the same quirks
17:37marcanit shouldn't be hard
17:37marcanmostly just the queue entry size is doubled IIRC
17:38marcanthe other quirks probably don't affect an emulator
17:38vilhalmer has joined #asahi
17:38modwizcodeFor most quirk stuff I just need to stub stuff out so code doesn't complain (i.e. all the HID registers are mostly stubbed to zero, but I expect I'll have to emulate a writable reg for things that readback the value (m1n1 doesn't))
17:39modwizcodeIncidentally where did you pull the reg definitions for spinning up cores from?
17:39marcanthe reg addresses come from the adt
17:39modwizcodeYeah but the offsets
17:39marcanthe what reg does what is, well, corellium code, which I treated as vendor code
17:39marcani.e. I broke it down and figured out what i needed and what I didn't
17:40modwizcodeAre you planning to write docs for it anywhere? (at least defining the offsets?)
17:40marcanI want to write docs for everything, and anyone is welcome to poke me to write docs about any specific thing they need because that'll encourage me to do so
17:40modwizcodeI have enough hacked together to boot linux with a version of m1n1 that doesn't pull the addresses from the ADT but it's not modeled after hardware at all
17:40vilhalmer has quit [Read error: Connection reset by peer]
17:40marcanjust need to allocate time to it
17:40marcaneventually ideally we should have fairly comprehensive SoC docs
17:41modwizcodeI'd appreciate NVMe and the SMP bringup docs.
17:41modwizcodeI'm hoping the QEMU code will generally be well documented enough to have full docs embedded
17:41modwizcodemost of QEMU doesn't do that and it sucks
17:41marcanwhat I know about SMP is trivial so far, let me infodump on wiki real quick
17:41marcanalso feel free to rewrite/reformat whatever
17:42vilhalmer has joined #asahi
17:46Tokamak_ has quit [Quit: Textual IRC Client: www.textualapp.com]
17:48vilhalmer has quit [Quit: :qa!]
17:53kettenismarcan: I don't think it makes sense for m1n1 to do UEFI stuff itself
17:53kettenisif it would implement a PSCI interface it should just advertise it in the device tree
17:53kettenisand have U-Boot or tianocore expose it in a UEFI table
17:54never_releasedkettenis: should be part of the UEFI itself
17:54never_releasedas a set of runtime services functions
17:54never_releaseddon't think that m1n1 is the right place for it, would end with oddball hacks
17:54never_releasedwhereas the UEFI runtime services region is already mapped
18:09Glanzmannmarcan: I read in the backlog that NVMe is not over PCIe on M1. What I/O bus do they use? Do you know anything about the Sound card used in the M1 models?
18:09GlanzmannDoes someone know if palm detection is done in the kernel or in userland on Linux for the touchpad?
18:13raster has joined #asahi
18:17Glanzmannmarcan: I'm also using thinkpad usb keyboards. Luckily none failed so far. I also have a bluetooth one.
18:19modwizcodeGlanzwmann: Last I knew I think palm detection was done in the kernel in the hid stuff but that's changed a lot since the last time I messed with it so it might be raw hid with a userspace driver
18:20modwizcodealso I would assume the NVMe controller is just directly accessible off the memory as MMIO rather than being tunneled through pcie
18:20modwizcodemarcan: thanks
18:20modwizcodeWonder what WLAN debug is
18:21marcanprobably literally what it says on the tin...
18:21marcandebug output from the broadcom firmware I presume
18:21modwizcodeAh I forget that WLAN chipsets actually like run a whole freaking OS
18:21modwizcodeI'm not sure how I feel about that :/
18:21marcanit's fullmac, and also custom stuff (it'll have proprietary stuff for AirDrop I bet...)
18:22modwizcodeYou think AirDrop is something proprietary in the WLAN? I bet it's just normal Wifi Direct/P2P with a special broadcast format that's generic
18:22opticronyeah, there was an airdrop on linux implementation floating around, iirc
18:24modwizcodethat's pretty neat, might be interesting to poke at. No idea why Google can't get this right Wifi direct is pretty easy
18:26opticronone special thing that's necessary is apparently active monitor mode
18:26opticrononly some wifi cards support it
18:26marcanmodwizcode: it's proprietary
18:26marcanI mean of course it's over the WiFi physical layer
18:27davidrysk[m]yeah someone recently RE'd it (which is what opticron linked)
18:28davidrysk[m]but indeed it is proprietary, built on standards, apparently the standards aren't good enough to be reliable
18:30modwizcodeI bet the issue is the polling/discovery time for existing stuff. A lot of stuff on android uses bluetooth based discovery with Wifi data transfer which is the worst possible option
18:30modwizcodeI just was assuming it's a featureset supported by generic controllers but I guess not, what's AWDL?
18:33zopieux has quit [Ping timeout: 265 seconds]
18:35zopieux has joined #asahi
18:36marcanjust some protocol Apple cooked up (Apple Wireless Direct Link?)
18:37modwizcodeInteresting
18:37modwizcodeI should look at the code
18:37pg12_ has quit [Quit: pg12_]
18:38pg12 has joined #asahi
18:52acelogic has joined #asahi
19:04arndThe approach that ardb came up with for psci over the uefi runtime interface would definitely be intended to run in u-boot, and not rely on having tianocore or something along those lines. As far as I understand it could actually be implemented in m1n1 as well, without doing any other parts of UEFI
19:05arndit's a bit of a hack, but probably enough to get things running until everyone has moved to u-boot for their boot flow
19:07arndmy first suggestion was to do something more like RTAS in powerpc open firmware, which has a different way of calling into firmware code based on DT properties, but I do prefer ardb's solution since it uses a callback interface that is already established on arm firmware, just not yet for psci
19:08arndI also thought about what it would take to route PCI config space through that for the NVMe drive. It would probably work, but I'd rather have a simple platform driver in the kernel for this one than to hack up a PCI host in firmware for the sake of making an unmodified Linux driver work
19:10arndI remember doing PCI config space over RTAS on powerpc, and I always wondered why the arm server folks that use ACPI haven't done it yet, but as the M1 only has one device behind it, there is really point
19:10never_releasedarnd: depends
19:10never_releasedminimal kernel work required could be a goal
19:11arndFor other OSs certainly: if you want to run Windows, that would be helpful. For Linux I prefer doing it right
19:11never_releasedarnd: I'd prefer all the OSes to share the same stack there
19:12never_releasednot this FW for Linux, this other FW for X and this other one for Y
19:12arndnot going to happen anyway: windows and RHEL rely on ACPI, and for normal Linux we want a sane abstraction
19:13never_releasedPSCI has already an upcoming PCIe config space conduit
19:13never_releasedwhat it'd look like basically is it being a PSCI conduit in addition to hvc and smc ones
19:15arndWhat I could see though would be an EL2 wrapper that runs tianocore and provides a SBSA/SBBR style environment for booting unmodified operating systems, with an emulated GIC, pl011, PCI mmconfig, and (if you want to go wild) virtio-net and shadow page tables for 64kb pages
19:16never_releasedarnd: or even more insane
19:16never_releasedexploiting guarded execution
19:16never_releasedremember that we have GL2 in parallel of EL2
19:16arndI don't remember what that does
19:17never_releasedsecurity feature, a set of rings in parallel used for PPL notably
19:17never_released(Page Protection Layer)
19:17never_releasedGL1 for guest OSes (at EL1) and GL2 for host OS (at EL2)
19:18never_releasedhas its own exception vectors of course
19:19arndah, so they do have a higher privilege level than EL2 but just didn't want to be compatible with Trustzone/EL3? I can't say I blame them ;-)
19:21never_releasedarnd: they had EL3 on the Apple A7 to Apple A9
19:21never_releasedthen dropped that to only have EL1 and EL0
19:21never_releasedA13 added guarded exec
19:21never_releasedand then A14/M1 added... EL2 and 4KB page support (which was there in Apple A7 and A8, dropped in A9)
19:22never_releasedthey also dropped big endian in user-mode on A10... A7-A9 had big endian at EL0 only
19:26vilhalmer has joined #asahi
19:31ketteniswell, IMNSHO Red Hat choosing not to support device trees in RHEL is their problem
19:34vilhalmer has quit [Read error: Connection reset by peer]
19:34vilhalmer has joined #asahi
19:52modwizcodeI thought it extremely strange that ARM (and previously open firmware stuff) successfully met their needs via device tree seemingly just fine, and then later ACPI was reintroduced for... some unclear reason. (I'm sure there's a real reason but I've not seen it explained anywhere)
19:58never_releasedmodwizcode: same FW everywhere
19:58never_releasedit's an absolute requirement for Windows
19:59never_releasedand DT was underspecified a lot
19:59never_releasedand is still not _that_ stable
20:00modwizcodeI think I asked about this before, but is there any documentation of what the heck GL1/2 actually do? (and why they're special?). I've read all the docs I can find about PPL and APRR (which I think is mostly unrelated) but guarded execution seems to be a totally undocumented thing so far?
20:00never_releasedmodwizcode: yep, utterly undocumented :p
20:00modwizcodenever_released: I mean I don't see why windows can't learn to deal with DT
20:00never_releasedmodwizcode: technical reasons
20:01never_releasedWindows is tightly bound to ACPI
20:01never_releasedsince ages now
20:16vilhalmer has quit [Read error: Connection reset by peer]
20:17vilhalmer has joined #asahi
20:27vilhalmer has quit [Read error: Connection reset by peer]
20:28vilhalmer has joined #asahi
20:52arnd25 years since Windows NT for PowerPC used an Open Firmware device tree ;-)
21:23raster has quit [Quit: Gettin' stinky!]
21:29krbtgtNT on PPC used ARC, not OF
21:30krbtgtthe tl;dr on windows' dependence on EFI/ACPI is that NT actually mandates ARC from the beginning
21:30krbtgtNTLDR.COM? that's actually an ARC emulator for BIOS
21:30krbtgtthere's a shim bootloader for ARC on OF on PPC
21:31krbtgtand NT had a bunch of HALs but that's not relevant
21:31krbtgtanyways 2000 made it use ACPI optionally in HALs
21:32davidrysk[m]mjg59 has written at length regarding ACPI and Windows and how vendor assumptions make things difficult
21:32krbtgtvista mandates ACPI on all platforms, then some stuff happens in 8.x for the ARM platform superfund site (it mandates ACPI/EFI on ARM, just IIRC there's some "HAL extensions" that paper over interrupt controlleer differences, ask never_released)
21:33davidrysk[m]it's at the point where Linux has to claim to be Windows for the hardware to behave correctly (on most x86 systems)
21:33krbtgti can't blame MS for that
21:33krbtgtbut dumb OEMs
21:34never_releasedkrbtgt: on Windows 8.0, you technically only needed an halext for the timer on arm
21:34never_releasedon 8.1, GTDT ACPI table for the timer
21:34never_releasedand no halexts needed
21:34davidrysk[m]never_released: why couldn't MS build out devicetree support for ARM64? The desire to placate OEMs?
21:34never_releasedfor HW with arm arch timer + GIC
21:34never_releaseddavidrysk[m]: it's a Linux only broken thing
21:35never_releasedit's not a standard
21:35never_releasedit's whatever Linux folks cooked on their side
21:35davidrysk[m]meanwhile ACPI is practically a Windows-only broken thing, and doesn't follow the standard in practice
21:35never_releaseddavidrysk[m]: what?
21:35never_releasedWindows on Arm was booting with ACPI in 2007
21:35never_releasedchoice was already set in stone by then
21:36never_releaseddevice tree came way too late for arm
21:40never_releasedWindows on Arm(v6) on 1st gen Tegra in 2010
21:40davidrysk[m]Ahh, WinCE on ARM
21:40never_releasedwas already UEFI + ACPI
21:40davidrysk[m](or is this post WinCE)
21:41never_releasedand that one was a pic of it running x86_32 Reversi
21:41never_releasedthrough dynamic binary translation
21:43kettenisgiven that arm and aarch64 are different archotectures, this doesn't really matter
21:44never_releasedkettenis: for Windows, was actually funny, almost the same ACPI tables between arm32 and arm64
21:44never_released(there are devices such as the last-gen Lumia which can run the two)
21:45never_releasedWindows NT on Arm was UEFI + ACPI since the very beginning, which helps
21:47Hexagon has left #asahi [#asahi]
21:47Hexagon has joined #asahi
21:48amw has joined #asahi
21:52acelogic has quit [Remote host closed the connection]
21:54acelogic has joined #asahi
21:55acelogic has quit [Remote host closed the connection]
21:56acelogic has joined #asahi
21:57snalty has quit [Quit: ZNC 1.8.2 - https://znc.in]
22:00VinDuv has quit [Quit: Leaving.]
22:35amw has quit [Ping timeout: 264 seconds]
22:51amw has joined #asahi
23:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
23:01yrlf has joined #asahi
23:02DragoonAethis has quit [Quit: hej-hej!]
23:15maor26 has quit [Ping timeout: 240 seconds]
23:30DragoonAethis has joined #asahi
23:49DragoonAethis has quit [Quit: hej-hej!]
23:49DragoonAethis has joined #asahi
…