Slashdot Mirror


Why Intel Wants BIOS Dead

An anonymous reader writes "This brief, readable whitepaper by Brian Richardson, a product manager at BIOS-vendor AMI, examines the history of BIOS firmware and explains why chipmaker Intel has invested much time and effort to create and promote a firmware framework to replace BIOS. Why would a chip company care about firmware? Read Richardson's paper about the 'Evolution of BIOS: EFI, the Framework, and beyond' to find out."

4 of 65 comments (clear)

  1. OpenFirmware by noselasd · · Score: 4, Insightful

    Why can't all the PC architecture vendors just get along and use OpenFirmware like most other sane architectures ?

  2. Re:For the lazy... by FooAtWFU · · Score: 4, Insightful
    they just want the current firmware standard to evolve to better meet the needs of today's technology.

    For values of "today's technology" equal to "Microsoft's latest DRM systems."

    --
    The World Wide Web is dying. Soon, we shall have only the Internet.
  3. Ugh. by bluephone · · Score: 4, Insightful
    Yes, I RTFA, and Jesus H. Christ on a stick, that's a worthless article. I'm sending the site an email, I want those 5 minutes of my life back. As any high school geek could have said, the article boils down to the BIOS is still limited to Real Mode 8086 emulation, and thus everything until an OS kicks in is limited to this as well, as hopefully 80% of /.ers know. Then, it goes on to say EFI solves this. Not how, no technical details, aside from you can boot from USB devices (as you can with some modern BIOSs) without emulating a disk device.

    Worthless article. I could have gotten that from the Intel EFI press releases put out FOUR YEARS AGO.

    --
    jX [ Make everything as simple as possible, but no simpler. - Einstein ]
  4. Re:It's DOS, not BIOS by anti-NAT · · Score: 4, Insightful

    Who in their right minds is going to buy a new PC and put such an old OS on it?

    Corporates who need to upgrade to a new server for performance, yet can't afford to spend huge amounts of money upgrading the applications to suit the newer OSes.

    I'd be guessing you haven't worked in the large(ish) enterprise/corporate world. If you haven't, and haven't been exposed to custom applications, you probably aren't aware that hardware and the OSes to run the applications is a very, very minor cost when compared to the total costs of developing, deploying and supporting a custom application.

    The great advantage of the existing PC architecture has been the fact that if your applications weren't performing fast enough, you could just throw newer hardware at it. An over-the-weekend upgrade could result in dramatic performance increases. Compare that to having to port an application to a new architecture, test it, fix bugs, and if it the opportunity was taken to improve it at the time by changing the way it worked, running training courses for users and support staff, all of which may take six to twelve months or more.

    Continuing backward compatibility is probably the primary reason for the success of the PC architecture over the last twenty years.

    --
    The Internet's nature is peer to peer - 20050301_cs_profs.pdf