Search by Tags

BSP Layers and Reference Images for Yocto Project Issue Tracker

 

The following table contains known issues, scheduled bug fixes, and feature improvements for the Toradex BSP Layers and Reference Images for Yocto Project.

The tickets are split into two major states:

  • Submitted (open): new features and bug fixes for BSP versions that have not yet been released. They may be scheduled for a specific release version; not planned; or in our backlog. All of them have one of the following states:
    • Known Issue: a bug or unexpected behavior that has been reported and is pending a fix. Once fixed, the status will transition to Fixed.
    • Feature Request: a new feature that may be added to a future release. Once released, the status will transition to New Feature.
  • Released (closed): new features and bug fixes for BSP versions that have already been released. All of them have one of the following states:
    • Fixed: a bug that has been fixed and released.
    • New Feature: something that didn't exist before and was added to a new release.


Any schedules are not guaranteed but reflect the current planning. The planning could be shifted due to priority changes.

Issues that are scheduled for a specific version will be integrated into the mentioned version of the BSP.

We will update this table continuously in order to always provide the latest state of our development plan. Please see also the Linux Support Strategy to learn more about the different releases.

View All Submitted (open) Released (closed)
Clear Filter
Issue #StatusSubjectModuleSubsystemWinCE OSSeveritySubmitted for Mainline

Not Planned
ELB-313Known IssueIncompatibility Between L4T Linux Kernel and iproute2-ss140804Colibri T20, Colibri T30, Apalis T30CANLowNo

Description: There exists an incompatibility of sorts between the older L4T Linux kernel version our Tegra BSPs are based on and the newer iproute2-ss140804 from our V2.4 BSPs leading to errors as follows:
root@apalis-t30:~# ip -details link show can0
RTNETLINK answers: Invalid argument
Cannot send link get request: Invalid argument

Workaround: Either downgrade to iproute2-ss131122 from our V2.3 BSPs or simply drop specifying a particular interface (e.g. use 'ip -details link show' instead).