-
Notifications
You must be signed in to change notification settings - Fork 17.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename AP_Logger_DataFlash to AP_Logger_JEDEC #26322
Rename AP_Logger_DataFlash to AP_Logger_JEDEC #26322
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't agree with this naming change. JEDEC is an organization that controls many, many specs. Why is DataFlash confusing? I think you should pick a name that actually makes sense. I would, for instance, be ok with AP_Logger_Flash.
Is W25N01GV not a flash chip?! Would you be happy with |
Rename to |
How about black box? |
Rather too generic, I think? This is a driver for hardware which speaks a specific set of opcodes, you could foresee other standards in use there. |
So I spent a couple of hours trying to hunt down the standard these opcodes follow. Couldn't find one. I've seen them references as "Industry Standard Opcodes", frequently by the JEDEC name ("JEDEC READ ID"), and sometimes by one of the original implementers ("M25P80 opcodes"). I was fully expecting to be able to reference a JEDEC standard number, but I can't find one. Linux has gone with "spinor" to describe them: https://github.com/torvalds/linux/blob/master/include/linux/mtd/spi-nor.h#L21 So we could make this |
da7198c
to
2a172f3
Compare
The naming if this driver class is really confusing!
This is just one of the dataflash backends we support, the other being the W25N01GV.
Done as two commits, one to rename the files, the second to adjust for the renaming.