On Mon, Jul 24, 2017 at 10:51:12PM +0200, Mark Kettenis wrote:
> > Date: Mon, 24 Jul 2017 23:07:00 +0300
> > From: Artturi Alm <[email protected]>
> > 
> > On Sun, Jul 23, 2017 at 07:45:53PM +0200, Mark Kettenis wrote:
> > > > Date: Sat, 22 Jul 2017 11:21:31 +0300
> > > > From: Artturi Alm <[email protected]>
> > > > 
> > > > Hi,
> > > > 
> > > > anyone else having issues with sxie? w/bsd.rd from latest snapshot
> > > > it was unable to get ip from dhcpd even.
> > > > 
> > > > this is what it does look like at the other side:
> > > > 
> > > > 11:01:15.170089 e6:29:5b:e9:e6:29 5b:e9:e6:29:5b:e9 5be9 342: 
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629
> > > > 11:01:15.170353 e6:29:5b:e9:e6:29 5b:e9:e6:29:5b:e9 5be9 342: 
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629 5be9 e629 5be9 e629 5be9
> > > >                          e629 5be9 e629
> > > > 
> > > > just to make sure there was nothing physically wrong in my setup,
> > > > i attached usb-ethernet(axen), and got the ip like expected, this
> > > > was in a row to the earlier garbage w/o rebooting in between.
> > > > 
> > > > i haven't used it for like a year, so got no time frame when this
> > > > has appeared, anyone w/ideas?
> > > > -Artturi
> > > 
> > > I'm upgrading my A10s-ALinuXino-Micro over sxie(4), so the driver
> > > defenitely still works for me.
> > > 
> > 
> > That's good. Do you know if u-boot did init it? In my case i'm quite
> > sure the u-boot i used did not, and i'm now guessing just by quick
> > look at sxie.c, that iirc. there was some ugly hack somewhere to enable
> > the use of some sram section in memory for the emac, and since i saw no
> > trace of that hack in sxie.c, maybe it was elsewhere and got cleaned up?
> > meaning sxie would rely on u-boot to work? i'll test when i have a free
> > sd-card, will let you know.
> 
> Yes, U-Boot initializes the network interface.

Regression in /usr/local/share/u-boot/Cubieboard/u-boot-sunxi-with-spl.bin,
w/2017.03 it is working:

U-Boot SPL 2017.03 (Apr 03 2017 - 12:27:12)
DRAM: 1024 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1


U-Boot 2017.03 (Apr 03 2017 - 12:27:12 -0600) Allwinner Technology

CPU:   Allwinner A10 (SUN4I)
Model: Cubietech Cubieboard
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c0b000


and with current(.05) it doesn't:

U-Boot SPL 2017.05 (Jul 11 2017 - 16:35:33)
DRAM: 1024 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1


U-Boot 2017.05 (Jul 11 2017 - 16:35:33 -0600) Allwinner Technology

CPU:   Allwinner A10 (SUN4I)
Model: Cubietech Cubieboard
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   No ethernet found.


i guess that means, we either hope u-boot 2017.07 will fix this, or add
the likely missing handling of "allwinner,sun4i-a10-sram-a3-a4"-compatible ?
this is such a minor thing, that i hope you won't waste time on this anymore
than deciding what should be done, and maybe ease my curiosity if the success
you've had was w/2017.05 or not? :)

i cc'ed maintaineri, as i failed to build .07, and in case he would have any
news about progress w/upgrade to it? or if the u-boot changelog for between
.05 and .07 has been considered unworthy of the port-update?
-Artturi

Reply via email to