Advanced Search

royka wrote:

The SPI driver has nothing to do with Armbian, it's in the kernel, it seems to be a known issue with the default (example) driver. Unless their is a proper SPI driver for the rk3399 it won't be different on that sbc. AFAIK there's only made a realtime driver for the RPI.
Unfortunately I don't have a spi board to test with, perhaps it helps to pin the irq of spi to an isolated core?

I've seen that there has been a rt patch for one board for a quite old kernel, I can try to find that one and if I'm able to apply that on the newer kernel.
 

Is there really a real-time kernel version for the rk3399, like the one for Raspberry Pi? Because I haven't been able to find anything about it.Also, if you manage to find something useful with the older kernel, I’d really appreciate it if you could let me know. Thanks

Just tested on master and it seems it fails to show the correct 'current_line = 5' during the first run right after starting the config. After that it works for me.
Not sure why it fails the first time though other than that ''current_line" does not seem to update before an actual move of axis has taken place.

[edit]
The other thing that seems like a bug is that 'mcodes' always contains 'M0'.

 

Open a terminal (Ctrl+Alt+t) and enter this command
then choose your config and check for errors in the terminal output.

In /etc/default/grub:

GRUB_DISABLE_SUBMENU=true

You will need to modify the file with superuser permissions, but if you're new to Linux, using vim or nano might be too tedious. You can use something like:
or:and then launch the graphical editor as a superuser like so:or:I'm not on Debian right now, so if gksudo doesn't work, try gksu, and if that doesn't work, then resort to using `sudo` instead. Common practice is to never use `sudo` though for graphical applications.  After modifying /etc/default/grub (there should be a comment already in the file about GRUB_DISABLE_SUBMENU) run:Now count the number of menuentries starting from 0, then make that your `set default=` setting. Afterward, re-run:command again.