aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/files
diff options
context:
space:
mode:
authorEddi De Pieri <eddi@depieri.net>2016-11-08 17:38:03 +0100
committerMathias Kresin <dev@kresin.me>2016-11-12 21:04:15 +0100
commit07bc0d60898d812f3c5793d4c020e748342176b2 (patch)
tree66c46c15829fad5330b6dfb7630b988d5533e0bc /target/linux/lantiq/files
parentfc93494066c43d7cf77219a633c805cc9e984b67 (diff)
downloadupstream-07bc0d60898d812f3c5793d4c020e748342176b2.tar.gz
upstream-07bc0d60898d812f3c5793d4c020e748342176b2.tar.bz2
upstream-07bc0d60898d812f3c5793d4c020e748342176b2.zip
lantiq: fix pci issue if mem kernel parameter is used
As specified by e0229a16b0001c08e6c2611fa0bb9814507fced4 if the VR9 based router provides FXS ports and they should enabled then the following must added to the kernel command line: mem=[TOTALMEMSIZE-2M] vpe1_load_addr=ADDRESS vpe1_mem=2M By adding mem= parameter a pci device stop working correctly. The pci-lantiq.c module use get_num_physpages() to compute dynamically the memory amount of the board. The mem= make the module to compute in the wrong way the BAR11MASK, so in this situation the mask is misaligned with the dma area that the hardware expects. This patch is a port of what legacy ifxmips_pci.c does. Signed-off-by: Eddi De Pieri <eddi@depieri.net>
Diffstat (limited to 'target/linux/lantiq/files')
0 files changed, 0 insertions, 0 deletions