Struct SdioClient

pub struct SdioClient<'fs> { /* private fields */ }

Handle all “SDIO” traffic to/from the device.

“SDIO” is actually handled by a pair of ports, and isn’t real SDIO that’s happening over like a real chip. So if you came hear searching for real SDIO code, I’m sorry. Nintendo calls this SDIO, and does it over a pair of TCP ports. You came to the wrong place.

The two ports that make up an SDIO Client are the “control” port, where clients can send “printf” debug logs, as well as requests to read/write data on the other stream. The other port called the “data” port is where the underlying data is actually sent from one side to another.

Implementations

impl<'fs> SdioClient<'fs>

pub async fn connect( mion_ip: Ipv4Addr, control_port: Option<u16>, data_port: Option<u16>, connect_timeout: Option<Duration>, host_filesystem: &'fs HostFilesystem, no_load_bearing_sleep: bool, ) -> Result<Self, CatBridgeError>

Connect to a MION getting ready to service SDIO requests.

Errors

If we cannot connect successfully to the device within the specified timeout. NOTE: the timeout applies uniquely to each connection. However we do attempt to connect concurrently so you shouldn’t need to wait for your specified timeout twice.

pub async fn serve(self) -> Result<(), CatBridgeError>

Actually end up serving SDIO Traffic to a CAT-DEV, or other SDIO type of device.

I know it may be unusual to have a client called “serve”, but this is expected behaviour, although we initiate the connection (because the OS hasn’t started up yet), we do end up acting in a server model.

Errors

If we run into any errors actually servicing a device we are actively connected too.

impl SdioClient<'static>

pub async fn serve_concurrently(self) -> Result<(), CatBridgeError>

Actually end up serving SDIO Traffic to a CAT-DEV, or other SDIO type of device.

I know it may be unusual to have a client called “serve”, but this is expected behaviour, although we initiate the connection (because the OS hasn’t started up yet), we do end up acting in a server model.

This server is capable of receiving multiple requests concurrently. Sending over the data port is still single-threaded, because the protocol inherently doesn’t allow for it, but you can at least service control requests while waiting on the data-stream with this server.

Errors

If we run into any errors actually servicing a device we are actively connected too.

Trait Implementations

impl<'fs> Debug for SdioClient<'fs>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.