Hi, >> Tegra124 requires the bootloader to perform VPR initialization, otherwise the >> GPU cannot be used by the system. Since using the GPU without that >> initialization results in a hang, the GPU DT node is left disabled, and it is >> the task of the bootloader to enable it after ensuring it is safe to use the >> GPU. >> >> VPR init is already performed since patch df3443dfa449, but the device tree was >> left untouched. This patch series performs this last step and prepares the GPU >> intialization code to receive more code for newer chips. > > Tested-by: Andreas Färber <afaerber@xxxxxxx> > > I've tested this patchset on v2015.07 with 4.2.0-rc3-00115-gc5dfd65 - > with these two patches I get a console login on HDMI again. > > However, I'm still having trouble with X11... Should that be working > with linux.git? (haven't tried linux-next.git yet) My understanding is that it's not or you need to use glamour to do so, wayland in theory should work. > Among other errors, it seems that nouveau is looking for firmware > nouveau/nvea_fuc409c and nouveau/fuc409c - who should be providing that? > It's not in linux-firmware.git [1], and I see no /dev/mmcblk0p* to check > whether the original system has such a file (which I doubt, given the > nouveau naming). It then falls back to the tegra drm iiuc. Details of the changes with firmware loading in this patch series here, likely need the patches, or maybe newer ones for it to work: http://www.spinics.net/lists/dri-devel/msg84828.html Firmware landed upstream here: https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=899ebcb6812681b91cf2dfd390574b478c612442 > With -rc2 I've seen the system freeze, with -rc3 just not behaving as > expected when starting X (with ssh/serial remaining usable). Without the above patchset I've seen the lockups too. Peter -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
