lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<DC-IRC> [Discord] <shivansps> the last panthor patch is petty much "please merge this already"
<DC-IRC> [Discord] <shivansps> the last panthor patch is petty much a "please merge this already"
<DC-IRC> [Discord] <liwei19920307> Hello everyone, after using Netplan to bind the IP, dmesg will display this information
<DC-IRC> [Discord] <liwei19920307> Indeed, the main storyline is a better choice. I am just testing if the decoding is working properly to compare why the MPP in Fregate is not working
<DC-IRC> [Discord] <liwei19920307> Indeed, the mainline is a better choice. I am just testing if the decoding is working properly to compare why the MPP in Fregate is not working
<DC-IRC> [Discord] <liwei19920307> Is this caused by WOL related issues?
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> [Discord] <amazingfate> It seems so. Find if netplan has related config.
<DC-IRC> [Discord] <mecoblock> Is there are timeline for Armbian on BSP 6.1 (built on mainline 6.1) ? Has anybody tried it or are there no plans for now
PhotoJim has quit [Ping timeout: 255 seconds]
<DC-IRC> [Discord] <Werner> No plans afaik. However Joshua is working hard on it. Maybe someone is willing to adopt his work at some point and add it as source into our build framework. Armbian is usually following mainline as good as possible. Having vendor bsp is just a temporary solution until mainline catches up.
PhotoJim has joined #armbian-rockchip
PhotoJim has quit [Ping timeout: 256 seconds]
PhotoJim has joined #armbian-rockchip
PhotoJim has quit [Ping timeout: 246 seconds]
PhotoJim has joined #armbian-rockchip
PhotoJim has quit [Ping timeout: 264 seconds]
<DC-IRC> [Discord] <mecoblock> yeah I was just wondering, hopefully most of the rk stuff makes it into mainline since they finally based it on something "more" current
PhotoJim has joined #armbian-rockchip
<DC-IRC> [Discord] <narga_64> Focussing the energy on adding rk3588 to mainline is likely better than trying to use the energy on vendor 6.1 instead 😄
<DC-IRC> [Discord] <narga_64> Would someone mind merging this PR to add the latest rk3588 blobs, please? 😃
<DC-IRC> [Discord] <narga_64> https://github.com/armbian/rkbin/pull/25
<DC-IRC> [Discord] <narga_64> I'd like to incorporate them into the Friendlyelec CM3588.
<DC-IRC> [Discord] <narga_64> The blobs can be used for all other rk3588 devices as well.
<DC-IRC> [Discord] <spooky8086> Please be careful updating the blobs on existing rk3588 devices.. If the SPI, eMMC, or SD have a different ddr blob it will lead to ram instability causing systems to crash.
<DC-IRC> [Discord] <narga_64> Thanks for this info!
<DC-IRC> [Discord] <narga_64> Do you mean if two different Linux images are installed on SD card and eMMC? Or if U-Boot uses a different DDR blob than kernel? Or something else?
<DC-IRC> [Discord] <narga_64> How can I check this?
<DC-IRC> [Discord] <narga_64> From the blob release notes, I have the impression that updated blobs often fix issues.
<DC-IRC> [Discord] <spooky8086> The bootloader requires ddr + spl blobs. When you have the bootloader installed on the SPI or eMMC and try to boot from an SD card, the system will use the spl blob from the SPI or eMMC with the ddr blob on the SD card.
<DC-IRC> [Discord] <spooky8086> This causes memory training issues that can be seen in uboot. I can't show an example right now, but not all spl and ddr blobs are compatible.
<DC-IRC> [Discord] <spooky8086> It's confusing and hard to explain.
<DC-IRC> [Discord] <narga_64> Ah that does make sense! Thank you! The release notes above also mention sometimes in the DDR notes "BL31 should be update to V1.41 or above."
<DC-IRC> [Discord] <narga_64> So basically, you need to make sure that the SPL/bl31 blob that U-Boot loads is an updated version as well, correct?
<DC-IRC> [Discord] <narga_64> If you have the bootloader on the image itself/the same storage device, it does not matter since the Armbian board configuration file takes care of that via "DRR_BLOB" and "BL31_BLOB"=... if I understand this correctly.
<DC-IRC> [Discord] <spooky8086> That is correct
<DC-IRC> [Discord] <narga_64> And some devices like NanoPc-T6 do not have "DDR_BLOB" in their board config since it uses mainline U-Boot which I guess already has the blobs included and mainline U-Boot chooses which version gets used?
<DC-IRC> [Discord] <spooky8086> Idk how armbian chooses the blob versions to be used, but it should still need the same blobs.
<DC-IRC> [Discord] <dualtachyon> if there are specific things they want from the BL31 blob, i can have a look. I have reverse engineered the RK BL31 a fair bit
<DC-IRC> [Discord] <mecoblock> you should contact them then, they’re really nice and have always responded to my emails
<DC-IRC> [Discord] <dualtachyon> i will have a look