Intel is working on implementation of UEFI 2.5 HTTP boot support.

Best Regards,
Ye Ting

-----Original Message-----
From: Blibbet [mailto:blib...@gmail.com] 
Sent: Saturday, June 06, 2015 7:00 AM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] UEFI HTTP Boot and Redfish support?

HP gave a talk at the Spring UEFI Forum event titled "Goodbye PXE and
IPMI. Welcome HTTP Boot and Redfish!".

But a few days ago AMI just released a new IPMI-based product, so
"Goodbye IPMI" is apparently not a universally agreed upon, pehaps
"Welcome to the party, pal!" is more approrpiate? :-)

Besides HP, who supports UEFI 2.5 HTTP Boot?

Besides HP, who supports Redfish with their UEFI implementation?

DNS/DHCP/HTTP[S] servers aside, is there enough code in TianoCore to
support HTTP Boot, or is additional non-TianoCore code required,
including HTTPS TLS support?

More generally, how do people figure out which IBV/OEMs support UEFI's
various features? Except for a few OEMs, most consumer merchant pages
for hardware rarely includes information about firmware, and the main
consumer resource AFAICT (Consumer Reports) is also ignoring firmware in
it's data. The UEFI.org pages don't have any information on this. It's
hard to determine what features in the UEFI Forum spec are in Tianocore,
and what are only in commercial products. I wish the UEFI Forum would
work with its vendor members to help clarify the features their products
include.

Heck, I'd create a new page on Wikipedia or elsewhere, if I had the data.

Thanks,
Lee
RSS: http://firmwaresecurity.com/feed




------------------------------------------------------------------------------
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to