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 | ce48dfe9f2e037cb3cc7a7f646bc9201b7a727d9 (patch) | |
| tree | e8ac1473f955869729dccd7d5090f5e47fa755f5 /target/linux/ubicom32 | |
| parent | dcb14852cf841353b446934f06c94218e9c0fead (diff) | |
| download | master-187ad058-ce48dfe9f2e037cb3cc7a7f646bc9201b7a727d9.tar.gz master-187ad058-ce48dfe9f2e037cb3cc7a7f646bc9201b7a727d9.tar.bz2 master-187ad058-ce48dfe9f2e037cb3cc7a7f646bc9201b7a727d9.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.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29679 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/ubicom32')
0 files changed, 0 insertions, 0 deletions