Slashdot Mirror


AMD Provides Fusion Support For Coreboot

An anonymous reader writes "AMD has done a big code drop providing Fusion support for Coreboot, the project that once was called LinuxBIOS for providing an open source BIOS implementation." A lack of vendor support has long made the task of the coreboot developers difficult. Support for what is slated to be a common chipset is pretty encouraging, and will hopefully make it easier to run an entirely Free Software system for diehards like RMS.

13 of 71 comments (clear)

  1. Wait! by otravi · · Score: 3, Insightful

    What's this? A Phoronix article where I _don't_ have to click through eleven other articles to find the source?

    Other than that: Hopefully this will make coreboot's future brighter, by a lot.

  2. Speed by Nerdfest · · Score: 2

    Open source altruism aside, i want a stable, flexible, fast-booting BIOS. The standard BIOS that comes with most motherboards is awful, and is frequently missing important features.

    1. Re:Speed by Elbereth · · Score: 2

      Open source altruism aside, i want a stable, flexible, fast-booting BIOS. The standard BIOS that comes with most motherboards is awful, and is frequently missing important features.

      What's so wrong with your motherboard's BIOS? What features is it missing?

      What brand and model motherboard do you have? I'm predicting it's not an Asus board, because Asus has awesome BIOSes.

    2. Re:Speed by blair1q · · Score: 2

      Interesting. Most BIOS I've seen have had too many features, leading to the slow booting that you noted.

    3. Re:Speed by Ant+P. · · Score: 3, Insightful

      I've got a Jetway mini-ITX, and its BIOS/ACPI is so FUBAR that they managed to break *all* power management stuff along with access to the temperature sensor and fan speed controls. Y'know, the main reasons for buying a low-speed mini-ITX in the first place.

      And unlike all other mobo manufacturers I've used (Asus is good, and so is Gigabyte), this one seems to never, ever put out updates to fix their broken firmware, let alone add features to it.

    4. Re:Speed by SScorpio · · Score: 2

      You could do what some BIOSes already do, which is hold down a key. Just hold down the key as you turn the computer on and it would go into the settings menu.

    5. Re:Speed by Lumpy · · Score: 2

      Software programmers can design hardware worth shit. So I guess we are even.

      Plus BIOS is written in a secret programming language called assembler. Something that it seems that most programmers can't do anymore.

      --
      Do not look at laser with remaining good eye.
    6. Re:Speed by LWATCDR · · Score: 2

      True. I wonder just how fast and effecent you could make something like the Atom if you dropped all the old odds and ends that it has to support. Things like 8087, MMX, 286 instructions, and just had it support 64bit mode.
      Yes a lot of stuff would not run anymore but for say the mobile market and embedded it could be a real winner.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    7. Re:Speed by hairyfeet · · Score: 3, Insightful

      And you just hit the nail on the head of why this will NEVER take off...planned obsolescence. The OEMs want you to have to blow cash for a new laptop every couple of years, and having a tweak-able BIOS doesn't help in that regard. The same goes for the ass raping most of these companies charge for replacement parts for laptops. Often it is cheaper to shitcan the laptop and get another one and that is precisely the point in a nutshell.

      Sadly I doubt we'll ever see a truly open laptop BIOS because it is in the short term interest of the companies to make laptops into disposable devices, damn the waste and effect on the environment. This is just another example of why "damn everything but the quarterly earnings report!" hurts us all in the long run. It is a waste of material, a waste of resources, a poisoning of the environment, all to make a product that could easily last 10 years with a little thought into a 2 year or less disposable item. Just sad.

      --
      ACs don't waste your time replying, your posts are never seen by me.
  3. Also a smart move. by Ungrounded+Lightning · · Score: 2

    I think even just the willingness to contribute something to an open BIOS implementation is very commendable.

    Additionally, it could be a smart move for AMD. A FOSS BIOS could give them a competitive advantage in sales, as the only/first manufacturer of modern high-end chipsets enabling personal computer products where a full code audit or replacement with user-trusted secure code would be practical.

    Compare this to Intel, which includes support for remote administration in the chips, BIOS, and network adapter firmware - as a "feature". This runs under the OS, invisible to it if desired and unstoppable, and provides a hardware man-in-the-middle that can completely control the system - even "phoning home" when traveling or at an IP address not previously known to the "remote administrator".

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  4. Thanks, AMD by drinkypoo · · Score: 3, Insightful

    That's very nice. Of course, there's more to motherboard support than the chipset and CPU, but they are two major hurdles.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  5. Not just for "diehards like RMS"; for you! by KonoWatakushi · · Score: 2

    It may come as a surprise, but right now, someone else owns your entire platform. The BIOS/EFI do not merely boot the system, they also provide run time services in the form of System Management Mode.

    That's right, your system is running black box code at runtime. The TPM already lives there, and if you are "lucky", the future malware will be limited to DRM which can't be circumvented, or systems that only run signed code. The implications for security are staggering, and considering that modern systems even have access to your network from this code, the opportunity for abuse is truly frightening. (How trivial would it be for your government--or the manufacturers in China--to install backdoors, remote key logging facilities, or root kits and such?)

    Support Coreboot, so that we may retain control of our own systems. Many thanks to its authors for their persistence, and AMD for their generous contributions. For further information, there was also an interesting google talk a while back.