You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very good find, this wrong handling is already in our code since loooong time, at least down to v6.10. Seems like not much users needed any different baudrate than the default 100,000 😄.
Creating a bug report/issue
Required Information
G_DIETPI_VERSION_CORE=6 G_DIETPI_VERSION_SUB=25 G_DIETPI_VERSION_RC=3 G_GITBRANCH='master' G_GITOWNER='MichaIng'
stretch
Linux link 4.19.42-v7+ #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l GNU/Linux
RPi 3 Model B (armv7l)
Steps to reproduce
dietpi-config
to e.g. 10kHzExpected behaviour
dtparam=i2c_arm_baudrate=10000
Actual behaviour
i2c_arm_baudrate=10000
. Thedtparam=
is missing. Because of this, dietpi-config does not change the baudrate effectively.I changed the entry in /DietPi/config.txt manually and then the baudrate changed.
The text was updated successfully, but these errors were encountered: