Skip to content

Conversation

@mrkozmic
Copy link

spi_nor_write returned bytes written (retlen) from the last call to nor->write
If nor->write was called several times the returned retlen would be smaller than expected by jffs2, even if writing was successful.

The following message would appear:
jffs2: Write of 183 bytes at 0x003e02ac failed. returned 0, retlen 167

mrkozmic added 2 commits June 28, 2016 16:59
spi_nor_write returned bytes written (retlen) from the last call to nor->write
If nor->write was called several times the returned retlen would be smaller than expected by jffs2, even if writing was successful.

The following message would appear: 
jffs2: Write of 183 bytes at 0x003e02ac failed. returned 0, retlen 167
Some drivers implementing nor->write might not reset *retlen every time nor-write is called, 
thus accumulating bytes written. We can zero *retlen here since we are counting bytes written in retlen_l*/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant