["Orange Pi PC - OP0600" "Armbian 22.11.1 Jammy XFCE" no /dev/spi* device(s)]

you need to check your uboot log whether dt overlays are applied.

[Can't login serial console]

check your console tools (minicom) config.

[pcduino8 uno]

10 hours ago, microdoc said:

I built a new kernel from 6.1.0-rc6

 

I think you are using debian official kernel, or build from it. I think you need to check the patches from armbian, cherry pick some to rebuild debian kernel.

 

 

[Moxa firmware missing]

Quote

apt-file search moxa

firmware-misc-nonfree: /lib/firmware/moxa/moxa-1110.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1130.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1131.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1150.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1151.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1250.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1251.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1410.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1450.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1451.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1613.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1618.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1653.fw
firmware-misc-nonfree: /lib/firmware/moxa/moxa-1658.fw
 

 

[This kernel does not include the required loadable module support]

17 hours ago, Gunwoo Gim said:

I tried installing linux-image-arm64 from the debian repo. but it didn't manage to boot, or even output anything on screen.

 

I guess already use mainline uboot? right? if you are still using verdor uboot, debian kernel missing 1 patch to support boot mainline kernel on vendor uboot.

 

I have added configs to enable debian kernel to support amlogic socs, tested A311d, S905x3 should also be supported.

I guess you have wrong boot method, suggest you to use extlinux.conf install of boot.scr (local boot)

 

install `u-boot-menu` and use extlinux.conf as boot menu to boot debian's kernel.

 

if this not work, I suggest you to use `debootstrap` to rebuild your system, if you know how to configure system to bootable.

 

 

[This kernel does not include the required loadable module support]

17 hours ago, Gunwoo Gim said:

Hi, I'm trying to use ZFS but the kernel I'd like to use doesn't support loadable modules. The version is 22.08.4 at the moment (5.10.147)

Can I use zfs-dkms on linux-image-current-meson64?

 

just install linux-image-arm64 from official debian repo, if missing some feature, just replace the dtb, then install zfs-dkms.

[RX today: Error: No interface matching "end0" found in database.]

On 11/2/2022 at 8:26 PM, OLE_G said:

2: end0: <BROA

please change eth0 to end0

[Weird Boot Message]

On 11/10/2022 at 8:39 AM, moosemen said:

[256]write_leveling error
[258]read_calibration error
[262]write_leveling error

 

these are dram initial logs.

[Can't enable the Bluetooth on Tinkerboard]

/dts-v1/;
/plugin/;

/ {
    fragment@0 {
		target = <&uart0>;

		__overlay__ {
			pinctrl-0 = <&uart0_xfer>, <&uart0_cts>, <&uart0_rts>;
			bluetooth {
				compatible = "realtek,rtl8723bs-bt";
  				device-wake-gpios = <&gpio4 26 0>;
				host-wake-gpios = <&gpio4 31 0>;
				enable-gpios = <&gpio4 29 1>;
			};
		};
    };
};

 

dtc -I dts -O dtb bt.dts -o bt.dtbo

 

would you like to try this dtbo?

[Can't enable the Bluetooth on Tinkerboard]

https://lore.kernel.org/all/20190217121513.22965-4-beagleboard@davidjohnsummers.uk/

[Tmall MAGIC BOX 3(M17) s905x Can not boot]

if you want to try VIM's u-boot, armbain supports VIM, you can download armbian and flash it to SD card.

 

https://www.armbian.com/khadas-vim1/

[Tmall MAGIC BOX 3(M17) s905x Can not boot]

due to no vendor binary blobs to build uboot, restore to vendor OS is the only way to unbrick. these binary blobs are for memory init, power sequency.

now your device is bricked, you can just try VIM's u-boot or p212's u-boot.

 

只能重新刷成出厂的云OS。你看看国内论坛有没有。例如：znds.com等。

既然你的设备已经坏了，可以试试VIM. 或 p212的u-boot。这样可以重新安装成Linux/Armbian，但安卓/云OS只不能了。

不懂可以私信我。

[Efforts to improve video performance on meson64 based TV boxes]

`--opengl-pbo` is needed when use lima.

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

U-boot.bin

boot.scr

meson-gxm-magicbox-m16s.dtb

u-boot.bin boot.scr meson-gxm-magicbox-m16s.dtb

[Armbian file server, need hardware advice]

I think many of us want to use arm sbc as NAS, but remember, your data is expensive, but you put it on cheep server...

at least you need an arm device designed for NAS, not any SBC.

 

 

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

I suddenly understand why they don't accept new board patches, normally 5.19 would be release, and 5.20 merge window would be opened, and only fix would be accept. but due intel silicon bug, everything are delayed.

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

Thank you for telling about Amlogic maintainer will not merge new boards. I have more time for more investigation on vendor OS to find more.

 

could I add Co-develeped-by you in furture patches?

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

for 

11 hours ago, chewitt said:

This is the default sdio_pwrseq node (inherited from include): https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/amlogic/meson-gx-p23x-q20x.dtsi#L94-L99  - it is in the top/indented section. So if you add the node to your board dts (to override a property) the node should be in the same top/indented section, not the 'body' area.

 

is below correct?

 

/ {
        compatible = "tmall,magicbox-m16s", "amlogic,s912", "amlogic,meson-gxm";
        model = "Tmall MagicBox M16S";

        gpio-keys {
                compatible = "gpio-keys-polled";
                poll-interval = <100>;

                key-power {
                        label = "power";
                        linux,code = <KEY_POWER>;
                        gpios = <&gpio_ao GPIOAO_2 GPIO_ACTIVE_LOW>;
                };
        };
                  
       sdio_pwrseq :emmc-pwrseq {
           reset-gpios = <&gpio GPIODV_2 GPIO_ACTIVE_LOW>;
       };
};

 

 

 

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

gpio-241 (sdio_wifi ) in lo GPIOX_7  

 

interrupt-parent = <&gpio_intc>;
           interrupts = <96 IRQ_TYPE_EDGE_RISING>; //89 + 7; GPIOX irq number from 89.. 

 

gpio-251 (bt_rfkill ) in lo   GPIOX_17 ( the name is bt_rfkill, but its direction is in, thus it is interrupt.

interrupt-parent = <&gpio_intc>;
           interrupts = <106 IRQ_TYPE_EDGE_RISING>;

 

both gpios are normal low, thus rising edge for irq.

 

 

and Vendor OS log:

<6>[ 0.538183] c0 1 (swapper/0) aml_wifi wifi.33: [wifi_dev_probe] interrupt_pin=241

<6>[ 0.538190] c0 1 (swapper/0) aml_wifi wifi.33: [wifi_dev_probe] irq_num=100, irq_trigger_type=1

 

take me sometime to understand gpio to irq number....

 

now left device side wakeup-pin.... this is too difficult.

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

I don't have any line of code. just have the box.

 

here is an example of this wifi/bt module. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi?h=v5.19-rc8#n402

 

 

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

no, according its bindings file, it's SDIO device or USB device, no UART device type.

 

I think I need postpone wifi/bt node, because, I need to enable gpio_intc, I think it may different to default value. need time.

 

 

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/net/marvell-bt-8xxx.txt?h=v5.19-rc8

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/net/wireless/marvell-8xxx.txt?h=v5.19-rc8

 

missing interrupts and marvell,wakeup-pin,  

 

interrupt pins are GPIOX_7 for wifi, GPIOX_17 for bt.

 

this is infor from vendor OS:

 

gpio-241 (sdio_wifi ) in lo GPIOX_7

gpio-251 (bt_rfkill ) in lo   GPIOX_17 ( the name is bt_rfkill, but its direction is in, thus it is interrupt.

 

but wakeup-pin is device side pin to wakeup soc, this is unknown.

 

as said in bindings file, these are optional, wifi/bt are still work without them. but can't fill them with wrong data.

 

 

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

&sd_emmc_a {
        mwifiex@1 {
                compatible = "marvell,sd8897";
                reg = <1>;
        };

        btmrvl@2 {
                compatible = "marvell,sd8897-bt";
                reg = <2>;
        };
};

 

 

this is Wifi/Bt nodes I plan to add, and wifi/bt are work with these nodes. because other properties are optional.

 

 

 

 

 

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

On 7/27/2022 at 11:20 AM, chewitt said:

a) The sdio_pwrdeq node is in the wrong place in the dts, it should be in the initial indented section, see https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/amlogic/meson-gx-p23x-q20x.dtsi#L94-L99 - it is not a top-level node

 

I don't understand this part, could you explain it more? what is top-level node?

in my mind, if a node has phandle, I can modify it in any place.

if you can add a patch to your github, this will help a lot.

 

 

I already sent a email only to Sean ask how to handle RC keymap patch.

 

if this patch is already accepted, I will send new version without this patch.

new version will have 1 dts patch following 3 bindings patches, 2 with Acked-by.

 

I plan to:

add bt/wifi node to indicate bt wifi is ready, and comments about what missing in these nodes.

(from sd8897 bindings, missing interrupt pin in soc side, meson gpio doesn't support interrup mode, and wake-up pin in device side, no impact to main function)

add LED node quoted in "/* */" and comments to let others to know why LED is not enabled.

(from info from Neil, need more patch to enable GPIO_TEST_N)

in dts patch, not seprate patches.

 

do you agree?

 

I want to wait Sean's email for some days then new version.

 

 

[Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)]

errr... sorry, I don't understand. upstream patch is so painful. this is the second try. much better than 1st. my 1st try no body reply my patch, even later days I found same patch with different author in kernel.