BSPs/FRI2

From Yocto Project
Jump to: navigation, search

Contents


Resources

Latest FRI2 README

Tips

Use this space to share tips about using the FRI2. If you didn't find it in the README and it took you longer than 5 minutes to figure it out, consider placing it here and we can work it into the README as appropriate.

Unable to view HDMI output on your monitor

Some HDMI monitors do not appear to work with the HDMI output from the FRI2. Which displays work and which do not can be unpredictable; it may even be the case that individual monitors of the same make and model may work while others may not.

As a workaround you can connect the FRI2 to the DVI connection on your monitor using an HDMI to DVI adapter.

Obtaining the ti_3410.fw file needed by ti_usb_3410_5052

Debian (and perhaps other Linux distros) do not package ti_3410.fw (no, not even in lfirmware-linux-nonfree). The following bash script will use git to obtain just the one file from kernel.org and move it to where "modprobe ti_usb_3410_5052" will find it:

  #!/bin/bash
  sudo apt-get install git
  git clone -n git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git --depth 1
  cd linux-firmware
  git checkout HEAD ti_3410.fw
  sudo cp -p ti_3410.fw /lib/firmware

The script is tested on Debian with 3.1.0 kernel and will need to be modified if your system uses RPM and/or does not follow the standard filesystem hierarchy.

Note that Ubuntu and Fedora both package it with the linux-firmware package and Ubuntu also includes it in the various linux-image packages.

Known Issues

Warning at arch/x86/kernel/apic/ipi.c

WARNING: at [...] linux-yocto-3.2.18+git1+5b4c9dc78b5ae607173cc3ddab9bce1b5f78129b_1+76dc683eccc46804729a76b9d2fd425ba540a483-r1/linux/arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0xa4/0xe0()
Hardware name: Fish River Island II
empty IPI mask
Modules linked in:
Pid: 1, comm: swapper/0 Not tainted 3.2.18-yocto-standard #1
Call Trace:
 [<c103b8d3>] warn_slowpath_common+0x73/0xa0
 [<c1018234>] ? default_send_IPI_mask_logical+0xa4/0xe0
 ...

This appears to be a known issue with how IPIs are handled within the generic SMP infrastructure. A fix is being discussed on LKML, but the warning appears to be benign.

Personal tools