1. 07 Apr, 2021 4 commits
  2. 15 Mar, 2021 4 commits
    • Jan Kiszka's avatar
      cobalt: Avoid reading time twice via xnstat_exectime_update · aacfaf8b
      Jan Kiszka authored
      
      
      This macro may unroll to instantiating 'date' twice. If that is a call
      to some get-time function, as via xnstat_exectime_switch, we needlessly
      do that twice.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      aacfaf8b
    • Jan Kiszka's avatar
      cobalt/posix/mqueue: Avoid returning internal EADV as error · 5f14ea8a
      Jan Kiszka authored
      In contrast to real RTDM devices, message queues have no fallback path
      to Linux in userspace. Thus, EADV is neither needed nor detected by
      libcobalt. Avoid leaking it from RTDM to the mq syscall interface.
      
      Fixes: 2db562ad
      
       ("cobalt: switch hand over status to -EADV for non-RTDM fd")
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      5f14ea8a
    • Jan Kiszka's avatar
      ci: Do not install unneeded crosstools · 1b89f045
      Jan Kiszka authored
      
      
      Make the package set arch-specific to save some bytes and seconds.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      1b89f045
    • Stephane Grosjean's avatar
      RT-socket-CAN: Add support of PEAK PCAN-PCIe FD cards family · 88d10a9d
      Stephane Grosjean authored and Jan Kiszka's avatar Jan Kiszka committed
      
      
      This patch includes the driver that supports the CANFD interfaces of
      the PCAN-PCIe FD family. This driver is largely inspired by the peak_pciefd
      driver included in the kernel since version 4.12. Except for the
      differences related to the RTDM model, this driver differs from the
      socket-CAN driver by the following points:
      
      . CAN 2.0 a/b support only (CAN-FD not available in rt-socket-can)
      . all interrupts are required (or released) when loading (or unloading)
        the module, not when activating (or deactivating) the CAN interface as in
        the socket-CAN model. Only hardware interruptions are enabled (or
        disabled) when the rtcan interface is set up (or down).
      . This way of operating allows the usage of the MSI mode: if CONFIG_PCI_MSI
        is defined while CONFIG_XENO_OPT_SHIRQ is not, then the driver activates
        the MSI mode by default. The legacy INTA mode is used otherwise. In case
        CONFIG_PCI_MSI is defined, the parameter module "usemsi" allows to change
        this default behaviour: usemsi=0 selects INTA mode while usemsi=1 selects
        MSI mode.
      . the Tx flow is managed more easily (no echo management in rt-socket-can)
      Signed-off-by: default avatarStephane Grosjean <s.grosjean@peak-system.com>
      Tested-by: default avatarAndy Tannenbaum <trb@bioniklabs.com>
      [Jan: added to CI]
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      88d10a9d
  3. 08 Mar, 2021 12 commits
  4. 06 Mar, 2021 1 commit
  5. 16 Feb, 2021 1 commit
  6. 15 Feb, 2021 1 commit
  7. 10 Feb, 2021 1 commit
  8. 08 Feb, 2021 10 commits
  9. 05 Feb, 2021 3 commits
  10. 03 Feb, 2021 3 commits