Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem
On Tue, Oct 17, 2017 at 11:59:17AM +0200, Jean-Louis Mounier wrote:
> Le 16/10/2017 à 22:45, Karsten Merker a écrit :
> > On Mon, Oct 16, 2017 at 09:39:36PM +0200, Jean-Louis Mounier wrote:
> > > => 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
> There may be an issue : yesterday evening, I only started the
> installation, just enough to verify the communication between
> the installer and the repositories. I didn't complete the
> installation.
>
> Maybe I should try a (minimalist) installation and verify that
> the network is still working when the system reboots !
>
> Do you think it is necessary ?
On the A20, a reboot is always a "cold reset" (performed by the
SoC's watchdog), so on reboot u-boot performs exactly the same
initialization sequence as at power-on time. If u-boot gets
changed to initialize PA17 properly during startup, I see no
reason why that shouldn't work on reboot as well, so there is
IMHO no reason to perform another full test installation right
now. For the time being, we'll have to wait and see how the
attempts at getting support for board revision J into mainline
u-boot work out.
Regards,
Karsten
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Reply to: