RFC arm: socfpga: Usability fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 35 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 35 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [PATCH 00/35][RFC] arm: socfpga: Usability fixes
Quoted 7 lines · Marek Vasut
Quoted 6 lines · Chin Liang See
Dear Wolfgang,
Quoted 3 lines · ZY - wd
Dear Chin Liang See,
In message <[email protected]> you
Quoted 12 lines · wrote:
Quoted 12 lines
Quoted 11 lines
Quoted 5 lines
Hmmm... actually I can get it works well for my Altera dev kit. The
get_dram_sizewould take in the argumentPHYS_SDRAM_1_SIZE. From here, the function will ensure the memory specified can read and writable. If its failing here, probably the SDRAM access might have issue. FYI,PHYS_SDRAM_1_SIZEis0x40000000for 1GB.Normally,
get_dram_size()would be called with a size argument that is _larger_ (twice as big) as the biggest possible memory configuration on the respective device. Otherwise it can only detect smaller memory sizes, but would fail to detect if a bigger memory device is installed by accident.
Quoted 7 lines
Quoted 3 lines
Yup, you are right. But currently, the memory space after the SDRAM is a bridge to FPGA. We will get data abort when trying to read that area (for a blank FPGA).
This is good, no ? If you reliably get DABT if the H2F bridge is disabled, you can place the trampoline into the DABT vector and detect DRAM size. I'll have to test this.
Aw snap, on my hardware, when I access past SDRAM, I am getting a wrap around. What's worse is that I can reliably read and write from that location. This renders get_ram_size() unusable. All right, guys, ideas ?
Best regards,
Marek Vasut