Jump to content

zeekoe

Members
  • Posts

    19
  • Joined

  • Last visited

Everything posted by zeekoe

  1. No dtb.back on debian it seems... Thanks for your help!
  2. Yay! For others with similar problems: downgraded kernel with armbian-config (System > Other) to 5.10.60 Restored device tree (which is probably only needed if you messed it up in the first place; armbian-config > System > Dtc) to spi@ff130000 { compatible = "rockchip,rk3288-spi\0rockchip,rk3066-spi"; clocks = <0x07 0x43 0x07 0x154>; clock-names = "spiclk\0apb_pclk"; dmas = <0x1f 0x0f 0x1f 0x10>; dma-names = "tx\0rx"; interrupts = <0x00 0x2e 0x04>; pinctrl-names = "default"; pinctrl-0 = <0x28 0x29 0x2a 0x2b 0x2c>; reg = <0x00 0xff130000 0x00 0x1000>; #address-cells = <0x01>; #size-cells = <0x00>; status = "okay"; max-freq = <0x2faf080>; phandle = <0x95>; spidev@0 { compatible = "rockchip,spi_tinker"; reg = <0x00 0x00>; spi-max-frequency = <0x2faf080>; spi-cpha = <0x01>; }; spidev@1 { compatible = "rockchip,spi_tinker"; reg = <0x01>; spi-max-frequency = <0x2faf080>; spi-cpha = <0x01>; }; }; Note that phandle is different. I know not much about device tree, but this seems to be a sequence number.
  3. Thanks for your reply. While thinking further, I can vaguely remember that this error/warning was not new. So it might as well not be related to my problem. I found this: That could be my real problem. Might be of help to others, too, that fail after upgrade. I think I messed up the device tree thingy, if I get it restored, will post here again...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines