Damned that makes things more complicated :) That could push us along the following lines ? CONSOLE_DEVICES = "/dev/ttyS2 /dev/tty1" CONSOLE_BAUD_ttyS2 = "1500000" CONSOLE_BAUD_tty1 = "115200" (well,

----- Mail original ----- What about making this change at the poky level, then ?

From: Yann Dirson <yann@...> This is a RK3328 board from Pine64. Board details at https://wiki.pine64.org/wiki/ROCK64. Default image is built to boot from SD-card. Building an image for eM

In fact we already have rock-pi-e.wks doing this. Let's do the minimum for now for this to get merged, and we'll improve incrementally. Eg. only now I realize, through the presence of rk3328-boot.wks,

Oh, right, copypaste rules around here, so Garmin does have a role but something may be missing :) Right that was something I wondered how to deal with and forgot (and note that for the nanopi-m4 I us

From: Yann Dirson <yann@...> This is a RK3328 board from Pine64. Board details at https://wiki.pine64.org/wiki/ROCK64. Default image is built to boot from SD-card. Building an image for eM

<yann.dirson=blade-group.com@...> a écrit : This statement was refering to core-image-minimal. The board does get working ethernet, usb, hdmi with core-image-base, the only major de

From: Yann Dirson <yann@...> This is a RK3328 board from Pine64. Board details at https://wiki.pine64.org/wiki/ROCK64. Signed-off-by: Yann Dirson <yann@...> --- This is just ba

From: Yann Dirson <yann@...> Take the firmware from rbwifibt, as a compatible one does not seem to be available in broadcom-bt-firmware. Disclaimer: I have only been able to scan/pair with

From: Yann Dirson <yann@...> As far as the AP6356S in NanoPi-m4 is concerned, the included wifi firmwa= re is for Rockchip's kernel tree, but for Bluetooth firmware this seems to b= e the

From: Yann Dirson <yann@...> --- conf/machine/include/nanopi-m4.inc | 5 ++++- recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg | 5 +++++ 2 files changed, 9 insertions(+), 1 deletion(-

From: Yann Dirson <yann@...> This is required for wifi support on nanopi-m4 with kernel 5.10. This is dependant on poky commit commit 698fd81c551b52ff7f4a26e42d9acf9ad= 4ce5639, "linux-fir

From: Yann Dirson <yann@...> This patch provides "standard" and "tiny" BSP. There is still much work to be done in dispatching feature to individual scc files - the more boards we can supp

From: Yann Dirson <yann@...> There is a known issue in mainline kernel making the machine unusable once a HDMI screen is plugged. This patch lets VOPB be alone to use the HDMI port and avo

From: Yann Dirson <yann@...> With this version the most board features work (Wifi requires recent poky master for a linux-firmware fix), except for the audio jack and possibly Bluetooth su

<Diego.SantaCruz@...> a écrit : That does look nicer that way, much closer to what I intended, thanks! Best regards,

That pretty much clarifies the whole thing, thanks for taking the time for this!

Thanks for those clarifications! Some additional questions below I'd think (and I take your further remarks about workflow as confirming this), that when upgrading the kernel the best tool would be gi

I am currently working on a kmeta BSP for the rockchip-based NanoPI M4 [1], and I'm wondering how I should be providing kernel patches, as just add ing "patch" directives in the .scc does not get them

From: Yann Dirson <yann@...> Take the firmware from rbwifibt, as a compatible one does not seem to be available in broadcom-bt-firmware. Disclaimer: I have only been able to scan/pair with