BSPs/FRI2 - Revision history

Sgarman at 17:33, 12 February 2013

2013-02-12T17:33:12Z

← Older revision		Revision as of 17:33, 12 February 2013
Line 6:		Line 6:
	== Tips ==		== 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.		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 ===		=== Obtaining the ti_3410.fw file needed by ti_usb_3410_5052 ===

Dvhart: /* Obtaining the ti_3410.fw file needed by ti_usb_3410_5052 */

2013-01-05T00:42:11Z

Obtaining the ti_3410.fw file needed by ti_usb_3410_5052

← Older revision		Revision as of 00:42, 5 January 2013
Line 18:		Line 18:

	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.		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 <b>Ubuntu and Fedora both package it</b> with the linux-firmware package and Ubuntu also includes it in the various linux-image packages.

	== Known Issues ==		== Known Issues ==

Alison Chaiken: Formatting

2013-01-05T00:27:59Z

Formatting

← Older revision		Revision as of 00:27, 5 January 2013
Line 6:		Line 6:
	== Tips ==		== 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.		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.
	~~=== Tip Name ===~~		=== Obtaining the ti_3410.fw file needed by ti_usb_3410_5052 ===

	==== 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:		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:
Line 20:		Line 18:

	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.		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.


	== Known Issues ==		== Known Issues ==

Alison Chaiken: Add script for obtaining ti_3410 firmware file.

2013-01-05T00:27:14Z

Add script for obtaining ti_3410 firmware file.

@@ Line 7: / Line 7: @@
 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.
 === Tip Name ===
-Example tip, replace this one first.
 == Known Issues ==

Dvhart at 16:47, 4 January 2013

2013-01-04T16:47:23Z

← Older revision		Revision as of 16:47, 4 January 2013
Line 1:		Line 1:
	__TOC__		__TOC__

	~~This is a placeholder for tips and tricks on using the Fish River Island 2 (FRI2) BSP with the Yocto Project.~~

	== Resources ==		== Resources ==
	[http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README?h=master Latest FRI2 README]		[http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README?h=master 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.
			=== Tip Name ===
			Example tip, replace this one first.

	== Known Issues ==		== Known Issues ==

Dvhart at 05:14, 8 December 2012

2012-12-08T05:14:34Z

← Older revision		Revision as of 05:14, 8 December 2012
Line 2:		Line 2:

	This is a placeholder for tips and tricks on using the Fish River Island 2 (FRI2) BSP with the Yocto Project.		This is a placeholder for tips and tricks on using the Fish River Island 2 (FRI2) BSP with the Yocto Project.

			== Resources ==
			[http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README?h=master Latest FRI2 README]

	== Known Issues ==		== Known Issues ==

Dvhart: /* Warning at arch/x86/kernel/apic/ipi.c */

2012-08-03T16:39:49Z

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

← Older revision		Revision as of 16:39, 3 August 2012
Line 15:		Line 15:
	...		...

	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.		This appears to be a known issue with how IPIs are handled within the generic SMP infrastructure. A fix is being discussed on [https://lkml.org/lkml/2012/2/19/11 LKML], but the warning appears to be benign.

Dvhart: /* Warning at arch/x86/kernel/apic/ipi.c */

2012-08-03T16:39:13Z

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

← Older revision		Revision as of 16:39, 3 August 2012
Line 15:		Line 15:
	...		...

	This appears to be a known issue with how IPIs are handled within the generic SMP infrastructure. I fix is being discussed on LKML, but the warning appears to be benign.		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.

Dvhart at 16:38, 3 August 2012

2012-08-03T16:38:35Z

← Older revision		Revision as of 16:38, 3 August 2012
Line 1:		Line 1:
			__TOC__

	This is a placeholder for tips and tricks on using the Fish River Island 2 (FRI2) BSP with the Yocto Project.		This is a placeholder for tips and tricks on using the Fish River Island 2 (FRI2) BSP with the Yocto Project.

Dvhart at 16:36, 3 August 2012

2012-08-03T16:36:44Z

← Older revision		Revision as of 16:36, 3 August 2012
Line 1:		Line 1:
	This is a placeholder for tips and tricks on using the Fish River Island 2 (FRI2) BSP with the Yocto Project.		This is a placeholder for tips and tricks on using the Fish River Island 2 (FRI2) BSP with the Yocto Project.

			== 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. I fix is being discussed on LKML, but the warning appears to be benign.