Skip to content

R&D / new frontier

Get kernels and low-level code running on new hardware, accepted against agreed benchmarks.

A new chip sits idle until the workloads you need run well on it. We use our own AI platform to generate compute kernels and low-level code, and test correctness and performance on your target chip.

  • Kernels
  • Ports
  • Low-level code

Correctness tests and performance benchmarks

  • Your target platforms

Today

New chips and boards can sit waiting on kernels, ports and drivers that specialists write by hand.

A new target can add kernel, porting or driver work to your team’s backlog, and missing kernel or driver support can block the workloads you need.

  • First build

    Compute kernels for the workloads you select, on one target chip

    Kernels and the low-level code they need, checked for correctness and performance on that chip.

  • How it is tested and accepted

    The correctness tests and benchmarks pass on your chip.

    Correctness tests and performance benchmarks, measured against a baseline you nominate, such as your current hand-written kernels or the vendor library.

    What counts as passing is set per engagement: which tests and benchmarks, on which hardware, against which baseline.

    • We agree on acceptance criteria with you before we build, then test every build against them.
    How we test what we build

Other first builds

  • Code porting across platforms

    When software has to move to a new processor, the port is often done by hand.

    First build

    One codebase ported to one target processor, with the correctness tests the port must pass there.

  • Low-level software generation

    Drivers and board support code often get rewritten by hand for each new board or chip.

    First build

    Low-level code for one agreed board or chip, with the tests it must pass on that hardware.

  • What you have at the end

    Code that passes on your hardware.

    • Kernels, ports or low-level code for the hardware you named, with the test results from that hardware.
    • The tests and benchmarks used to accept the work, set up to run on your target platforms.
  • Who it is for

    Software leaders with new hardware to bring up.

    The VP Software or head of R&D, who owns the bring-up plan.

    Day to day the work sits with compiler, firmware and platform software leads.

    See solutions by role

Industries

Where kernel and porting work is a first build

  • Semiconductor

    First build: kernel bring-up on one chip, accepted against agreed benchmarks.

  • Robotics

    First build: a firmware port to your next board.

Free consultation

Start with one chip, codebase or board. We’ll show you what we’d build first.

In a free consultation we learn how the work gets done today and where AI automation would pay off. You leave with a recommended first build, or a plain answer that it isn’t a fit.