slarm64This forum is for the discussion of slarm64.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|----------- delimiter ----------- "added" "configuration file build-packages.conf" -----------|
|----------- delimiter ----------- "added" "configuration file rock_5.conf" -----------|
|----------- delimiter ----------- "added" "configuration file rk3588.conf" -----------|
|----------- delimiter ----------- "start" "build slarm64 ARCH aarch64 images: core" -----------|
|----------- delimiter ----------- "clear" "boot tools" -----------|
|----------- delimiter ----------- "compiling" "u-boot-tools-rockchip 2017.09" -----------|
|----------- delimiter ----------- "compiling" "arm-trusted-firmware master:tag:v2.9" -----------|
|----------- delimiter ----------- "compiling" "u-boot-rk3588 2017.09" -----------|
|----------- delimiter ----------- "compiler" "gcc 13.1.0" -----------|
CLEAN dts/../arch/arm/dts
CLEAN dts
CLEAN examples/standalone
CLEAN tools
CLEAN tools/lib tools/common
CLEAN spl/arch spl/board spl/cmd spl/common spl/disk spl/drivers spl/dts spl/env spl/fs spl/lib spl/u-boot-spl spl/u-boot-spl-dtb.bin spl/u-boot-spl-nodtb.bin spl/u-boot-spl.bin spl/u-boot-spl.dtb spl/u-boot-spl.lds spl/u-boot-spl.map spl/u-boot-spl.sym spl/u-boot.cfg tpl/arch tpl/board tpl/common tpl/disk tpl/drivers tpl/dts tpl/fs tpl/u-boot-spl.lds tpl/u-boot-tpl tpl/u-boot-tpl-nodtb.bin tpl/u-boot-tpl.bin tpl/u-boot-tpl.map tpl/u-boot-tpl.sym tpl/u-boot.cfg
CLEAN u-boot u-boot-dtb.bin u-boot-dtb.img u-boot-nodtb.bin u-boot.bin u-boot.cfg u-boot.cfg.configs u-boot.dtb u-boot.img u-boot.itb u-boot.its u-boot.lds u-boot.map u-boot.srec u-boot.sym System.map bl31_0x00040000.bin bl31_0x000f0000.bin bl31_0xff100000.bin u-boot-dtb.bin u-boot-nodtb.bin u-boot.bin idbloader.img u-boot-dtb.img u-boot.img
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/zconf.tab.o
[snip]
CC [M] drivers/media/usb/gspca/m5602/m5602_ov7660.o
In file included from ./include/linux/linkage.h:7,
from ./include/linux/kernel.h:17,
from ./include/linux/cpumask.h:10,
from ./include/linux/smp.h:13,
from ./include/linux/lockdep.h:14,
from ./include/linux/mutex.h:17,
from ./include/linux/kernfs.h:11,
from ./include/linux/sysfs.h:16,
from ./include/linux/kobject.h:20,
from ./include/linux/cdev.h:5,
from drivers/net/wireless/uwe5622/unisocwcn/platform/wcn_log.c:1:
drivers/net/wireless/uwe5622/unisocwcn/platform/wcn_log.c: In function ‘log_cdev_init’:
./include/linux/export.h:29:21: error: passing argument 1 of ‘class_create’ from incompatible pointer type [-Werror=incompatible-pointer-types]
29 | #define THIS_MODULE ((struct module *)0)
| ^~~~~~~~~~~~~~~~~~~~
| |
| struct module *
drivers/net/wireless/uwe5622/unisocwcn/platform/wcn_log.c:263:37: note: in expansion of macro ‘THIS_MODULE’
263 | wcnlog_class = class_create(THIS_MODULE, "slog_wcn");
| ^~~~~~~~~~~
In file included from ./include/linux/device.h:31,
from ./include/linux/cdev.h:8:
./include/linux/device/class.h:230:54: note: expected ‘const char *’ but argument is of type ‘struct module *’
230 | struct class * __must_check class_create(const char *name);
| ~~~~~~~~~~~~^~~~
drivers/net/wireless/uwe5622/unisocwcn/platform/wcn_log.c:263:24: error: too many arguments to function ‘class_create’
263 | wcnlog_class = class_create(THIS_MODULE, "slog_wcn");
| ^~~~~~~~~~~~
./include/linux/device/class.h:230:29: note: declared here
230 | struct class * __must_check class_create(const char *name);
| ^~~~~~~~~~~~
cc1: some warnings being treated as errors
make[6]: *** [scripts/Makefile.build:252: drivers/net/wireless/uwe5622/unisocwcn/platform/wcn_log.o] Error 1
make[5]: *** [scripts/Makefile.build:494: drivers/net/wireless/uwe5622/unisocwcn] Error 2
make[4]: *** [scripts/Makefile.build:494: drivers/net/wireless/uwe5622] Error 2
make[4]: *** Waiting for unfinished jobs....
[snip]
LD [M] drivers/net/wireless/rtl8192eu/8192eu.o
make[3]: *** [scripts/Makefile.build:494: drivers/net/wireless] Error 2
make[2]: *** [scripts/Makefile.build:494: drivers/net] Error 2
make[2]: *** Waiting for unfinished jobs....
[snip]
And lots of warnings like:
Code:
CC [M] drivers/net/wireless/realtek/rtlwifi/rtl8723be/led.o
drivers/net/wireless/rtl8189fs/core/rtw_ap.c: In function ‘rtw_ap_update_chbw_by_ifbmp’:
drivers/net/wireless/rtl8189fs/core/rtw_ap.c:4385:42: warning: the comparison will always evaluate as ‘true’ for the address of ‘padapters’ will never be NULL [-Waddress]
4385 | if (!(ifbmp & BIT(i)) || !dvobj->padapters)
| ^
and
Code:
LD [M] drivers/staging/vt6656/vt6656_stage.o
drivers/net/wireless/rtl8192eu/hal/hal_hci/hal_usb.c: In function ‘usb_init_recv_priv’:
drivers/net/wireless/rtl8192eu/hal/hal_hci/hal_usb.c:28:22: warning: cast between incompatible function types from ‘void (*)(void *)’ to ‘void (*)(long unsigned int)’ [-Wcast-function-type]
28 | (void(*)(unsigned long))usb_recv_tasklet,
| ^
and
Code:
drivers/net/wireless/rtl8189fs/hal/phydm/phydm_api.c: In function ‘phydm_nbi_debug’:
drivers/net/wireless/rtl8189fs/hal/phydm/phydm_api.c:1656:21: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘input + (sizetype)((long unsigned int)((int)i + 1) * 16)’ must not be NULL [-Waddress]
1656 | if (input[i + 1]) {
| ^~~~~
ocurring in several places.
the buildlog is bigger than 512k...
CC [M] drivers/net/wireless/realtek/rtlwifi/rtl8723be/led.o
drivers/net/wireless/rtl8189fs/core/rtw_ap.c: In function ‘rtw_ap_update_chbw_by_ifbmp’:
drivers/net/wireless/rtl8189fs/core/rtw_ap.c:4385:42: warning: the comparison will always evaluate as ‘true’ for the address of ‘padapters’ will never be NULL [-Waddress]
4385 | if (!(ifbmp & BIT(i)) || !dvobj->padapters)
| ^
and
Code:
LD [M] drivers/staging/vt6656/vt6656_stage.o
drivers/net/wireless/rtl8192eu/hal/hal_hci/hal_usb.c: In function ‘usb_init_recv_priv’:
drivers/net/wireless/rtl8192eu/hal/hal_hci/hal_usb.c:28:22: warning: cast between incompatible function types from ‘void (*)(void *)’ to ‘void (*)(long unsigned int)’ [-Wcast-function-type]
28 | (void(*)(unsigned long))usb_recv_tasklet,
| ^
and
Code:
drivers/net/wireless/rtl8189fs/hal/phydm/phydm_api.c: In function ‘phydm_nbi_debug’:
drivers/net/wireless/rtl8189fs/hal/phydm/phydm_api.c:1656:21: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘input + (sizetype)((long unsigned int)((int)i + 1) * 16)’ must not be NULL [-Waddress]
1656 | if (input[i + 1]) {
| ^~~~~
ocurring in several places.
the buildlog is bigger than 512k...
I'm considering one of these. What's GPU support like? Are there decent Mesa Drivers?
Last time i asked sndwvs he had no working hardware so most of the images were untested.
I have the hardware - and it is fast, office PC kind of fast, not just Android fast.
The only kernel i could make work was the 5.10.110 one patched with OEM patches.
Most of the packaged kernels here are not tested, the 3588S are, but the 3588 seem not to be, i tested few and they failed to run or build or both.
I have my device run that initially working kernel ripped from the 3588S image and an Slackware-aarch64-current system working on my device.
I am yet to go about compiling and installing a mainstream kernel on the device yet - the 6.5.6 made it thru with building (without any patches), but i can't get around to sit down and make it boot too.
Thanks very much for the reply. I feel cured from considering that particular SBC!
I take it the OEM doesn't provide a kernel source, or patches?
Is the Orange Pi any better, do you know?
Either way, you've given me a new 'gotchya' to watch out for.
EDIT: Just comparing the Orange Pi and the Rock Pi, the Orange Pi seems to have better software support. They even have Arch.
Oh, the OEM goes out of their way, but only for particular distributions, i think Armbian was included but i haven't looked in a while.
The Orange Pi, while admittedly having got more traction with the (weaker) Orange 5 (3588S) is not as attractive to me as either:
Friendly Elec Nano PC T6 (fully spec 3588 + proper metal case)
Orange Pi 5 plus (full spec 3588)
Both are on par with this Rock 5, but both have normal sized HDMI for both outputs and one input (rock has one on USB type-C OTG jack, good luck populating that), but the Nano PC T6 leads with how cheap the CNC case is plus it uses the common 5.5 mm barrel jack - KISS applies (and wins hands down) here.
Orange Pi got some lead with greater user base in the more vocal part of the linux community - but in the long run it might prove Friendly Elec is the winner -a properly done metal case will take you further than half-arssed distribution image let in neglect after the stellar release - Orange Pi's custom so far i could tell...
Did I mention the Banana Pi's alluring M2S model yet?
On top of that Friendly Elec seem to have an OEM run web store quite competitive to Aliexpress' pricing and shipping.
Thanks for laying things out so clearly. I have no local suppliers for Orange or Rock. But the fact that sndwvs has Orange Pi 5s running points me there, if the Rock Pi 5 images are untested. What are the graphics like? I can see CONFIG_MALI_DRM_DISPLAY in the kernel, but can't spot much in Mesa.
After my RazPi 4 experience, I wanted a decent non-proprietary graphics setup before I'd even consider a purchase. I'll wait for a decent driver source code before considering the Pi 5. I'd also want to hear back very good things on computing power or compile times. As an ex-hardware guy, I know internal tweaks can do a lot of unseen good only if the first design was terrible.
The RK3588 boards are priced close to €200. For a bit more, I'm into the bottom end x86_64 stuff. The spec I wanted was the RK3588+ board in a metal case with a bootable nvme and no fan. In Europe, CE requirements mean that any metal is grounded, so the metal case acts as a Faraday shield on internal wifi aerials. I'm trusting the sdcard has boot priority? Otherwise, if the M2 goes.....
EDIT: I'll check out the Banana M2S & Friendly Elec too.
Last edited by business_kid; 10-22-2023 at 05:43 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. I'm trusting the sdcard has boot priority? Otherwise, if the M2 goes.....
