-
Notifications
You must be signed in to change notification settings - Fork 655
examples/mtdpart:Register MTD devices using the mtd_register method #3130
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
Conversation
35c3954
to
1229352
Compare
please fix:
|
sure, working on this now |
06705ab
to
1c2b33e
Compare
done |
still have ci error, please run checkpatch.sh before you update patch. @jingfei195887 |
babf87b
to
27ba699
Compare
@jingfei195887 please drop merge patch. |
3330ee3
to
e7879e8
Compare
yes this is done |
e7879e8
to
7943646
Compare
1. Due to the automatic wrapping of MTD devices during the open() process, the legacy registration methods ftl_initialize() and bchdev_register() are no longer required for MTD device registration. The new method is now changed to register_mtddriver 2. Some code for space release and deregistration has been added, and certain error handling methods have been updated.
7943646
to
e4a1bec
Compare
Thank you @jingfei195887 :-) Great work! :-) Please remember to |
Thanks for the remind. |
Summary
Due to the automatic wrapping of MTD devices during the open() process, the legacy registration methods ftl_initialize() and bchdev_register() are no longer required for MTD device registration. The new method is now changed to register_mtddriver
Some code for space release and deregistration has been added, and certain error handling methods have been updated.
Test
Run the
examples/mtdpart
in sim:nsh for test an test is passed