On 18.01.2018 22:19, Paul Burton wrote:
> When constraining the highest DDR address that U-Boot will use for its
> data & relocated self, we need to handle the common case in which a 32
> bit system with 2GB DDR will have a zero gd->ram_top, due to the
> addition of 2GB (0x80000000) to the base address of kseg0 (also
> 0x80000000) which overflows & wraps to 0.
> 
> We originally had a check for this case, but it was lost in commit
> 78edb25729ce ("boston: Provide physical CONFIG_SYS_SDRAM_BASE") causing
> problems for the affected 32 bit systems.

I think I did a wrong conflict resolution because the patch didn't apply
anymore. I folded this patch into "boston: Provide physical
CONFIG_SYS_SDRAM_BASE" to fix this. Actually I wanted to resend the
updated patches. But if you are okay with the current state in
u-boot-mips/next branch, I'll take them as they are.

BTW: could you resend your series "boston: Ethernet support for MIPS
Boston board"? I still have no Acks or Reviews on the generic DM parts.
Thanks.


-- 
- Daniel

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to