We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I have read a comment that I think you put in the Embedded Controller source code.
"* Some boards have a sing capacitor problem with mode == IDLE. For such
Please can you clarify this statement a little:
I have been trying to make some of my own changes to the EC source code, in order to improve the battery charging behavior and avoid mini-cycles of charge/discharge. You can see my changes so far here: https://github.com/jcdutton/EmbeddedController (charge controller changes) https://github.com/jcdutton/zephyr (general improvements to port80 handling)
I have a FW16 AMD, that does not appear to have the IDLE problem you mentioned above. So, I am curious which boards have the problem?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I have read a comment that I think you put in the Embedded Controller source code.
"* Some boards have a sing capacitor problem with mode == IDLE. For such
Please can you clarify this statement a little:
Please can you describe what happens if one sets IDLE on those main-boards?
I have been trying to make some of my own changes to the EC source code, in order to improve the battery charging behavior and avoid mini-cycles of charge/discharge.
You can see my changes so far here:
https://github.com/jcdutton/EmbeddedController (charge controller changes)
https://github.com/jcdutton/zephyr (general improvements to port80
handling)
I have a FW16 AMD, that does not appear to have the IDLE problem you mentioned above.
So, I am curious which boards have the problem?
The text was updated successfully, but these errors were encountered: