On 05/01/16 18:42, Krzysztof Kozlowski wrote: > On Sun, May 01, 2016 at 06:01:08PM +0200, Hans Verkuil wrote: >>> Sorry, I meant the hanging issue I got in 4.6, not the ethernet issue. >>> I get the same problem with linux-next. Can you mail me the .config you are using? >> >> Never mind. >> >>> After some more testing I don't think it is hanging, instead it seems that the mmc >>> isn't enabled/found and so it just sits waiting for the root partition to appear. >> >> That was fun. There are two problems that both caused the boot to end at the same >> place: first of all the root partition is now called mmcblk1p1 instead of mmcblk0p1 >> in 4.6, so it was just waiting for the root partition to appear. Nothing to do with >> your patch series, just unexpected. > > Yes, annoying issue and unfortunately this is known... recommended > solution is to use root=PARTUUID=xxxx (you can get the PARTUUID with > blkid)... or replace the mmc device. > >> The second is that enabling CONFIG_VIDEO_S5P_FIMC causes the boot to hang at that >> same place. I suspect there is a deadlock somewhere. I'm digging deeper into that >> but again, unrelated to your patch series. >> >> Anyway, after disabling that config option I was finally able to test your patch >> series: >> >> Tested-by: Hans Verkuil <hans.verkuil@xxxxxxxxx> BTW, one thing I noticed is that to have u-boot detect the network device I need to call 'usb reset' twice. This is with u-boot 2016.1 release. Not a big deal, but I wondered if you see the same. Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
