JMCC

Members
  • Content Count

    573
  • Joined

  • Last visited

2 Followers

About JMCC

  • Rank
    Embedded member

Recent Profile Visitors

3933 profile views
  1. Ir is just an information message. It tells you that the tool you can use for system configuration is "armbian-config", and it warms you that it is in beta stage, just so you are aware of it.
  2. Well, if that's the case, then we should probably first try to merge legacy too and "sort out the mali mess" as @chwe said above, and if we are not able to do it, then we can split. Regarding what I have been working on: I was preparing an extension for the build system, in order to build the multimedia packages that are on the media script. It was well advanced, but I stopped it since I am not so sure about the prospective for legacy kernels. The impression I get is that most members are willing to get rid of them and stick with Mainline. So I would like to hear some impressions about it, to see if it is worth integrating that into the build script or not.
  3. Well, once a board goes into a family, it shares legacy, current and dev with the others, doesn't it? I don't understand exactly what you mean.
  4. Not if we put all RK3399 boards in rk3399, and all RK3328 in rockchip64. In that case, we could just keep our current kernel config and that would work.
  5. You can try @balbes150's images: Or you can do like me, I just burn two SD cards and switch them at pleasure .
  6. If you want plain window managers with no other gadget or bar on the screen, there are quite a few of them: Openbox, Fluxbox or JWM are among the most popular. But they won't make a big difference with LXDE or Xfce in terms of usability in low-res, since in these you can just hide the panel/bar and you will have the full screen available too. What will really matter IMO is that you set low DPI, set a small font, and choose a compact widget theme (for GTK and Qt). And minimalistic window decorations, in case you use them (some window managers don't even use window decorations, see here: https://wiki.archlinux.org/index.php/window_manager ).
  7. Well, this Kodi is just an old beta version. It is not intended for real use, just as a demonstration that Rockchip's GBM and RKMPP are working in our kernels. If you want to use Kodi seriously, I recommend you try LibreElec.
  8. Kodi launcher is not working in recent Armbian. Just launch it from console: Ctrl+alt+F1 sudo service lightdm stop kodi-gbm-wrapper
  9. You can download the image, and follow the instructions under the header "How to start", in this page: https://www.armbian.com/orange-pi-3/
  10. Well, I don't want to point out something that went wrong, but on the contrary I want to emphasize all the things that went well. Having been disconnected from Armbian for some months, I can see a major improvement in the project's organization. Things like a predictable release cycle, tagged repo with all the releases, scheduling and coordinating, bug tracking... I can see a lot of work has been put into it, and IMO the results are excellent. So a big congrats to everyone who took part on it! Great job!
  11. As a side note, I figured out what was causing the problem with desktop acceleration in Buster. It is this security fix that they introduced in their Mesa 18.3.6 package. So we definitely discard Buster as a multimedia desktop, but Focal may still work, we'll see when it is released.
  12. Notice that in my Renegade was dong something very similar (corrupting fs as soon as it booted), and it turned out to be some problem with not enough current on the SD card reader. @TonyMac32 released a fix that solved it by increasing the current in the DT, but after some upgrades the problem reappeared. Strange enough, it worked with the same DT but Firefly's kernel. I guess it had to be some kernel config missing in our kernel, but I haven't checked it in a while.
  13. No, I mean for the future. When focal is released, still leave Bionic for rockchip legacy desktop as an available download in the main page. Only for legacy desktop, not current
  14. Here is an update about multimedia integration: I have been trying to make all the Rockchip-legacy stuff work on Buster, and I am not able to get accelerated X desktop. I cannot find the exact cause, apparently something is making eglInitailize() fail. My guess is it has something to do with mesa libs, but could not debug the exact cause. In Rockchip, they are working in a completely new approach, using exa instead of glamor acceleration. They need to use for that another particular feature of their SoC's, called Rockchip-rga, which in turn needs its special kernel driver and userspace libs (similar to their rk-mpp). So far, it does not seem to be working in the 'stable-4.4-rk3288-linux' branch we are using, and the stable-v2 branch does not compile ATM. I wasn't even able to make it work with their own linaro image. So my proposal is that we keep the download option of Bionic Legacy Desktop for all the rockchips, with the link to the media-script thread, for those who need to use some of the features that are still only available in legacy kernels. ( @Igor would it be possible to keep it for a while? Bionic still has three years of support ). With newer releases (Buster, Focal), we will focus on mainline, and hopefully at some point legacy won't be necessary at all.
  15. When you decompile a dtb file, you will normally not get the same dts that was used for compiling. It will be a dts that will work the same as the original, but it will not keep the ordering, spacing and indentation, and not even the same identical syntax as the original one. You should instead look for your dts in the kernel source tree. Look in /arch/arm(64)/boot/dts. For example, for Tinker Board in the Mainline kernel, it's this one: https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/rk3288-tinker.dts . Which, in turn, includes another source file, namely this one: https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/rk3288-tinker.dtsi