GithubHelp home page GithubHelp logo

Comments (3)

NikolajSchlej avatar NikolajSchlej commented on August 15, 2024 1

The image is mostly conforming to early Framework specs listed here: https://www.intel.com/content/www/us/en/architecture-and-technology/unified-extensible-firmware-interface/efi-specifications-general-technology.html
There are several quirks that are Intel-specific and don't really worth bothering about because .BIO files aren't really UEFI images, they are update capsules. The real image can be dumped from SPI flash via Intel Flash Programming Tool, flashrom or hardware SPI programmer, then opened in UEFITool. I expect most parsing issues to be gone, and the rest will be something like "Intel decided to take a section type that was unused and use it for their own thing, then UEFI spec defined it as something else entirely and UEFITool gets confused".

from uefitool.

NikolajSchlej avatar NikolajSchlej commented on August 15, 2024

The file is of 2008 vintage, when things had rough edges and UEFI was still missing the Unified part. Some things did change since then, but this Framework-compatible file is a piece of legacy now, and it's unclear what value will adding proper support to all of its quirks actually brings in 2023. Thanks for reporting though.

from uefitool.

swiftgeek avatar swiftgeek commented on August 15, 2024

To me the value is that it's split it up better after extraction than legacy bios (from those that did extract correctly) and it is easier to read in ghidra decompiler (not that I'm any good at doing things in ghidra). I'm also still using that platform of that generation extensively, but couldn't find any other instance of (U)EFI for that intel generation (or even several next ones) with all the vPro features, built for (U)EFI rather than running some of them under CSM (like what happens with HP Elitebook 2530p, which also seems to extract way better now than in 2019).

If it isn't too much of a bother, any pointers as to what is going wrong with that file / what further resources could be read about pre-UEFI quirks/specs? I feel like the most broken things are with freeform subtypes, but I only make that wild guess due to how they end up being so big after extraction

EDIT:
Going through wayback it looks like UEFI 2.0 spec already existed for some time (since 03/01/06), but (U)EFI naming was just heavily inconsistent.

from uefitool.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.