On Mon, Oct 16, 2017 at 09:39:36PM +0200, Jean-Louis Mounier wrote:
for some reasons, I changed my mail configuration and I
discovered your last request very recently (!) Sorry for the
delay. Now I keep an eye on the bug thru the bug web page.
I discovered a new installer release but the bug is still
present.
Now the test :
=> gpio clear PA17
gpio: pin PA17 (gpio 17) value is 0
=>run bootcmd
after that, the installer got IPV4 and IPV6 addresses wwith DHCP and then
ran fine.
Hope it helps
Yes, that helps as it confirms that a change in u-boot alone is
enough to work around the issue in Linux as well (although it is
debateable whether the kernel should rely on the bootloader in
this case or not). There has recently been an attempt to address
the issue in mainline u-boot, but that didn't work out as planned
and the patch got rejected:
https://lists.denx.de/pipermail/u-boot/2017-September/307778.html
Regards,
Karsten