Switchboard

Actions Status Documentation Status PyPI version License

Introduction

Switchboard (SB) is a framework for communication between distinct hardware models, such as RTL simulations, RTL implemented on FPGAs, and fast SW models. This makes it possible to simulate large hardware systems in a distributed fashion, using whatever models are available for the different components.

In such a simulation, each hardware model has one or more SB ports. Each is unidirectional: it may act as an input or an output, but not both. In addition, each SB connection is single-producer, single-consumer (SPSC): an output port may not drive more than one input port, and an input port may not be driven by more than one output port.

Here's an example of what a switchboard connection topology might look like:

image

The method for adding a switchboard port depends on the language that a HW model is implemented in. For RTL-based models, SB ports are instantiated as Verilog models, whereas for C++ and Python-based models, these ports are instantiated as objects. We provide both a low-level interface for moving data directly between SB ports, as well as a higher-level interface for running UMI transactions over SB connections.

Under the hood, communication happens through shared-memory queues, where an SB output port is driving packets into the queue, and an SB input port is reading from that queue. This standardization is what allows any two kinds of models to talk to each other. A shared-memory SPSC queue is an appealing common interface because it is one of the fastest interprocess communication techniques, with latencies on the order of hundreds of nanoseconds; no system calls are required to transmit and receive data. At the same time, this type of queue is straightforward to implement for FPGA platforms, with queue read and write operations only requiring a handful of memory transactions.

For an in depth explanation of the theory and philosophy behind Switchboard, we recommend reading the paper Switchboard: an Open-Source Framework for Modular Simulation of Large Hardware Systems".

If used for research, please cite Switchboard by the following publication:

@misc{herbst2024switchboardopensourceframeworkmodular,
      title={Switchboard: An Open-Source Framework for Modular Simulation of Large Hardware Systems},
      author={Steven Herbst and Noah Moroze and Edgar Iglesias and Andreas Olofsson},
      year={2024},
      eprint={2407.20537},
      archivePrefix={arXiv},
      primaryClass={cs.DC},
      url={https://arxiv.org/abs/2407.20537},
}

Installation

The fastest way to install this package is from PyPI:

pip install switchboard-hw

However, if you want to run the examples below (or if you're a switchboard developer), clone this repository and install the Python package in-place:

git clone https://github.com/zeroasiccorp/switchboard.git

cd switchboard

git submodule update --init

pip install --upgrade pip

pip install -e .

Examples

Various examples demonstrating the features of switchboard are in the examples folder. If you'd like to run them yourself, please run this command first:

pip install -r examples/requirements.txt

This clones some additional repositories that are needed by the examples.

A good starting point is the python example, where a Python script sends packets to and receives packets from a Verilator RTL simulation. The configuration is simple: there is a small RTL simulation that accepts an SB packet, increments the data payload, and transmits the result on its SB output port. On the other side, a Python script sends an SB packet to the simulation, and checks that the packet it gets back has been incremented.

image

To run this example, you'll need verilator (sudo apt install verilator for Ubuntu, brew install verilator for macOS). You can then run the example by changing directory to examples/python and then typing make. That should produce output similar to the following:

*** TX packet ***
dest: 123456789
last: 1
data: [ 0  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
 24 25 26 27 28 29 30 31]

*** RX packet ***
dest: 123456789
last: 1
data: [ 1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
 25 26 27 28 29 30 31 32]

- ../verilog/testbench.sv:72: Verilog $finish
PASS!

To get a sense of how this works, open the Python script examples/python/test.py. The core logic is essentially:

from switchboard import PySbPacket, PySbTx, PySbRx

...

tx = PySbTx("to_rtl.q", fresh=True)
rx = PySbRx("from_rtl.q", fresh=True)

...

txp = PySbPacket(...)
tx.send(txp)

...

rxp = rx.recv()

In other words, we create an SB output port (tx) and an SB input port (rx). An SB packet is then created (txp) and sent via the output port. Finally, a new SB packet is received from the input port.

To get a sense of how switchboard is used in RTL, have a look at the Verilog part of this example in examples/python/testbench.sv. The core logic is the instantiation of queue_to_sb_sim (SB input port) and sb_to_queue_sim (SB output port), along with the initialization step to define the name of each SB connection. Notice that the Python output port is matched to the Verilog input port (to_rtl.q) and similarly the Python input port is matched to the Verilog output port (from_rtl.q).

`include "switchboard.vh"

...

`SB_WIRES(to_rtl, DW);
`QUEUE_TO_SB_SIM(to_rtl, DW, "to_rtl.q");

...

`SB_WIRES(from_rtl, DW);
`SB_TO_QUEUE_SIM(from_rtl, DW, "from_rtl.q");

Using the same name for two ports is what establishes a connection between them. You can use any name that you like for a SB connection, as long as it is a valid file name. The reason is that SB connections are visible as files on your file system. After this example runs, it will leave behind files called to_rtl.q and from_rtl.q. It's convenient to name SB connections in a way that is amenable to pattern matching, so that you can do things like rm *.q to clean up old connections.

We encourage you to explore the other examples, which demonstrate simulation with Icarus Verilog and switchboard's C++ library (minimal), bridging SB connections via TCP (tcp), and switchboard's UMI abstraction (umiram).

Build automation

We also provide build automation powered by SiliconCompiler that makes it easy to build RTL simulations with switchboard infrastructure (queue_to_sb_sim, sb_to_queue_sim, etc.). This is mainly important because Verilog DPI and VPI are used under the hood, requiring certain flags to be passed to the RTL simulator during the build. Using our build automation lets you focus on specifying RTL sources, without having to deal with these details.

As an example, we return to examples/python. The basic logic for a Verilator build is:

from switchboard import SbDut

dut = SbDut('name-of-top-level-module')

dut.input('path/to/file/1')
dut.input('path/to/file/2')
...

dut.build()

dut.simulate()

In other words, create an SbDut object, input() files, build() it to compile the Verilator simulator, and use simulate() to start the simulator. SbDut is a subclass of siliconcompiler.Chip, which allows you to invoke a range of features to control the simulator build, such as specifying include paths and `define macros. More information about siliconcompiler.Chip can be found here.

Packet format

An SB packet is a simple data structure with three parts, defined in switchboard/cpp/switchboard.hpp.

  1. A 32-bit destination.
  2. A 32-bit flags bit vector. Currently only bit "0" is used, providing the last flag.
  3. A 416-bit data payload. This width was chosen to accommodate a UMI packet with a 256 bit payload, 64-bit source and destination addresses, and a 32-bit command. In the future, we may support parameterizable data widths for switchboard connections.

destination and flags control how the packet is routed. destination indicates the intended recipient of the packet as a flat, unsigned 32-bit integer. This provides a mechanism where a packet can be routed through multiple hops before reaching its final destination.

For example, consider using switchboard to build a simple topology in which packets can be sent from one HW block to one of two other blocks. One could indicate which block should receive the packet using the destination field, with a router transmitting the packet to the right one.

image

The last indicator (part of the flags bit vector) indicates whether there is more to come as part of a transaction. The rule is that a transmission cannot be interrupted as long as as last is zero. As an example, consider the system below, where Block A and Block B are both sending SB packets to the same port on Block C, using a router to multiplex between the two. Following the rule of unbroken transmissions, if the router starts sending a sequence of packets from Block A to Block C, it cannot switch to sending packets from Block B to Block C until it gets a packet from Block A that has last set to one. It is legal to have last=1 set in all packets, meaning that packets can be interspersed at any time.

image

The purpose of last is two-fold. For one, it simplifies the process of transmitting "burstable" protocols such as UMI through switchboard. It also provides opportunities for performance optimization. For example, if a long sequence of SB packets is being sent over TCP, the TCP bridge knows it can wait to fill up its transmission buffer as long as last=0. Without the last bit, the bridge would have to send each packet one at a time (or speculatively wait for more packets), since any given packet may be the last one.

UMI interface

In addition to supporting data movement directly through SB packets, we provide a higher-level interface for running UMI transactions over switchboard connections. The mechanisms for this can be seen in the examples/umi* examples. Here's a sketch of what UMI transactions look like, adapted from the definition of python_intf() in examples/umiram/test.py:

from switchboard import UmiTxRx

umi = UmiTxRx(from_client, to_client, fresh=True)

wrbuf = np.array([elem1, elem2, ...], dtype)
umi.write(wraddr, wrbuf)

rdbuf = umi.read(rdaddr, num, dtype)  # also a numpy array

We are no longer creating PySbTx and PySbRx objects, but rather a single UmiTxRx object with two SB ports: from_client, and to_client. Transactions are sent by the Python script through the from_client port, and responses are received back through the to_client port.

UMI write transactions are generated with the umi.write() method, which accepts an address and numpy array or scalar as arguments. This sends out one or more SUMI packets to implement the write request, packing the data, source address, destination address, and command into SB packets. Since an SB packet is 416 bits, and the two addresses + command take up 160 bits, each SB packet contains up to 256b data. Switchboard automatically splits up larger transactions into multiple SUMI packets as needed, incrementing the source and destination addresses automatically. Optional arguments to write() control where a ack'd or non-ack'd (posted) write is used and the maximum amount of data to send in a single SUMI packet. If an ack'd write is used, write() blocks until the response is received.

In a similar fashion, umi.read() reads a certain number of words from a given address. For example, umi.read(0x1234, 4, np.uint16) will send out a UMI read request with dstaddr=0x1234, LEN=3, SIZE=1 from the SB port from_client. When it gets the response to that query on to_client, it will return an array of 4 np.uint16 words to the Python script. A umi.atomic() method is also provided to generate UMI atomic transactions.

Sometimes it is convenient to work directly with SUMI packets, for example when testing a UMI FIFO or UMI router. For that situation, we provide send() and recv() methods for UmiTxRx, highlighted in examples/umi_fifo/test.py. In that exampe, we are sending SUMI packets into a UMI FIFO, and want to make sure that the sequence of packets read out of the FIFO is the same as the sequence of packets written in.

The main while loop is essentially:

txq = []

while ...:
    txp = random_umi_packet()
    if umi.send(txp, blocking=False):
        txq.append(txp)

    rxp = umi.recv(blocking=False)
    if rxp is not None:
        assert rxp == txq[0]
        txq.pop(0)

In other words, first try to write a random packet into the FIFO. If successful, add it to the back of a list of outstanding packets. Then, try to read a packet from the FIFO. If successful, make sure that the packet is equal to the oldest outstanding packet (since this is a first-in, first-out queue) and remove that outstanding packet from our records. Continue in a loop until a sufficient number of transactions have been checked.

This code example demonstrates several features:

  1. send() and recv() for working with SUMI packets, represented using PyUmiPacket objects.
  2. blocking=False for non-blocking transactions. send() returns True if successful and False otherwise; recv() returns a PyUmiPacket if successful, and None otherwise. A transaction might be unsuccessful if the underlying UMI FIFO is full or empty. For example, if we don't call umi.recv(), eventually the FIFO will fill, and subsequent send() invocations will fail (returning False). Similarly, if we keep calling umi.recv() without calling umi.send(), eventually the FIFO will be empty, and umi.recv() will fail (returning None).
  3. The ability to generate random SUMI packets with random_umi_packet(). Various optional arguments can constrain the opcodes, addresses, and data.
  4. PyUmiPacket objects can be compared using Python == and != operators. This checks if two packets have equal commands, addresses, and data.

Queue format

Under the hood, SB ports are implemented using shared memory queues. The data structure used is made simple enough that RTL running on FPGAs can directly read and write to these queues, without the need for bridge programs. In fact, if two FPGAs have access to the same memory space, they can communicate through a shared memory queue without any involvement from the host operating system, after the initial setup.

The layout of the queue is:

  • Bytes 0-3: head (int32)
  • Bytes 64-67: tail (int32)
  • Bytes 128-179: SB packet
  • Bytes 256-307: SB packet
  • Bytes 320-371: SB packet
  • ...
  • Bytes 4,032-4,095: SB packet

To write an SB packet to the queue, compute next_head = head + 1. If next_head equals 62 (the end of the queue), then set next_head to 0. If next_head equals tail, then the write fails - the queue is full. Otherwise, write the SB packet to address 128 + (64 * head), and then set head to next_head.

Reading an SB packet works in a similar fashion. If tail equals head, the read fails - the queue is empty. Otherwise, read the SB packet from address 128 + (64 * tail), and then increment tail. If tail equals 62 (the end of the queue), then set tail to 0.

The queue implementation in C is in switchboard/cpp/spsc_queue.h, with care taken to avoid memory ordering hazards, and various cache-oriented optimizations. The queue implementation in Verilog (intended for FPGA-based emulation) can be found in switchboard/verilog/fpga/sb_rx_fpga.sv and switchboard/verilog/fpga/sb_tx_fpga.sv.

License

Apache 2.0

Contributing

switchboard is an open-source project and welcomes contributions. To find out how to contribute to the project, see our Contributing Guidelines.

Issues / Bugs

We use GitHub Issues for tracking requests and bugs.

Project links

Data verified by PyPI on Jul 10, 2026
Data provided by the project maintainers, verified at the time the release was uploaded to PyPI.

Key dates

PyPI data
Data sourced directly from PyPI's database.
  • Released:
Latest release

2 maintainers

PyPI data
Data sourced directly from PyPI's database.
Avatar for aolofsson from gravatar.com aolofsson Avatar for gadfort from gravatar.com gadfort

Credits

Author: Zero ASIC

GitHub Statistics

Data verified by PyPI on Jul 10, 2026
The GitHub source repository was provided by the project maintainers and verified by PyPI at the time of upload. Stars, forks, and open issues/PRs are derived from that repository and have not been independently verified.

License expression

Apache-2.0
View SPDX License List

Requires

Python >=3.10

Provides Extra

test docs

Classifiers

Report project as malware

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

switchboard_hw-0.3.4-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (328.7 kB view details)

Uploaded CPython 3.14tmanylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

switchboard_hw-0.3.4-cp314-cp314t-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl (308.3 kB view details)

Uploaded CPython 3.14tmanylinux: glibc 2.26+ ARM64manylinux: glibc 2.28+ ARM64

switchboard_hw-0.3.4-cp314-cp314t-macosx_11_0_arm64.whl (295.9 kB view details)

Uploaded CPython 3.14tmacOS 11.0+ ARM64

switchboard_hw-0.3.4-cp314-cp314t-macosx_10_15_x86_64.whl (304.9 kB view details)

Uploaded CPython 3.14tmacOS 10.15+ x86-64

switchboard_hw-0.3.4-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (325.9 kB view details)

Uploaded CPython 3.14manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

switchboard_hw-0.3.4-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl (304.0 kB view details)

Uploaded CPython 3.14manylinux: glibc 2.26+ ARM64manylinux: glibc 2.28+ ARM64

switchboard_hw-0.3.4-cp314-cp314-macosx_11_0_arm64.whl (285.5 kB view details)

Uploaded CPython 3.14macOS 11.0+ ARM64

switchboard_hw-0.3.4-cp314-cp314-macosx_10_15_x86_64.whl (295.9 kB view details)

Uploaded CPython 3.14macOS 10.15+ x86-64

switchboard_hw-0.3.4-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (325.8 kB view details)

Uploaded CPython 3.13manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

switchboard_hw-0.3.4-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl (303.1 kB view details)

Uploaded CPython 3.13manylinux: glibc 2.26+ ARM64manylinux: glibc 2.28+ ARM64

switchboard_hw-0.3.4-cp313-cp313-macosx_11_0_arm64.whl (285.0 kB view details)

Uploaded CPython 3.13macOS 11.0+ ARM64

switchboard_hw-0.3.4-cp313-cp313-macosx_10_15_x86_64.whl (295.6 kB view details)

Uploaded CPython 3.13macOS 10.15+ x86-64

switchboard_hw-0.3.4-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (325.7 kB view details)

Uploaded CPython 3.12manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

switchboard_hw-0.3.4-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl (303.2 kB view details)

Uploaded CPython 3.12manylinux: glibc 2.26+ ARM64manylinux: glibc 2.28+ ARM64

switchboard_hw-0.3.4-cp312-cp312-macosx_11_0_arm64.whl (285.0 kB view details)

Uploaded CPython 3.12macOS 11.0+ ARM64

switchboard_hw-0.3.4-cp312-cp312-macosx_10_15_x86_64.whl (295.5 kB view details)

Uploaded CPython 3.12macOS 10.15+ x86-64

switchboard_hw-0.3.4-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (324.5 kB view details)

Uploaded CPython 3.11manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

switchboard_hw-0.3.4-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl (302.5 kB view details)

Uploaded CPython 3.11manylinux: glibc 2.26+ ARM64manylinux: glibc 2.28+ ARM64

switchboard_hw-0.3.4-cp311-cp311-macosx_11_0_arm64.whl (284.3 kB view details)

Uploaded CPython 3.11macOS 11.0+ ARM64

switchboard_hw-0.3.4-cp311-cp311-macosx_10_15_x86_64.whl (293.5 kB view details)

Uploaded CPython 3.11macOS 10.15+ x86-64

switchboard_hw-0.3.4-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (323.3 kB view details)

Uploaded CPython 3.10manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

switchboard_hw-0.3.4-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl (301.2 kB view details)

Uploaded CPython 3.10manylinux: glibc 2.26+ ARM64manylinux: glibc 2.28+ ARM64

switchboard_hw-0.3.4-cp310-cp310-macosx_11_0_arm64.whl (283.3 kB view details)

Uploaded CPython 3.10macOS 11.0+ ARM64

switchboard_hw-0.3.4-cp310-cp310-macosx_10_15_x86_64.whl (292.3 kB view details)

Uploaded CPython 3.10macOS 10.15+ x86-64

File details

Details for the file switchboard_hw-0.3.4-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 5457fac39e0a0581506233729c5f083cdb8ed9b384b03daca2a0f65587adaf5f
MD5 43a19c03c004ffb61ef80d330a04b1c0
BLAKE2b-256 a14d361c95a851f4b6463bf75a657eee05cddbed921d39566dffed000001cc31

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp314-cp314t-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp314-cp314t-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 5e64c814106112f45fc3995ba909778887cdf6251e36708cacd6f587efafad7f
MD5 18e7cbbe3ca7c02bbb99718106a0877d
BLAKE2b-256 fc54c5a4729aca9487019e782614bedced2ce36cbd348a5054658d9f06e3bc9c

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp314-cp314t-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp314-cp314t-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp314-cp314t-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 2a958f51916aa0dce4b6e1401834d7996fe184a3dbcb2b5eb117b22e9719e689
MD5 2acec90bb2e36a37824565fb06660915
BLAKE2b-256 81d5bc1c77ec1955ef079fd0456f5561fe303ee8ca5948cefbbae026b41652a7

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp314-cp314t-macosx_11_0_arm64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp314-cp314t-macosx_10_15_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp314-cp314t-macosx_10_15_x86_64.whl
Algorithm Hash digest
SHA256 35806b33b41635c834fb510841e37c090d680d9ba99169b710bd87f614eb2b46
MD5 058488faa9d53e1c6b9691a2e51ac1bb
BLAKE2b-256 8a54047b2fcad4b8b18d889227fb58792c3653220ecb3f289715bed991db453a

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp314-cp314t-macosx_10_15_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 56335ec0c70e09a4399fbc0f3116929df91c7e207852b96547841d90fb7d37ac
MD5 80cdc3132d04500c51155616ba46b115
BLAKE2b-256 6f536454854641f83b0a90f6dbf3a2cad0ba40da199d68d9cde397b98cd4eb37

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 eea6b2ab76b7711a6c62d9ea5a4520017776142e09a1244e802de113b27203ad
MD5 63da53dfcb8d35b35f9ab5931f12cd5d
BLAKE2b-256 8f27a4951cd4d7d12b5e8e73c9166f461ad98fc48f2d078019816635af2c57cd

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp314-cp314-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp314-cp314-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 99f3cd4695f6236a4fcdb7b8ead3f42ce9a372ed3134250d5f9034dd1870a3cc
MD5 494940ad1e389e1125e5b225d32afac1
BLAKE2b-256 2617e510943faca1d93810618a70743b4dbbd60858c29b6340a49618cda0b2c9

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp314-cp314-macosx_11_0_arm64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp314-cp314-macosx_10_15_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp314-cp314-macosx_10_15_x86_64.whl
Algorithm Hash digest
SHA256 395465766a20d58605929547451b79a3b69e6bdb492ffc43d446c4327e0ef912
MD5 3dec6d4545d0857e94106c38b247dff7
BLAKE2b-256 dc81e4ef7638fc6261cd711f6707ced870ee5d4b3846ba79094399d7e6228e86

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp314-cp314-macosx_10_15_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 4931df04a0068434bfd5d3f0a958623f8aa561f110d656cf141fea768d51a5f9
MD5 218f32173b901bdbba47848b1f2d2a58
BLAKE2b-256 b7f3984a8933b84c378c0637d14b220ddd7487f7a274dede4221777e0c1ffd57

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 12590b510ee5cdb2c39a050b035b6c7fbbe68e3a043491fc4dbee22127016af4
MD5 0fc16933d111cf02132aea9a3d49b64c
BLAKE2b-256 29fa2fd0a1eb60e6f0566c4e350ed678d08d9c092098e5e54b99e43f7c5b9b1a

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp313-cp313-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp313-cp313-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 773dd18fba93d9bdc9452401ee12333e1aec5d4311c89f06e2b0758cd03eda42
MD5 2e0bf11291baa52319b73848df5748d1
BLAKE2b-256 c8d24c166a6bc0ecd7148d42597691cd865ebfc902161c5705253ccd9bc06868

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp313-cp313-macosx_11_0_arm64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp313-cp313-macosx_10_15_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp313-cp313-macosx_10_15_x86_64.whl
Algorithm Hash digest
SHA256 cb99b7650d9746bd6f79851cb09f262a55287cb5fdae64e7e9937e4fea521114
MD5 a892a82b64c90dcbe5679b4db762d267
BLAKE2b-256 e1545ce882e19c650421bde7439363cce134aaee0296e8541cc83b27c31d5c8d

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp313-cp313-macosx_10_15_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 04f35171caa81992e7c51ae6b41ad36e4b2a2a74fb2d91192fa326e93ef793be
MD5 27b85aa45c1aadfef8e592b1f8c335a7
BLAKE2b-256 20ea8638a79f2f5f207bc82de520655577447666b4c54ed6950f28e6d84cb809

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 4c33d15933268c4008c70934377f97ae42598e2321a5c636b430a2862c70fd13
MD5 8c149a501a0fea66c08699f911e02c9c
BLAKE2b-256 31849d7f2251a4b9c65bde39983cc312b9979ca23634604e876b461b231d0dff

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp312-cp312-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp312-cp312-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 679ec45f6b273c6439dfa336254a6955b9d68f1e0896dc56b72e28268afba335
MD5 876d912974231c512e156e3266c01bb2
BLAKE2b-256 100c9f57805b7e7d63e57ac340bd85f01ee9142e8c854426ee45a73f9012b59c

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp312-cp312-macosx_11_0_arm64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp312-cp312-macosx_10_15_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp312-cp312-macosx_10_15_x86_64.whl
Algorithm Hash digest
SHA256 37d5fd753005e714596170b5b7b5f466b787fcaffaae9a312bea94ae1059f33c
MD5 6c0bbe314606be261bdbb6c9230bf1e0
BLAKE2b-256 3e45b163429447862aa84f1ad838398cf9ffab912d1786d3b57066bec7bbe98a

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp312-cp312-macosx_10_15_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 a87dca1209047220c99d6428929155d07987fdba992835d97d1ae36d71df2104
MD5 d069070e6318a2817734263cc9087283
BLAKE2b-256 3027f4c9c7ca2753e122293fa5f0d74747c46bb1413f73ee7ff8741df426148a

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 ca5583eb7b15080f056b762e857bcc11e3349c0d0159812b1f90c60721929532
MD5 44c05890b20c5880f13efad7891d04e3
BLAKE2b-256 03df4ee5b14801eabc5c5aa35b4bee78cf0777a6158a8412955ad7f66a87d54f

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp311-cp311-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp311-cp311-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 754e904235a3bd96a86a66df4d5ab66d3072c645b558cf8a5dd91d0508ea3a15
MD5 e48f288211ee7cb6d0299cee2f57a4e4
BLAKE2b-256 312c4de431203efbbabc5790f908b39ee075f0dbffb2db8d3ac4c9921db896b3

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp311-cp311-macosx_11_0_arm64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp311-cp311-macosx_10_15_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp311-cp311-macosx_10_15_x86_64.whl
Algorithm Hash digest
SHA256 7712f75ac6186e69e4deae5983473266004d69e540efae8c2f7dcb3a9962657f
MD5 3b63952fcab5806dfb3063dd03073667
BLAKE2b-256 39f3dbe54356147a0b855949276aba542fa20b8a56ee90f6862d51a4c4de09d2

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp311-cp311-macosx_10_15_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Algorithm Hash digest
SHA256 6adf9a9f05db4c465a1b17026ffdd118516013cbd8b9afcc361a85b15e0f9146
MD5 903bb66c7d8ff49189a534de87066901
BLAKE2b-256 acec83e805e14b297defafebca46c13d8e7fde50c6f6b04f74a137da9fea72a0

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 30e613ca554a11b6baaa14e4889d96bdea3c421f8bc41643c85b03fc6fe09c14
MD5 7c4224d1ffa32c4e6dc6e3ec63619e27
BLAKE2b-256 5b7a1905d04aea7db0ece4cef17444a52ec5367e7bd19c6a42da6621c7ec194c

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp310-cp310-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp310-cp310-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 fbb25c51fe0ebd604ff8c9940bcc9da5e94f06153ebb65a740b5a7b2cf958e9a
MD5 2932a180b4415b0f80d0aa708f417e44
BLAKE2b-256 53b5deddf822913e7e19d45b328753eeda4b278ede25bc13096630d95ae0cb85

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp310-cp310-macosx_11_0_arm64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file switchboard_hw-0.3.4-cp310-cp310-macosx_10_15_x86_64.whl.

File metadata

File hashes

Hashes for switchboard_hw-0.3.4-cp310-cp310-macosx_10_15_x86_64.whl
Algorithm Hash digest
SHA256 0de9228a195739a91459c082f1ba38150d41e143b99f9cdb3f6f012b5da2e3a3
MD5 16103e888e7e89d0a7c5f4245921bcde
BLAKE2b-256 1378e36b910561b1c426432a7b139c6493c3f66776875a626295a46424e005f5

See more details on using hashes here.

Provenance

The following attestation bundles were made for switchboard_hw-0.3.4-cp310-cp310-macosx_10_15_x86_64.whl:

Publisher: wheels.yml on zeroasiccorp/switchboard

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page