arre

  • Content Count

    5
  • Joined

  • Last visited

About arre

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. There is a difference between PREEMPT and PREEMPT RT. So no, the real time patch was not enabled on your kernel
  2. @andreluiz109 : I did a small patch to the build system, to force it to not take the latest linux kernel, but a specific one. Perhaps there was an option in the armbian build system to specify this but I did not immediately find it. The reason why this is important, is that the linux RT patches are only applicable to a very specific kernel version. (e:g: the 4.18.8-RT 9 patch MUST be applied to the linux kernel 4.18.8 tag). That's why I did the following patch to the armbian build system (armbian build-system tag 9531d1bc7ecd0f468e29e402ba00cbc7b7dd683f) : di
  3. Hi all, Just wanted to share that I got the realtime patch working on an Orange Pi Zero on 4.18.8 I used the armbian build environment and the official RT patch. A few tricky points were the CPU govenor and CPU operating points automatically switching by default, causing the realtime behavior to be really bad (max spikes around 3000 in cpu test). By patching the device tree to only use a fixed operating point, I achieve the following output: Linux orangepizero 4.14.8-rt9-sunxi #1 SMP PREEMPT RT Sat Jan 6 14:36:31 CET 2018 armv7l armv7l armv7l GNU/Linux /ro
  4. Hi all, Just wanted to share that I got the realtime patch working on an Orange Pi Zero on 4.18.8 I used the armbian build environment and the official RT patch. A few tricky points were the CPU govenor and CPU operating points automatically switching by default, causing the realtime behavior to be really bad (max spikes around 3000 in cpu test). By patching the device tree to only use a fixed operating point, I achieve the following output: Linux orangepizero 4.14.8-rt9-sunxi #1 SMP PREEMPT RT Sat Jan 6 14:36:31 CET 2018 armv7l armv7l armv7l GNU/Linux /ro