Bug 3068

Summary:	[FRI2]MMC detection FastBoot firmware
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Alexandru Palalau <alexandrux.palalau>
Component:	bsps-meta-intel	Assignee:	Darren Hart <dvhart>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	tom.zanussi
Version:	1.3
Target Milestone:	1.4
Hardware:	Other
OS:	x86
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Alexandru Palalau 2012-09-06 21:37:02 UTC

The secondary MMC cannot be detected under Intel Fast Boot firmware on the FRI2.
Tested the behavior with autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120731-2/machines/fri2/core-image-sato-fri2.hddimg

dmesg does not return any message when inserting the MMC.
Also, EFI shell does not recognize the secondary MMC.
Internal MMC does not present the described behavior.

Comment 1 Darren Hart 2012-09-06 21:47:15 UTC

Discussing with the firmware team. Will report back.

Comment 2 Darren Hart 2012-09-06 23:12:37 UTC

From the fastboot release notes:

The connect command (with the -r option) forces the shell to connect all available device support drivers to all devices in the system.  The process may take a few seconds (depending upon the nature of the external devices attached to the system). When complete, this command will allow the user access to all connected devices which the BIOS can support.

Can you try running "connect -r" from the shell? Does the secondary mmc device appear in this case?

Comment 3 Darren Hart 2012-09-13 14:37:42 UTC

Being worked on by the fastboot team.

Comment 4 Darren Hart 2012-10-25 14:58:42 UTC

This is resolved in the 1018 build.

Comment 5 Alexandru Palalau 2012-11-09 11:14:27 UTC

Behavior is still encountered with http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20121102-2/machines/fri2/ core-image-sato-sdk image.

Comment 6 Darren Hart 2012-12-06 15:59:48 UTC

Comment 7 Darren Hart 2013-03-05 00:39:13 UTC

Alex, note this is a firmware issue, not a Linux issue. As it is beyond the scope of what the Yocto Project developers can address, I'm closing as "INVALID" for lack of a better resolution.