ning

these are dram initial logs.

/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?

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

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/

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只不能了。 不懂可以私信我。

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

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

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.

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.

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?

for 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>; }; };

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.

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

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.

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.

&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.

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.

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.

it's full chinese name is "天猫魔盒 M16S” 天猫 is Tmall, 魔盒 is magicbox. Alibaba is manufactor, tmall magicbox is product line name, m16s product name. if follow manufactor,product-line_product-name this will be too long in this case. so I choose a short one.

already do it in v5: http://lists.infradead.org/pipermail/linux-amlogic/2022-July/013067.html

you can check 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 , what you write follows bcm bluetooth. that's wrong. and wifi/bt DT items for its drivers are supplementary data, not for of_porbe, not such data, driver still work, but if you give wrong data, driver will not work.

@chewitt your dts is wrong. LED gpio is GPIO_TEST_N, not GPIOAO_9, there is no adc key, need to set sdio_pwrseq reset pin, otherwise wifi lose after reboot. and bluetooth may not work with your dts. my dts is finished. I initial 2 patches are not finished, due to this devices is black box to everyone. and it's finished in v3.

Hw Spec Soc: Amlogic S912-H, (S192 with dolby, DTS) Mem: 2G Ddr3 Emmc: 16G 4K HDMi AV out ethernet ?? Wifi/Bt ?? USB port *1 5V DC-IN IR receiver Reset hole OS: Ali YunOS Steps 1, connect UART from mainboard test points, (I can only find M17's UART port) 2, build u-boot follow q200.rst in u-boot doc, use VIM2 config and use VIM2 fip blobs (hope that works) 3, build Arm64 debian bookworm with default debian kernel to USB driver, and config system. 4, falsh u-boot to USB driver 5, connect to device with UART, hope to stop at u-boot cmdline, and erase emmc. if failed, find other way to erase, maybe Amlogic flash tool. 6, instert USB driver, and reboot device potaintial issues: can't find UART port on mainboard VIM2 mainline Uboot can't boot M16S device does not support boot from USB. No schematics for next step dev.

recent days I find Chromebook may be better Arm devices with laptop form factor. compare with Pinebook pro, Chromebooks are cheaper, and mass product, and better tested. why no much people discuss how to install 3rd OS to its internal emmc, or reflash its uboot? I have searched on ArchArm forum, only 1 topic. but there actually a way to reflash uboot, and mainline uboot already has support for arm based chromebooks. It should be easy, but why no discussion?