Hello,
Please try to insert udelay() calls in addition to dsb() in the
mctl_mem_matches()
and see if this helps. I suspect that there's just no way to do
perfectly reliable
synchronization all the way from the CPU to DRAM and back in this particular
scenario (which involves wacky things, such as a
Hi Stephen,
On 29/11/2023 18:45, Stephen Graf wrote:
Some testing results:
With the default DRAM timing of 30x24=720, most often when my system
boots it comes up with DRAM 2G, but I have a 1G system. Once in a while
the boot shows 1G. When it shows 2G the linux OS also shows 2G and
continui
Some testing results:
With the default DRAM timing of 30x24=720, most often when my system
boots it comes up with DRAM 2G, but I have a 1G system. Once in a while
the boot shows 1G. When it shows 2G the linux OS also shows 2G and
continuing does not make much sense.
On one boot where u-boot
3 matches
Mail list logo
