martinayotte

 View Profile  See their activity

  • Posts

    3889

  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Posts posted by martinayotte

    Bug GUI Armbian on Pinebook

    in Allwinner A64, H5 and H6

    Posted

    On 3/9/2021 at 1:35 PM, derpeter said:

    So while i`m not familiar with the the details of the display init i assume this is not the display but the gpu / drm driver crashing.

    I've tried for months to clarify the reason of such issue ...

    My last working kernel was 5.7.6, and the issue appeared as soon as 5.8.0, I've done "diff" between both branches and I still didn't figured out the glitches ...

    1

    [Warning] NPi K1 Plus (not Pihole) seems to have trouble with kernel 5.11.1

    in General chit chat

    Posted

    55 minutes ago, guidol said:

    seem to make some trouble

    It seems that NanoPi K1 Plus is using rtl8189 WiFi ... Right ?

    Driver is broken in 5.11, I'm working on it with other guys, I'm using OPiPC+/OPiLite/OPiPlus2E.

    In the mean time, if you don't need WiFi, disable the module : 

    mv /lib/modules/5.11.1-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko /lib/modules/5.11.1-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko-disabled

     

    1

    Orange Pi One+ cannot communicate with UART3 on Armbian_21.02.1_Orangepioneplus_buster_current_5.10.12.img.xz

    in Allwinner A64, H5 and H6

    Posted

    50 minutes ago, ebalcsk said:

    I try to communicate on UART3

    Can you check DT if pinctrl-0 is present in UART3 node ?

     

    You can verify using this : 

    ll /proc/device-tree/soc/serial@5000c00

    (In my old 5.9 build, I see that they are missing and only UART0 has its pinctl-0 handle.)

     

    If missing, you can decompile DTB into DTS, edit DTS to add "pinctrl-0 = <phandle>;" where phandle can be found in "uart3-pins" node ...

    0

    Trying to add gpio-line-names to nanopi duo

    in Development

    Posted

    3 hours ago, sgjava said:

    This is the step I'm missing.

    I'm not understanding exactly.

    Maybe because I've always producing patches manually ...

    Here is a summary of how I would do it : 

    (edit the file to add "gpio-line-names" manually)
nano cache/sources/linux-odroidxu4/odroid-5.4.y/arch/arm/boot/dts/exynos5420-pinctrl.dtsi
(save)
pushd cache/sources/linux-odroidxu4/odroid-5.4.y/
git diff arch/arm/boot/dts/exynos5420-pinctrl.dtsi > ~/my-gpio-line-names.patch
popd
mv ~/my-gpio-line-names.patch patches/kernel/odroidxu4-dev/odroidxu4-add-gpio-line-names.patch

     

    0

    Trying to add gpio-line-names to nanopi duo

    in Development

    Posted

    28 minutes ago, sgjava said:

    each pinctrl using phandle to identify

    Be carefull : phandle can vary between builds, so better use <&pio> and <&r_pio> symbols.

     

    30 minutes ago, sgjava said:

    So next question is how do I make this part of build process

    As I said earlier, append you overlay code in some new board specific patch such as ./patch/kernel/sunxi-dev/nanopi-duo/board-h2plus-nanopi-duo-add-overlay.patch which will also provide change to arch/arm/boot/dts/overlay/Makefile.

    0

    Trying to add gpio-line-names to nanopi duo

    in Development

    Posted

    3 hours ago, sgjava said:

    do you have an example for /boot/armbianEnv.txt gpio-line-names?

    I've manually copied my gpio-line-names.dtbo under /boot/dts/overlay/sun8i-h3-gpio-line-names.dtbo

    Then, I added "overlays=gpio-line-names" in /boot/armbianEnv.txt, and rebooted ...

    3 hours ago, sgjava said:

    This is generated board specific, correct?

    Yes, my test was for OrangePiPC+, and tested using libgpiod "gpioinfo" ...

    0