davo22 indeed blasphemy is possible Gumstix Introduces CM4 to CM3 Adapter, Carrier Boards for Raspberry Pi Compute Module 4 .. but add $30 to the cost of the CM4 module and things are starting to get expensive, and you're still misssing proper Ethernet and other things that IMHO make an RPi4 more long-term attractive. Slice also needs drivers/hardware support that means it's not quite the simple swap that you'd want.
Posts by chewitt
-
-
CM4 was just announced Raspberry Pi CM4 and CM4Lite Modules Launched for $25 and Up but as I previously hinted the module uses a new form factor so is not compatible with the CM/CM3 using Slice box.
-
arm64: dts: meson: add support for the WeTek Core 2
Thank you for the people who own this device.
Core2 is an S912 device that was never released so I'm fairly confident I'm the only person who owns one
I use it for Panfrost sanity testing on GXM when I get bored of using a VIM2.
-
The LE device should be able to join a WiFi hotspot shared from the phone although from personal experience phones frequently drop the tether to save battery which results in the LE device losing network access. More advanced Bluetooth tethering is not supported. The 'tethering' capability in the OS is the reverse, where the LE device shares its Ethernet connection via a local WiFi hotspot that other devices can join.
-
There are no current plans for more LE 9.2 releases but the firmware should be in LE10 by default: linux-firmware: pick mrvl/sd8897_uapsta.bin for Generic by chewitt · Pull Request #4587 · LibreELEC/LibreELEC.tv · GitHub
-
Not much changed while you were out. The driver is loaded but firmware is still missing .. you can redo the commands in post #2:
Codemkdir -p /storage/.config/firmware/mrvl wget -O https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mrvl/sd8897_uapsta.bin /storage/.config/firmware/mrvl/sd8897_uapsta.bin reboot
If you're lucky someone might send the changes needed to GitHub..
-
Kodi needs to know how to open ffmpeg calling the correct hardware decoder (nvdec, not vdpau) and for things like DRMPRIME to work it also needs to understand an entirely different buffer management process (EGL Streams) not GBM, the standard the Linux kernel adopted. None of them are a huge leap, but "no more proprietary crap" is one of the few things the members of Team Kodi agree upon so if it happens it will almost certainly be a surprise drive-by conttribution from someone new not an existting team member.
-
-
No major changes. Amlogic is now one of the best supported core codebases for ARM devices thanks to u-boot work done by Baylibre and efforts from LibreComputer to get their products accepted into the major distros. The multimedia capabilities are still languishing in the dark ages.
-
I've been tracking that branch for changes, but the patches are posted and then merged so fast (7h in that case) that I didn't see them. I'd expect them to appear in Linux 5.9. You can also try backporting them to 5.7.
-
You should not expect to use device-tree files from 5.7 on 5.1, and I'm not sure what advantage you could perceive in doing that.
-
LE10/K19 first alpha will be soon and likely uses Linux 5.7 .. but this an alpha and since final release is likely months away some higher kernel version will probably be used in final releases, we'll keep bumping during alpha and won't lock things down until beta. There is no point in including the patches flagged above, all they do is establish the current driver is for the A variant and add firmware for the B variant. Until there is also driver code for the B variant there's "nothing to see here, move along please" and adding the realtek vendor driver could be done in a private build, but it won't be done for a public release as we'd need to disable the in-kernel driver globally which will affect other users with A variant hardware.
Keep an eye on Linux network development - Patchwork and once you see patches posted, there's something to test.
-
unfortunately with this image device is not booting, always constant lighting red and blue LEDs. It doesn't matter if I try to start from SD card or USB pendrive. It worth mention that I installed balbes150 SPI boot 20191003/spiboot.img. Should I use different one SPI?
I have an N2 (and N2+) with the latest petitboot spi image that HK published and all I do is write the SD card (or eMMC module) and ensure the boot switch is to the right, and it boots into LE without issues. I can't say I've ever tried USB, but mainline u-boot should support that too.
-
e123enitan1 SSH in and run "dmesg | paste" and share the URL while connected to ethernet, and then run ^ those commands and see if you can connect WiFi from the console.
-
extremeaudio what happens if you force ethernet to 100-BaseT speeds?
fri.K i've not seen issues with N2 in testing but see if LibreELEC-AMLG12.arm-9.80.0-odroid-n2.img.gz works better, this is using updated boot firmware (revised to support N2+) .. write image to SD card or eMMC and put the boot switch to the right - it will not boot with petitboot (switch to the left).
-
Code
[ 8.232771] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 8.232799] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
Can you repeat the Q201 test with LibreELEC-AMLGX.arm-9.80.0-box.img.gz
Also check the Q200 device-tree, and see if any other GXM dtb files get further (VIM2, etc.). The same AP trick should work if no Ethernet.
-
Test installations are $free
-
The core OS is in awesome and super-reliable shape since we moved to mainline u-boot and modern kernels. Unfortunately the one thing we need to work well (hardware decoding) is in pissy shape .. and until there's a eureka moment on seeking/flushing support with GBM/V4L2 images aren't so usable. Raspberry Pi (also using stateful decoding) is now stuck at the same point so I'm hoping their considerably larger gene-pool of talent (Amlogic's is woefully small) will figure out something and then we'll be in better shape.