keeping simple

Category: systems

  • Single core cell phone solution and marketing vs engineering

    FSMLabs is finally able to discuss the single core cell phone handset solution we developed with Infineon Technologies last year. This system is cool technology – literally – since it allows parts count reduction on the handset and that reduces power consumption and that reduces heat production. More to the point, in a volume driven…

  • Microkernels and why academic OS research is boring

    Andy Tanenbaum writes a defense of microkernels that (1) misses the content of Linus Torvald’s critique, (2) ignores the most relevant paper on software development, David Parnas’ Software Jewels paper, and (3) pretends RTLinux does not exist. The problem with microkernels is that they are not modular and the problem with all the “nearly ready…

  • GreenHills, foreigners, and the gummi bear threat

    When GreenHills launched their anti-Linux offensive, they crossed a line – and I doubt they even knew it. To cast doubt on the value of Linux in critical applications, GreenHills tried to create a scare about the nationality and “loyalty” of engineers working on Linux. This is stupid on three levels. First, software security is…

  • Pitiful formal methods in computer science

    FSMLabs is making its way through the DO178 requirements and we’ve given a lot of thought to Common Criteria over the last couple years. One of the advantages of DO178 is that it does not accept the totally untested and frankly unlikely premises of “formal methods”. The reason mathematics has advanced so much was not…

  • Above all, the SUSPENSE: Wind River’s DSO with Robert Mitchum and hippies! (updated)

    I’ve been meaning to write about DSO – WindRiver’s attempt to define synthetic “standards” (see the linuxdevices article for technical detail and a more serious approach). “Is DSO hype or substance?” asked Wind River CEO Ken Klein during the sponsored address, and sought to persuade the engineers in the audience that it is indeed substance…

  • Auragen computers remembered

    In the early 1980s, I worked for a start-up called Auragen Computers based in Fort Lee, New Jersey. We were making a 68K based fault tolerant UNIX based on a smart idea by Sam Glazer. Most of the software engineers lived in New York City and commuted out. Start-ups with New Yorkers have a different…

  • The long haul in the embedded software business.

    Chris Lanfear from VDC systems asks FSMLabs has the product line, but lacks the market presence and awareness that other companies have invested in with venture-backed capital. We believe the company has largely bootstrapped itself over the years and while this conservative approach has a number of benefits, it is difficult to achieve the market…

  • Digital Rights Management and Logic

    The Sony DRM fiasco is due to a common failure of requirements management logic. If an engineered system relies on certain properties, whenever you add a new requirement, you need to check consistency. You have a boat that has EnoughCargoSpace and ReasonableEnergyCost and you decide to add the requirement CantLeak. So you encase the entire…

  • Power Point, Rocket Science and dangers of compelling stories

    In American English, you can say that something is not too difficult by saying “it’s not rocket science.” We don’t have a good idiom for saying the opposite – that something is hard to understand, not bullet-pointable. Edward Tufte dislikes PowerPoint because it can be used in a way that obscures critical data under a…

  • Priority Inheritance: Hack or Error

    The subject of priority inheritance has come up again on the Linux kernel mailing list and Torvalds correctly notes “Friends don’t let friends use priority inheritance”. Just don’t do it. If you really need it, your system is broken anyway. “Priority inheritance” is similar to “soft real-time” in that both are efforts to avoid building…