diff options
| author | Gabor Juhos <juhosg@openwrt.org> | 2012-01-07 19:36:33 +0000 |
|---|---|---|
| committer | Gabor Juhos <juhosg@openwrt.org> | 2012-01-07 19:36:33 +0000 |
| commit | a56bdeff9d994f6e8e39cd8a0cad571866b27533 (patch) | |
| tree | b9485b060efb44c62a76663bab827fec1c13c238 /target/linux/ramips | |
| parent | 8b567fb508573e35f1acfce638cdc76617c1f0b8 (diff) | |
| download | upstream-a56bdeff9d994f6e8e39cd8a0cad571866b27533.tar.gz upstream-a56bdeff9d994f6e8e39cd8a0cad571866b27533.tar.bz2 upstream-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 'target/linux/ramips')
0 files changed, 0 insertions, 0 deletions