summaryrefslogtreecommitdiffstats
path: root/tools/m4
diff options
context:
space:
mode:
authorGabor Juhos <juhosg@openwrt.org>2012-01-07 19:36:33 +0000
committerGabor Juhos <juhosg@openwrt.org>2012-01-07 19:36:33 +0000
commita56bdeff9d994f6e8e39cd8a0cad571866b27533 (patch)
treeb9485b060efb44c62a76663bab827fec1c13c238 /tools/m4
parent8b567fb508573e35f1acfce638cdc76617c1f0b8 (diff)
downloadmaster-31e0f0ae-a56bdeff9d994f6e8e39cd8a0cad571866b27533.tar.gz
master-31e0f0ae-a56bdeff9d994f6e8e39cd8a0cad571866b27533.tar.bz2
master-31e0f0ae-a56bdeff9d994f6e8e39cd8a0cad571866b27533.zip
ar71xx: allow to specify max read size for m25p80
Reading from the flash chip on the TL-WR2543ND seems buggy. If the SPI flash driver tries to read too much data in one SPI transfer, the flash chip returns bogus values. This can be caused by a buggy flash chip on my board, or it can be a bug in our SPI driver. Add a workaround to the m25p80 driver until I find out the root cause of the problem. The patch allows to specify the maximum numner of bytes which can be read safely withint one SPI transfer. SVN-Revision: 29679
Diffstat (limited to 'tools/m4')
0 files changed, 0 insertions, 0 deletions