10:04 <kwizart> ha, no luck to open a MR for grate-linux as it was not started as a fork from torvalds... trying to figure out how to deal with that...

11:14 <digetx> forking grate-linux isn't an option?

11:23 <kwizart> right, but that's not what I've done in the first step

13:16 <kwizart> open question for tegra maintainers... I wonder if the series related to simpledrm support have been tested along nvidia "desktop" driver for arm64 ? specially with a kernel that lacks efifb ?

13:17 <kwizart> namely http://patchwork.ozlabs.org/project/linux-tegra/list/?series=328822 and http://patchwork.ozlabs.org/project/linux-tegra/list/?series=328824

13:18 <kwizart> If I understand the series well, it will allow to transition from the firmware setup fb to the OS without flickering (while iommu setup)

13:20 <kwizart> tagr, ^^ (about memory fb series)

13:22 <tagr> kwizart: nope, the simpledrm support is for integrated Tegra display only

13:23 <tagr> it's theoretically possible to do something alike for dedicated GPUs, but it's far simpler to use EFIFB for those

13:24 <tagr> EFIFB doesn't work for Tegra integrated display because EFIFB lacks a way of describing what clocks/resets/power-domains are needed, for discrete GPUs that shouldn't be a problem since that handling is all done within the PCI device

13:30 <kwizart> okay, so no conflict with tegra if efifb is kept enabled for desktop gpu (from a generic distro kernel perspective)

13:49 <tagr> kwizart: I suppose there could be an issue if both the GPU and Tegra initialize display, not sure how (or if) our UEFI implementation handles that