Google Teams Up with US Government for Open-Source Chips

A computer chip.
(Image credit: Shutterstock)
4

Google and the U.S. Department of Commerce’s National Institute of Standards and Technology (NIST) on Wednesday signed a joint research and development pact under which Google will finance production of open-source chips that could be used by academic and small business researchers to build a variety of emerging applications.

The majority of newly developed devices require chips to enable their core or 'smart' functionality. But startups usually formed in universities and small businesses typically do not have money to develop their own chips, order custom chips from design houses, or procure large quantities of of-the-shelf components. But scholars and small companies tend to have some bright ideas when it comes to emerging applications, which is why to NIST decided to team up with Google to help them turn their ideas into products.

Latest Videos FromTom's Hardware
Anton Shilov
Contributing Writer

Anton Shilov is a contributing writer at Tom’s Hardware. Over the past couple of decades, he has covered everything from CPUs and GPUs to supercomputers and from modern process technologies and latest fab tools to high-tech industry trends.

  • WINTERLORD
    This is Kool outside of building new fabs and the chips act education is a huge part of innovation all this investment into semiconductors hope there on track with education to for all those nice new fabs. In alot of big cities Spanish is a requirment in the introduction (class you have to take to start college) iv always thought rather than teaching a second language maybe computer programming or somthing to that affect should be required as it prolly is in china
    Reply
  • jackt
    there will be a open source backdoor ?
    Reply
  • InvalidError
    jackt said:
    there will be a open source backdoor ?
    If you layout your own chip, it would be extremely difficult for a third-party to insert functionality without causing silicon results to have multiple inexplicable divergences from post-place-and-route simulation results. To put in a backdoor after-the-fact, the "attacker" would need to reverse-engineer your design to find out where and how to insert it.

    If an "open foundry" was going to put backdoors in, it would have to be integrated into IP-cores (ex.: XPU cores, USB, PCIe, Ethernet, memory, etc.controllers) you put in your design, then the foundry only needs to worry about having at least one way (ex.: Ethernet, USB, PCIe) to access its IPcore-to-IPcore network and installed backdoors.
    Reply
  • jackt
    InvalidError said:
    it would be extremely difficult for a third-party to insert functionality without causing silicon results to have multiple inexplicable divergences...

    not a problem if both parts agree.
    Reply