Head here to get the latest UEFI plugfest presentations on a variety of topics, although security dominates the topic list, with top notch presentations by Insyde, Intel (and here), ARM, Phoenix and Microsoft. The presentation by Microsoft is a redacted version of what was presented live because it contained details about unreleased versions of the Windows operating systems.
After security, it was programming languages, with presentations by Intel for ACPI Source Language (ASL) and MicroPython.
My presentation focused on adapting Microsoft's Security Development Lifecycle to UEFI and firmware, based on our ongoing experience at Insyde. Conversations afterward showed a great level of interest in introducing these processes into an industry that has traditionally not worried about this level of discipline in security.
Rounding out the topic list was the state of UEFI (the illustrious Mark Doran, Intel), SMBIOS and ACPI table construction (ARM), EDK2 platforms (Linaro), UEFI capsule update (Microsoft), and NVMe (AMI).
Showing posts with label AMI. Show all posts
Showing posts with label AMI. Show all posts
Thursday, April 05, 2018
Thursday, November 01, 2012
Phoenix and AMI Press Release: ARMv8, AppliedMicro and an IDE
[Disclaimer: I am an ex-Phoenix employee and currently work for a Phoenix and AMI competitor]
UPDATE: Ran into a Phoenix employee at the ARM TechCon yesterday, and he invited me to go watch their X-Gene firmware at 11:00am. Cool.
Phoenix Technologies, one of the three mainstream independent BIOS vendors (IBVs) just put out a press release talking about their support for the new ARMv8 64-bit processor architecture and their relationship with AppliedMicro, who is developing their own variant, called the X-Gene. Kudos. Good stuff. Immediately followed by AMI. AMI goes further to say they will be demoing it today at the ARM TechCon in Santa Clara, where I am headed as I type this.
It is with the 64-bit ARM that I expect to see the real transition to UEFI boot-loaders happen. With 32-bit ARM cores, there were a lot of supported choices because UEFI was (relatively speaking) late to the game. But ARM has been working with the ABST (ARM Binding Sub Team) within UEFI for a while. So, the question is: will QNX and WindRiver and other embedded OS' go ahead and follow Linux's lead and support UEFI as the standard boot model for ARM.
But the funny thing about the Phoenix press-release is that it contains IDE in the title, but nowhere in the text does it ever talk about an "integrated development environment". An IDE would be something like Eclipse or Visual Studio. They do talk about an "enhanced build environment" and "award winning...tools". So I went to their web site to check the press release and couldn't find it there. But when I looked at other sites, they used the phrase "Independent Build Environment". Ok. That makes more sense. One of the other blogs just muffed it.
UPDATE: Ran into a Phoenix employee at the ARM TechCon yesterday, and he invited me to go watch their X-Gene firmware at 11:00am. Cool.
Phoenix Technologies, one of the three mainstream independent BIOS vendors (IBVs) just put out a press release talking about their support for the new ARMv8 64-bit processor architecture and their relationship with AppliedMicro, who is developing their own variant, called the X-Gene. Kudos. Good stuff. Immediately followed by AMI. AMI goes further to say they will be demoing it today at the ARM TechCon in Santa Clara, where I am headed as I type this.
It is with the 64-bit ARM that I expect to see the real transition to UEFI boot-loaders happen. With 32-bit ARM cores, there were a lot of supported choices because UEFI was (relatively speaking) late to the game. But ARM has been working with the ABST (ARM Binding Sub Team) within UEFI for a while. So, the question is: will QNX and WindRiver and other embedded OS' go ahead and follow Linux's lead and support UEFI as the standard boot model for ARM.
But the funny thing about the Phoenix press-release is that it contains IDE in the title, but nowhere in the text does it ever talk about an "integrated development environment". An IDE would be something like Eclipse or Visual Studio. They do talk about an "enhanced build environment" and "award winning...tools". So I went to their web site to check the press release and couldn't find it there. But when I looked at other sites, they used the phrase "Independent Build Environment". Ok. That makes more sense. One of the other blogs just muffed it.
Subscribe to:
Posts (Atom)
