DataHub has been deprecated. PI spec has removed it.

ReportStatusCode() could have many different implementations or be outputted to 
different "channels", such as serial port, port80, datahub and so on.

So for your 1st question, need check your ReportStatusCode() implementation to 
see if it supports output to DataHub.

For 2nd question, it should be ok because they are two different layer's 
interface.

From: Felipe Martins [mailto:[email protected]]
Sent: Thursday, June 27, 2013 08:45
To: [email protected]
Subject: [edk2] EFI Data Hub and ReportStatusCode() API

Hello everyone,

I apologize in advance if this list is not the appropriate place to ask 
questions concerning the Intel Platform Innovation Framework, but I couldn't 
find any other active community that could help me with my questions.
I am trying to understand the relationship between the EFI Data Hub and 
ReportStatusCode() API(both from the Intel Platform Innovation Framewok) and 
I've got a few questions about details that weren't made clear from the specs:

  *   The EFI DataHub spec says that a record declaring a class of 
EFI_DATA_CLASS_PROGRESS_CODE indicates that the record was logged via the 
ReportStatusCode() API. Does that mean that if I use ReportStatusCode() to log 
a progress message, then it will be available to be read from the Data Hub? I 
tried to reproduce this scenario, but even though ReportStatusCode() returned 
EFI_SUCCESS, there were no records in the DataHub when I tried to read from it. 
Is it the expected behavior? I'd like to point out that I could successfully 
read records that were logged using the DataHub protocol instead of the 
ReportStatusCode() API.

  *   Can I use the DataHub protocol to log a progress record or should it be 
done only via ReportStatusCode()? I ask that because the Data Hub spec seems to 
indicate that those should only be written using ReportStatusCode() and, 
despite the fact that I managed to write progress records using the DataHub 
protocol, I worry that it might "break" something.
Thanks in advance for any help.
Att,
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to