Jump to content

zador.blood.stained

Members
 View Profile  See their activity

  • Posts

    3633

  • Joined

  • Last visited

 Content Type 

Everything posted by zador.blood.stained

  1. zador.blood.stained
    If we are talking about connecting IR receiver to any GPIO (and not using a dedicated GPIO pin and an in-SoC CIR decoding HW) then it should be enough to use this which requires the appropriate kernel drivers, RC keymaps and DT modifications (since we don't have overlays support there yet).
  2. zador.blood.stained
    It tries to boot with the legacy kernel configuration (/boot/.next is missing) ... but you are using the mainline kernel
  3. zador.blood.stained
    You can adjust this manually in the build script if you need to pull a specific kernel version. Yes, the question is who needs it and thus who is going to solve it. And you should be able to build such images if you put enough work into this, but you should always keep in mind the limitations of the mainline kernel on H3/H5 based Orange Pi boards.
  4. zador.blood.stained
    No, but you can keep an eye on this and decide for yourself when H5 and especially A64 get enough features supported upstream to be considered "stable" for your needs.
  5. zador.blood.stained
    There were some patches to this kernel to support newer eMMC revisions (or rather to not crash if an incompatible revision is found), so the kernel and uInitrd for fel-mass-storage has to be rebuilt if anyone wants to fix this.
  6. zador.blood.stained
    There is no such config in our current build script: https://github.com/armbian/build/tree/master/config/boards Exactly
  7. zador.blood.stained
    Looking at gitlab performance it may be easier to host a simple Git server ourselves, though issues and PRs would become a problem. Regarding performance BitBucket may be a better alternative. But in any case it's too early to look at this, GitHub still works fine for us.
  8. zador.blood.stained
    I96 is not supported by Armbian and was never tested by us (for any purposes - performance, consumprion, bugs, ...). For Zero you could probably find some numbers, they won't be much lower compared to Lite.
  9. zador.blood.stained
    It could be tested by tools like stress or cpuburn, though I'm not sure what kind of cpuburn should be used on A15 cores.
  10. zador.blood.stained
    +120°C in a couple of ms? Highly unlikely, and your syslog for some reason always contains 228°C for thermal_zone0 and 234°C for thermal_zone1, while, for example, the mainline kernel defines the critical temp at 115°C.
  11. zador.blood.stained
    Backwards compatibility with Xenial environment was broken by mistake, will fix it ASAP.
  12. zador.blood.stained
    Do we really need it? AF_ALG is present in new kernels, works with newer openssl versions out of the box and gives +/- the same if not better performance compared to cryptodev AFAIK.
  13. zador.blood.stained
    We don't control the kernel repository, but it is 3.10 (no upstream patches anymore) and the last commit here was at 13 Oct 2016, so IMO it's pretty safe to say that this source is not maintained.
  14. zador.blood.stained
    S500 devices (LeMaker Guitar and RoseApple Pi) are the only devices without initrd/UUID support, both are EOS and have only 3.10.y EOL kernel source. I propose creating a tag in the build script and deleting their configuration files along with the code that deals with non-UUID root cases to simplify our code base for upcoming LUKS rootfs encryption support. Any thoughts/objections?
  15. zador.blood.stained
    You could add a check for the kernel version in your eMMC installation script, i.e. like this (requires the "linux-base" package installed) if linux-version compare $(uname -r) gt 4.0 ; then echo "Installation to internal storage is not supported on this kernel version" exit 1 fi or you could check if /dev/data exists if this path is common for all TV boxes.
  16. zador.blood.stained
    Just so you don't waste your time, this kernel version does not support composite video output anyway.
  17. zador.blood.stained
    So if you do have an oscilloscope, can you capture the signal from UART TX (from the board side) and calculate its baud rate? (reference, just in case). But they may need a special condition (i.e. a specific resistance between the USB data lines) to activate the high current limit mode.
  18. zador.blood.stained
    Still there is no encoding out of the box, though there was a patched FFmpeg version with experimental encoding support.
  19. zador.blood.stained
    AFAIK the xf86-video-armsoc driver is generic and can support multiple platforms (i.e. there was a patch to add sunxi DRM+Mali support to it).
  20. zador.blood.stained
    Are we talking about A20 or H3?
  21. zador.blood.stained
    but still nobody patched the legacy driver for CSI_EN/CSI_PWR_EN pins support, so we have 2 kernel options - 1 partially broken and 1 not developed yet.
  22. zador.blood.stained
    Everything is correct. There is no w1-sunxi module on mainline, w1-gpio is used with Device Tree overlays instead of it.
  23. zador.blood.stained
    There is no CSI support in mainline, it doesn't matter which CSI camera driver will you try to use.
  24. zador.blood.stained
    In theory - yes. It should be enough to simply write an Armbian image directly to the HDD. On practice it is impossible to diagnose booting issues in any other possible scenario without a UART console. This is for native SATA, OPi Zero has only USB SATA via the NAS expansion board or any other USB-SATA adapter.
  25. zador.blood.stained
    This was killed in u-boot v2017.11 but the boot script wasn't updated yet, though it is mostly irrelevant here.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept