Package: x-loader
Version: 1.4.4git20100713-1ubuntu2
The patch debian/patches/support_micron_and_numonyx_memory.patch adds support for Numonyx RAM. However when it programs the SDRC it sets up the two banks CS0 and CS1 so that they overlap in memory:
__raw_writel(0x2, SDRC_CS_CFG); /* 256MB/bank */
__raw_writel(SDP_SDRC_MDCFG_0_DDR_NUMONYX_XM, SDRC_MCFG_0);
__raw_writel(SDP_SDRC_MDCFG_0_DDR_NUMONYX_XM, SDRC_MCFG_1);
where SDP_SDRC_MDCFG_0_DDR_NUMONYX_XM is 0x04590019 (possibly with some bits in the BANKALLOCATION field also set). In the SDRC_MCFG_p register bits [17:8] specify the RAMSIZE in units of 2MB. So here the value is 0b01_0000_0000 ie 256*2MB == 512MB. So we're saying that CS0 (and CS1) are banks of 512MB of RAM, but we're setting SDRC_CS_CFG to put them just 256MB apart in the address space.
I'm not sure what this does in the hardware, but it definitely causes problems in qemu : https://bugs.launchpad.net/qemu-maemo/+bug/651332
This doesn't happen for the Micron RAM configuration because there the value we write into the MCFG registers is 0x03588019 | B_ALL, which specifies a 256MB RAMSIZE and the separation is correct.
Either the Numonyx RAM is 512MB a bank (in which case the CS_CFG should be set to 4) or it is 256MB a bank like the Micron, in which case the MCFG values should be changed.
I'm not sure what the source of the patch is that is being used, but you are correct that it is wrong.
Numonyx is 512MB/bank, currently a single bank, but if configured properly the code will work with a future 2 bank 1GB part.
This patch is done properly in my x-load git repo:
http://
I'm also not sure what "upstream" is being used for x-load, so can't say for certain that the patch in my tree will apply cleanly.