3068 2012-09-06 21:37:02 +0000 [FRI2]MMC detection FastBoot firmware 2013-03-05 00:39:13 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-intel 1.3 Other x86 RESOLVED INVALID Medium+ normal 1.4 1 alexandrux.palalau dvhart tom.zanussi --- --- --- oldest_to_newest 24898 0 alexandrux.palalau 2012-09-06 21:37:02 +0000 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. 24899 1 dvhart 2012-09-06 21:47:15 +0000 Discussing with the firmware team. Will report back. 24904 2 dvhart 2012-09-06 23:12:37 +0000 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? 25172 3 dvhart 2012-09-13 14:37:42 +0000 Being worked on by the fastboot team. 26909 4 dvhart 2012-10-25 14:58:42 +0000 This is resolved in the 1018 build. 27322 5 alexandrux.palalau 2012-11-09 11:14:27 +0000 Behavior is still encountered with http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20121102-2/machines/fri2/ core-image-sato-sdk image. 28057 6 dvhart 2012-12-06 15:59:48 +0000 . 30422 7 dvhart 2013-03-05 00:39:13 +0000 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.