From: "Sean" <spbrogan@outlook.com>
To: Laszlo Ersek <lersek@redhat.com>,
devel@edk2.groups.io, Bret Barkelew <Bret.Barkelew@microsoft.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Matthew Carlson <macarl@microsoft.com>,
Leendert van Doorn <leendert@microsoft.com>
Subject: Re: [edk2-devel] who can help restore the iBFT spec link to working state?
Date: Tue, 6 Oct 2020 16:24:40 -0700 [thread overview]
Message-ID: <MN2PR07MB6974C534AE6D94BC0AFA125CC80D0@MN2PR07MB6974.namprd07.prod.outlook.com> (raw)
In-Reply-To: <38c97af7-7b0c-fc63-0fe2-5fb39d9c719b@redhat.com>
iBFT has been updated to align with other ACPI enumerated tables.
https://docs.microsoft.com/en-us/windows-hardware/drivers/bringup/acpi-system-description-tables#iscsi-boot-firmware-table-ibft
Thanks
Sean
On 9/28/2020 10:59 AM, Laszlo Ersek wrote:
> On 09/25/20 18:02, Sean Brogan wrote:
>> I see what i can find.
>>
>> Thanks for pointing this out.
>
> Thank you Sean!
> Laszlo
>
>> On 9/25/2020 7:20 AM, Laszlo Ersek wrote:
>>> Hi,
>>>
>>> the iBFT spec link
>>>
>>> http://www.microsoft.com/whdc/system/platform/firmware/ibft.mspx
>>>
>>> as shown at
>>>
>>> https://uefi.org/acpi
>>>
>>> does not work (it has not worked since at least August 13th, which is
>>> when I first reported this issue on the ASWG mailing list).
>>>
>>> Who from Microsoft can please help the community with a working, stable
>>> link to the iBFT spec?
>>>
>>> Thanks,
>>> Laszlo
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
next prev parent reply other threads:[~2020-10-06 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 14:20 who can help restore the iBFT spec link to working state? Laszlo Ersek
2020-09-25 16:02 ` [edk2-devel] " Sean
2020-09-28 17:59 ` Laszlo Ersek
2020-10-06 23:24 ` Sean [this message]
2020-10-07 12:04 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MN2PR07MB6974C534AE6D94BC0AFA125CC80D0@MN2PR07MB6974.namprd07.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox