> On Oct 22, 2014, at 6:07 PM, Tian, Hot <[email protected]> wrote: > > Can we use this? > > 9.3.6.7 PIWG Firmware Volume This type is used by systems implementing the > UEFI PI Specification to describe a firmware volume. The exact format and > usage are defined in that specification. > I thought eMMC cards were usually formatted as FAT?
The PIWG Firmware Volume device path is typically installed by the DXE Core based on an FV HOB being detected or a gDS->ProcessFirmwareVolume(). https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdeModulePkg/Core/Dxe/FwVolBlock/FwVolBlock.c The CONTROLLER_DEVICE_PATH was added to the UEFI (EFI) specification to deal with devices that were just produced by talking to different registers. So if a PCI device produced 2 device BAR1 and BAR2, the CONTROLLER_DEVICE_PATH would be used to tell the devices apart. So how does the software figure out which eMMC/SD card it is talking to on the PCI device? Thanks, Andrew Fish > > From: Igor Sharovar [mailto:[email protected]] > Sent: Thursday, October 23, 2014 12:52 AM > To: [email protected] > Subject: Re: [edk2] Firmware Volume Block Protocol > > You likely need to add an additional entry in the DevicePath representing > your "Media Type". For example, you may add "Vendor GUID"( not recomended) or > LUN. > > > On Tue, Oct 21, 2014 at 9:37 PM, Andrew Fish <[email protected] > <mailto:[email protected]>> wrote: > > On Oct 21, 2014, at 8:08 PM, Narinder Dhillon <[email protected] > <mailto:[email protected]>> wrote: > > Hi Andrew, > > It is a controller on PCIe bus, behind a PCIe root. > > > If the device only supports a single eMMC/SD card, then you can use the PCI > IO handle device path. If it supports multiple eMMC/SD cards then you can use > the PCI IO device path plus a CONTROLLER_DEVICE_PATH. The > CONTROLLER_DEVICE_PATH represents that the PCI device has more than one > device embedded in it. The ControllerNumber is just the same enumeration that > the EFI driver and OS driver use. > > Thanks, > > Andrew Fish > > > Thanx, > > On Tue, Oct 21, 2014 at 5:52 PM, Tian, Feng <[email protected] > <mailto:[email protected]>> wrote: > As far as I know, UEFI doesn’t define such device path for eMMC or SD device. > So it’s hard to work out a generic/cross-platform solution. > > But you could develop a platform-specific solution, such as using Vendor > Device Path or Controller Device Path, to represent the location of eMMC > device. > > From: Andrew Fish [mailto:[email protected] <mailto:[email protected]>] > Sent: Wednesday, October 22, 2014 08:36 > To: [email protected] <mailto:[email protected]> > Subject: Re: [edk2] Firmware Volume Block Protocol > > > On Oct 21, 2014, at 5:31 PM, Narinder Dhillon <[email protected] > <mailto:[email protected]>> wrote: > > Hi All, > > I am trying to implement a non-volatile variable storage at the top end of an > eMMC flash device. From all the reading, I have implemented the firmware > volume block protocol in the eMMC driver. > What I can't figure is, what kind of device path do I install along with FVB > protocol ? > I have seen examples of vendor hardware, media device. > > > How does the OS discover the eMMC flash device? > > Thanks, > > Andrew Fish > > > Thanx. > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho <http://p.sf.net/sfu/Zoho> > _______________________________________________ > edk2-devel mailing list > [email protected] <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/edk2-devel > <https://lists.sourceforge.net/lists/listinfo/edk2-devel> > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho_______________________________________________ > <http://p.sf.net/sfu/Zoho_______________________________________________> > edk2-devel mailing list > [email protected] <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/edk2-devel > <https://lists.sourceforge.net/lists/listinfo/edk2-devel> > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho <http://p.sf.net/sfu/Zoho> > _______________________________________________ > edk2-devel mailing list > [email protected] <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/edk2-devel > <https://lists.sourceforge.net/lists/listinfo/edk2-devel> > > ------------------------------------------------------------------------------ > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/edk2-devel
------------------------------------------------------------------------------
_______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
