Slashdot Mirror

← Back to Stories (view on slashdot.org)

Free/Open Source Software Hardware Requirements?

Posted by Cliff on from the flip-side-of-the-ole-chestnut dept.

Bender asks: "Most on Slashdot seem to be concerned with getting Free/Open Source software to be compatible with hardware (firmware, register sets, etc). My question is from the other side of the table: I'm in the hardware business and I'm wondering if there are any central guidelines to better guarantee compatibility with Linux/*BSD. As an example, to guarantee that our hardware runs Microsoft Windows, we have to conform to the Windows Logo Program Requirements. These requirements dictate (among other things) firmware interfaces, debug ports, and DRM. Some of these requirements, if not implemented carefully, could trigger incompatibilities with non-Microsoft operating systems. Is there a Linux/*BSD equivalent to the Microsoft requirements to allow hardware designers to build OS agnostic systems?"

5 of 228 comments (clear)

  1. tricky questions.. by Anonymous Coward · · Score: 2, Funny

    Why not ask someone who doesnt know?

    After all, this seems like there will be a 'right' answer to this question, and where's the fun in that?

  2. Re:To make it work with linux... by operagost · · Score: 5, Funny

    He said "Major Kernel Programmer," so you will need a commission and about 10 years in the Army. Too much trouble for a few free SATA controllers I'd say.

    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
  3. Just a coincidence move along now. by mlush · · Score: 4, Funny
    Some of these requirements, if not implemented carefully, could trigger incompatibilities with non-Microsoft operating systems.

    <Microsoft>Thats not a bug its a feature</Microsoft>

  4. Great Idea!11 Nerds will hate it. by gelfling · · Score: 2, Funny

    This is a wonderful suggestion which is why every nerd and geek who furiously insists on porting Linux to a parking meter he stole at the last Trekkie convention will object to it.

  5. Re:Well... by DudemanX · · Score: 2, Funny

    What's funny about that(and purely anecdotal) is that the WHQL certified driver from November gave me blue screens in World of Warcraft and other random lockups while the uncertified drivers from July have yet to give a hiccup. I've also had issues with some WHQL drivers for the Sound Blaster Live, while having no problems with other non-WHQL drivers for things like SATA controllers.

    So as far as I'm concerned the only advantage to WHQL drivers is that I don't have to make an extra mouse click during a driver install.
    Thanks Microsoft!