#
✕ nick:robher
#asahi · 2024-01-15 14:47
robherelin, leio: :( Okay, thanks for confirming. Guess I'm back to waiting.
#asahi · 2024-01-15 14:39
robherelin: 12.3
#asahi · 2024-01-15 14:36
robherj`ey: I did have 12.? and then updated MacOS which updated the firmware to 13.7 (or 13.6?).
#asahi · 2024-01-15 14:28
robherI'd really like HDMI working on my M1 MBP, but that's documented as requiring 13.5 firmware. Is there a way to install a specific version of firmware? Updating to 13.5 MacOS, I ended up with 13.7 firmware.
#asahi · 2022-12-12 16:08
robher_jannau_: Alright, I'll test with that once it lands.
#asahi · 2022-12-12 16:00
robher_jannau_: I've seem similar as chadmed on suspend. Perhaps related to this kernel msg?: apple-pmgr-pwrstate 28e580000.power-management:power-controller@288: PS mca0: Failed to reach power state 0xf (now: 0x24f)
#asahi · 2022-03-10 14:31
robhermarcan: I thought ESP is supposed to have a well known UUID.
#asahi · 2022-03-08 19:00
robherand a 27" iPad
#asahi · 2021-07-22 18:03
robherok, then I'd go the /reserved-memory route.
#asahi · 2021-07-22 17:59
robherIs SEPFW something that could be extracted and put into linux-firmware? I'd assume distros put at least some of linux-firmware into their initrds.
#asahi · 2021-07-22 17:56
robherah, what marcan already said...
#asahi · 2021-07-22 17:55
robheralready in memory, then reserved-memory...
#asahi · 2021-04-06 15:18
robherkettenis_: To look at it another way, for every node in a dts there should be a schema covering it and all the properties. At least that's the goal of where we want to get to with schemas.
#asahi · 2021-04-06 15:14
robherkettenis_: bindings should be documented. Who is the consumer should be mostly irrelevant.
#asahi · 2021-04-06 14:59
robher...of read-only PCI config registers, that is.
#asahi · 2021-04-06 14:59
robher'shadow' may refer to the port logic registers having writable versions of PCI config registers.
#asahi · 2021-04-06 14:57
robherIf there's enough memory space for ECAM, then put all the PCIe setup in bootloader. Unless you want power management...
#asahi · 2021-04-06 14:52
robherThose are only Tegra194 specific registers because we don't have a second user, but 0x8xx registers are DWC port logic registers. One of the extended cap registers lines up with what we used to hard code (I got rid of all the hardcoded offsets recently).
#asahi · 2021-04-06 14:49
robherdrivers/pci/controller/dwc/pcie-tegra194.c:#define GEN3_RELATED_OFF 0x890
#asahi · 2021-04-06 14:49
robherdrivers/pci/controller/dwc/pcie-tegra194.c:#define GEN3_EQ_CONTROL_OFF 0x8a8
#asahi · 2021-04-06 14:49
robher$ git grep -E '(8a8|890)' -- drivers/pci/controller/
#asahi · 2021-04-06 14:49
robherarnd, marcan: Looks like designware controller to me.
#asahi · 2021-04-06 13:21
robhermarcan: We generally try to not have lists of registers. That fine grained is hard to get both right and complete.
#asahi · 2021-03-04 20:30
robherhttps://patchwork.ozlabs.org/project/devicetree-bindings/list/?param=3&page=1
#asahi · 2021-03-04 20:29
robherIt's all in my backlog.
#asahi · 2021-02-11 14:10
robhermarcan: yes
#asahi · 2021-02-11 14:08
robhermarcan, arnd: looks okay to me in terms of semantics. The only thing is we walk up the whole tree for everyone else on every node. I think we should bail out on !apple. See some of the other quirks in that file which save quirk enable/disable in a static var.
#asahi · 2021-02-10 15:40
robhermarcan: Close enough for a prototype. If a property works, then implying from compatible strings can too. (See 'MacRISC' in the DT address code.) But better to discuss that with a concrete implementation and that wouldn't affect most of it.
#asahi · 2021-02-10 14:52
robherI meant whether 'ranges' is empty or not. Empty ranges means inherits parent address space or 1:1 translation. No ranges means not a translatable bus.
#asahi · 2021-02-10 14:47
robhermarcan: Probably recursively or recursively for empty 'ranges' only.
#asahi · 2021-02-10 14:43
robherA flag property or a flags cell work the same way ultimately. It's just inband vs. OOB WRT ranges.
#asahi · 2021-02-10 14:40
robherso the PCI controller picks up the flag from the parent bus for it's regs and PCI children get the flag from the PCI node.
#asahi · 2021-02-10 14:35
robhermarcan: Hopefully only 1 type per bus, but yes.
#asahi · 2021-02-10 14:34
robherLike dma-ranges is supposed to be.
#asahi · 2021-02-10 14:33
robherIdeally those would be in bus nodes.
#asahi · 2021-02-10 14:25
robherarnd: It's own registers are in 'reg' and a default bus and the memory space is in ranges, so that should be okay.
#asahi · 2021-02-10 14:23
robherI'd guess we'd need a way to change the default and then PCI mappings override that.
#asahi · 2021-02-10 14:21
robhermarcan: We don't really need per device do we? It's PCI and not-PCI AIUI.
#asahi · 2021-02-10 14:14
robherIf we have resource flags plumbed, we could just handle it in the DT address code like the other Mac quirks.
#asahi · 2021-02-10 14:13
robherarnd, marcan: I'm not a fan of a flag for this in DT. A new flag in PCI cells would be tolerable, but if we're talking a flag cell on default buses I'd expect that would not work on any existing code. And if OpenBSD doesn't need a flag, neither should Linux.