1. 16 Nov, 2018 10 commits
  2. 06 Nov, 2018 3 commits
  3. 05 Nov, 2018 1 commit
  4. 31 Oct, 2018 2 commits
  5. 28 Oct, 2018 9 commits
  6. 17 Oct, 2018 3 commits
    • Sebastian Smolorz's avatar
      rtdm: expose user-side file descriptors to drivers · 04df9389
      Sebastian Smolorz authored and Jan Kiszka's avatar Jan Kiszka committed
      
      
      RTDM drivers refer to open files or sockets by using struct rtdm_fd.
      Normally, the user-side file descriptors returned by socket() or open()
      calls are not necessary for driver operations. However, in some special
      cases the user-side fd has to be determined, for example as return
      value of rt_tcp_accept() which is a driver function of RTnet's TCP
      protocol driver.
      Signed-off-by: default avatarSebastian Smolorz <sebastian.smolorz@gmx.de>
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      04df9389
    • Philippe Gerum's avatar
      boilerplate/setup: cobalt: do not advertise non-RT CPUs to applications · bed7acf3
      Philippe Gerum authored and Jan Kiszka's avatar Jan Kiszka committed
      
      
      The CPU affinity mask in __base_setup_data.cpu_affinity - which may be
      set by --cpu-affinity - is conventionally checked by applications for
      determining which CPUs are usable for real-time duties.
      
      Over Cobalt, we need to make sure that such mask reflects the set of
      CPUs available for running real-time threads as defined by the core
      (i.e. /proc/xenomai/affinity), in absence of --cpu-affinity
      setting.
      
      Otherwise, some applications like switchest looking at an empty
      affinity mask may wrongly assume that all CPUs are available for
      running RT threads, leading to a failure when manually pinning such
      thread to an invalid (non-RT) CPU.
      
      With current Cobalt core and I-pipe releases not fixed for gracefully
      handling invalid domain migration requests over a non-RT CPU, such a
      failure may trigger a kernel panic.
      Signed-off-by: Philippe Gerum's avatarPhilippe Gerum <rpm@xenomai.org>
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      bed7acf3
    • Jan Kiszka's avatar
      build: Modernize device installation · e3eefdf4
      Jan Kiszka authored
      
      
      Drop the obsoleted mknod calls - all modern systems use devtmpfs, and
      that creates the rtp nodes for us.
      
      Furthermore, switch the remaining installation of udev rules to proper
      automake, using sysconfdir, INSTALL_DATA etc., dropping sudo from those
      steps (installation into privileged folders implies "sudo make install"
      or running as root in the first place).
      
      Finally, only differentiate between pre-existing udev.rules and default
      installation into rules.d.
      
      This removes the need for the install-user target - drop it.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      e3eefdf4
  7. 10 Oct, 2018 2 commits
  8. 02 Oct, 2018 4 commits
  9. 27 Sep, 2018 1 commit
  10. 24 Sep, 2018 3 commits
    • Philippe Gerum's avatar
      cobalt: use generic linux/uaccess.h header · bae753be
      Philippe Gerum authored and Jan Kiszka's avatar Jan Kiszka committed
      
      
      asm/uaccess.h is an arch-local, partial header which may cause build
      issues if included directly.
      Signed-off-by: Philippe Gerum's avatarPhilippe Gerum <rpm@xenomai.org>
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      bae753be
    • Marek Vasut's avatar
      cobalt/arm64: prepare-kernel: Map aarch64 to arm64 · 6171f857
      Marek Vasut authored and Jan Kiszka's avatar Jan Kiszka committed
      
      
      Various build systems and also the kernel uses aarch64 to refer to
      arm64, map aarch64 and arm64 to the same thing.
      Signed-off-by: Marek Vasut's avatarMarek Vasut <marex@denx.de>
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      6171f857
    • Philippe Gerum's avatar
      drivers/can: flexcan: rebase on mainline v4.14.58 · c6f278d6
      Philippe Gerum authored and Jan Kiszka's avatar Jan Kiszka committed
      
      
      Usable with latest Flexcan controller revisions available from recent
      i.MX series. The older driver would break when initializing the chip
      (FIFO activation), e.g.:
      
      [  957.052272] rtcan0: real bitrate 1000000, sampling point 75.0%
      [  957.058325] rtcan0: writing ctrl=0x011a2003
      [  957.062670] rtcan0: flexcan_set_bit_time: mcr=0x5980000f ctrl=0x011a2003
      [  957.069403] rtcan0: flexcan_chip_start: writing mcr=0x79a2020f
      [  957.069421] rtcan0: flexcan_chip_start: writing ctrl=0x011aac53
      [  957.075359] Unhandled fault: imprecise external abort (0x1c06) at 0xaec71a2c
      [  957.088371] pgd = cae8c000
      [  957.091106] [aec71a2c] *pgd=9d843835, *pte=ba49d75f, *ppte=ba49dc7f
      [  957.097447] Internal error: : 1c06 [#1] SMP ARM
      [  957.108324] CPU: 1 PID: 843 Comm: rtcanconfig Not tainted 4.14.34 #1
      [  957.115391] Hardware name: Freescale i.MX7 Dual (Device Tree)
      [  957.121155] I-pipe domain: Linux
      [  957.124404] task: caee1900 task.stack: ca5d0000
      [  957.128968] PC is at flexcan_chip_start+0x180/0x34c
      [  957.133869] LR is at flexcan_chip_start+0x178/0x34c
      
      As a bonus, the latest work arounds addressing silicon bugs are now
      included (e.g. use of timestamp-based offloading when the FIFO
      ordering does not match the time of arrival).
      Signed-off-by: Philippe Gerum's avatarPhilippe Gerum <rpm@xenomai.org>
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      c6f278d6
  11. 17 Sep, 2018 2 commits