07-16-2018, 07:44 AM
It seems that the way things are, the devices are not enablet right away. However, they can be enabled via "dts overlays", essentially additional changes to the internal "device tree" structure.
See https://github.com/ayufan-rock64/linux-b...al-devices
There is an example there of enabling a network interface. I found that I could enable the i2c-0 bus (the one on pins P3 and P5) by the following command, run as root:
enable_dtoverlay i2c0 i2c@ff150000 okay
where the names such as "i2c@ff150000" are found in the device-tree-source file on the github repository:
https://github.com/ayufan-rock64/linux-k...k3328.dtsi
Now, note that a number of GPIOs are already in use for various other purposes (the SPI for exampe is used for an on-board memory chip) and might not be readily available.
To have this happen on startup, put it into /etc/rc.local
See https://github.com/ayufan-rock64/linux-b...al-devices
There is an example there of enabling a network interface. I found that I could enable the i2c-0 bus (the one on pins P3 and P5) by the following command, run as root:
enable_dtoverlay i2c0 i2c@ff150000 okay
where the names such as "i2c@ff150000" are found in the device-tree-source file on the github repository:
https://github.com/ayufan-rock64/linux-k...k3328.dtsi
Now, note that a number of GPIOs are already in use for various other purposes (the SPI for exampe is used for an on-board memory chip) and might not be readily available.
To have this happen on startup, put it into /etc/rc.local