going

Members
  • Posts

    157
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

going's Achievements

  1. To return the system to its original state, you need to delete this file: sudo rm /etc/kernel/postinst.d/zz-sync-dtb Then update the repository with test packages and install the two packages. cd deb git pull cd nanopineo sudo dpkg -i linux-dtb-current-sunxi_22.05.0-trunk_armhf.deb linux-image-current-sunxi_22.05.0-trunk_armhf.deb This will update (install with replacement) your kernel and dtb. Don't do anything with the 5.17 kernel. It works and will be a backup in case something goes wrong in the future. You can switch to it by simply correcting the links.
  2. @Igor I checked for kernel 5.15. Interfaces are being created. If we accept these changes today, will they have time to enter the release? leo@orangepipc2:~$ uname -r 5.15.35-sunxi64 leo@orangepipc2:~$ find /sys/ -name '*spi*' find: ‘/sys/kernel/debug’: Permission denied /sys/class/devlink/platform:1c20800.pinctrl--platform:1c68000.spi /sys/class/devlink/platform:1c20800.pinctrl--platform:1c69000.spi /sys/class/devlink/regulator:regulator.0--spi:spi2.0 /sys/class/spidev /sys/class/spidev/spidev1.0 /sys/class/spi_slave /sys/class/spi_master /sys/class/spi_master/spi2 /sys/class/spi_master/spi1 /sys/devices/platform/reg-dummy/regulator/regulator.0/consumer:spi:spi2.0 /sys/devices/platform/reg-dummy/regulator/regulator.0/spi2.0-vdd /sys/devices/platform/soc/1c68000.spi /sys/devices/platform/soc/1c68000.spi/spi_master /sys/devices/platform/soc/1c68000.spi/spi_master/spi2 /sys/devices/platform/soc/1c68000.spi/spi_master/spi2/statistics/spi_async /sys/devices/platform/soc/1c68000.spi/spi_master/spi2/statistics/spi_sync_immediate /sys/devices/platform/soc/1c68000.spi/spi_master/spi2/statistics/spi_sync /sys/devices/platform/soc/1c68000.spi/spi_master/spi2/spi2.0 /sys/devices/platform/soc/1c68000.spi/spi_master/spi2/spi2.0/statistics/spi_async /sys/devices/platform/soc/1c68000.spi/spi_master/spi2/spi2.0/statistics/spi_sync_immediate /sys/devices/platform/soc/1c68000.spi/spi_master/spi2/spi2.0/statistics/spi_sync /sys/devices/platform/soc/1c68000.spi/spi_master/spi2/spi2.0/spi-nor /sys/devices/platform/soc/1c69000.spi /sys/devices/platform/soc/1c69000.spi/spi_master /sys/devices/platform/soc/1c69000.spi/spi_master/spi1 /sys/devices/platform/soc/1c69000.spi/spi_master/spi1/statistics/spi_async /sys/devices/platform/soc/1c69000.spi/spi_master/spi1/statistics/spi_sync_immediate /sys/devices/platform/soc/1c69000.spi/spi_master/spi1/statistics/spi_sync /sys/devices/platform/soc/1c69000.spi/spi_master/spi1/spi1.0 /sys/devices/platform/soc/1c69000.spi/spi_master/spi1/spi1.0/statistics/spi_async /sys/devices/platform/soc/1c69000.spi/spi_master/spi1/spi1.0/statistics/spi_sync_immediate /sys/devices/platform/soc/1c69000.spi/spi_master/spi1/spi1.0/statistics/spi_sync /sys/devices/platform/soc/1c69000.spi/spi_master/spi1/spi1.0/spidev /sys/devices/platform/soc/1c69000.spi/spi_master/spi1/spi1.0/spidev/spidev1.0 /sys/devices/platform/soc/1c20800.pinctrl/consumer:platform:1c68000.spi /sys/devices/platform/soc/1c20800.pinctrl/consumer:platform:1c69000.spi /sys/devices/virtual/devlink/platform:1c20800.pinctrl--platform:1c68000.spi /sys/devices/virtual/devlink/platform:1c20800.pinctrl--platform:1c69000.spi /sys/devices/virtual/devlink/regulator:regulator.0--spi:spi2.0 find: ‘/sys/fs/pstore’: Permission denied find: ‘/sys/fs/bpf’: Permission denied /sys/bus/platform/devices/1c68000.spi /sys/bus/platform/devices/1c69000.spi /sys/bus/platform/drivers/sun6i-spi /sys/bus/platform/drivers/sun6i-spi/1c68000.spi /sys/bus/platform/drivers/sun6i-spi/1c69000.spi /sys/bus/platform/drivers/sun4i-spi /sys/bus/spi /sys/bus/spi/devices/spi2.0 /sys/bus/spi/devices/spi1.0 /sys/bus/spi/drivers/spidev /sys/bus/spi/drivers/spidev/spi1.0 /sys/bus/spi/drivers/mmc_spi /sys/bus/spi/drivers/spi-nor /sys/bus/spi/drivers/spi-nor/spi2.0 /sys/firmware/devicetree/base/soc/pinctrl@1c20800/spi1-pins /sys/firmware/devicetree/base/soc/pinctrl@1c20800/spi0-pins /sys/firmware/devicetree/base/soc/spi@1c69000 /sys/firmware/devicetree/base/soc/spi@1c69000/spidev@0 /sys/firmware/devicetree/base/soc/spi@1c69000/spidev@0/spi-max-frequency /sys/firmware/devicetree/base/soc/spi@1c68000 /sys/firmware/devicetree/base/soc/spi@1c68000/flash@0/spi-max-frequency /sys/firmware/devicetree/base/soc/spi@1c68000/spi-flash@0 /sys/firmware/devicetree/base/soc/spi@1c68000/spi-flash@0/spi-max-frequency /sys/firmware/devicetree/base/aliases/spi1 /sys/firmware/devicetree/base/__symbols__/spi0 /sys/firmware/devicetree/base/__symbols__/spi1 /sys/firmware/devicetree/base/__symbols__/spi1_pins /sys/firmware/devicetree/base/__symbols__/spi0_pins /sys/module/spidev /sys/module/spidev/drivers/spi:spidev leo@orangepipc2:~$ ls /dev/spi* /dev/spidev1.0
  3. Today I have collected and added packages for 5.15 CURRENT here: https://github.com/The-going/PKG_test/tree/master/nanopineo @chouchou @mdrmdr Can I ask you to check this too?
  4. Good questions. Don't worry. We will return your system to its original state after the changes are accepted and updates are released. I'll report here.
  5. @mdrmdr The dtb files are already contained in the kernel package and installed in this location: /usr/lib/linux-image-$version This script, which currently exists on your system, copies them to the /boot folder. You don't need the dtb package, but you will have to fix the links in the /boot folder every time after updating the kernel. If you delete this script, then you will need a dtb package, that is, the system will return to the state it was before this experiment.
  6. @mdrmdr You will need to remove the linux-dtb-current-sunxi package and update the linux-image-current-sunxi package. This should be done after these changes are included in the update package. You don't need to touch what is working now.
  7. Who wants to test for sunxi64? @Erol @Falcounet https://github.com/The-going/PKG_test/blob/master/5.15-sunxi64/README.txt
  8. In the latest versions of the kernel, the recommended mechanism for loading and initializing kernel modules is to call its alias, which are contained in the **_device_id structure. At the same time, there remains a mechanism that is contained in the of_device_id structure for compatibility with old software that should work. Thus, we do not need to change or fix anything in the kernel. We'll just use the recommendation, add our alias and call this module by matching it with this alias. It will be right from the point of view of support in the long run. @Falcounet If you can test the 5.15 kernel, I will build packages for sunxi64 and also upload them for download. Please publish your OS and the name of the equipment that is connected via the SPI.
  9. @mdrmdr You need to wait for this change to be accepted. See what this command tells you right now. apt list --upgradable | grep '^linux'
  10. The changes that are used in this test. https://github.com/armbian/build/pull/3737
  11. Just test the operation of the equipment for a few days. And tell me if everything is okay. Fixed it
  12. Yes. Everything is right. That's what needs to be done.
  13. @mdrmdr https://github.com/The-going/PKG_test/blob/master/nanopineo/README.txt