On 2016-07-19 11:40 -0700, Martin Michlmayr wrote: > I tracked it down to CONFIG_ARM_TEGRA_DEVFREQ which I enabled in > 4.6-1~exp2. > > With this module enabled, I see the same hang you do. Without the > module, it works. > > Interestingly, it depends on the version of u-boot used, though. > With the u-boot from Debian (i.e. a current mainline DENX u-boot), I > do not get this issue (which is why my tests before enabling the > module didn't find it). I only see it with the old u-boot from > NVIDIA. > > I brought this up upstream: > http://permalink.gmane.org/gmane.linux.ports.tegra/26941 > and the response was that if mainline u-boot works, I should use that. > > I then edited the Debian wiki to remove the portions about the old > u-boot and made it clear users have to upgrade to Debian's u-boot. > > IMHO it should be ok to tell users to use a modern mainline u-boot, > but I don't mind disabling CONFIG_ARM_TEGRA_DEVFREQ again either > if you think that's a good idea. OK. I've confirmed that. (and that programing the debian uboot needs the old R19.3 flash tools, otherwise it just makes the board totally dead). So yes, as it all works with the Debian bits and we've documented the wrinkles on https://wiki.debian.org/InstallingDebianOn/NVIDIA/Jetson-TK1 I guess that's OK, although it is likely to catch some people out if they aren't reading that page. It would be good to work out the runes for flashing just the uboot with lower-level tools, and automating the setting of the uboot runes as much as possible. I guess we can call this bug closed, as it's not the kernel that's at fault. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
Attachment:
signature.asc
Description: Digital signature