The change log for the Rust[socketcan](https://crates.io/crates/socketcan) library.

- Added a number of netlink commands to modify the CAN interface parameters. including: setting the bitrate and (for FD) setting the data bitrate, setting control modes, manually restarting the interface, and setting the automatic restart delay time.

-[PR#50](https://github.com/socketcan-rs/socketcan-rs/pull/50) Add set_bitrate method

-[PR#45](https://github.com/socketcan-rs/socketcan-rs/pull/45) Dump handles extended IDs

-[PR#44](https://github.com/socketcan-rs/socketcan-rs/pull/44) Fix clippy warnings

-[PR#43](https://github.com/socketcan-rs/socketcan-rs/pull/43) Implement AsPtr for CanAnyFrame

- Support for Rust async/await

[package]

name ="socketcan"

version ="3.1.0-pre.0"

version ="3.1.0"

edition ="2021"

rust-version ="1.65"

authors = [

This will primarily add support for increased Netlink functionality to do things like set the bitrate on the interface, set control modes, restart the inteface, etc.

Version 3.0 adds integrated support for async/await, with the most popular runtimes,_tokio, async-std_, and_smol_. To get started we have already merged the[tokio-socketcan](https://github.com/oefd/tokio-socketcan) crate into this one and implemented`async-io`.

Unfortunaly this required a minor breaking change to the existing API, so we bumped the version to 3.0.

The async support is optional, and can be enabled with a feature for the target runtime:`tokio`,`async-std`, or`smol`.

Additional implementation of the netlink control of the CAN interface was added in v3.1 allws an application to do things like set the bitrate on the interface, set control modes, restart the inteface, etc.

- Added netlink functionality:

- Set the bitrate

- Set the bitrate[PR#50](https://github.com/socketcan-rs/socketcan-rs/pull/50), and the FD data bitrate

- Set the control modes (Loopback, Listen-Only, etc)

- Set automatic restart delay time

- Manual restart

-[PR#45](https://github.com/socketcan-rs/socketcan-rs/pull/45) Dump handles extended IDs

-[PR#44](https://github.com/socketcan-rs/socketcan-rs/pull/44) Fix clippy warnings

-[PR#43](https://github.com/socketcan-rs/socketcan-rs/pull/43) Implement AsPtr for CanAnyFrame

- Added cargo build features for`tokio` or`async-io`.

- Also created specific build features for`async-std` and`smol` which just bring in the`async-io` module and alias the module name to`async-std` or`smol`, respectively, and build examples for each.

- Made`CanAddr` pulic and added functions to help interact with low-level sockaddr types. Sockets can now be opened with an address.

- Can create an`Error` directly from a`CanErrorFrame` or`std::io::ErrorKind`.

-[#46](https://github.com/socketcan-rs/socketcan-rs/issues/46) Applications can create error frames:

-`CanErrorFrame::new()` now works.

-`CanErrorFrame::new_error()` is similar but more intuitive using a raw ID word.

-`From<CanError> for CanErrorFrame` to create an error frame from a`CanError`.

- Added`Frame::from_raw_id()` and`Frame::remote_from_raw_id()`

- Bumped MSRV to 1.65.0

A number of items still did notmakei into a release. These will be added in v3.x, coming soon.

A number of items still did notmake it into a release. These will be added in v3.x, coming soon.

- Issue[#22](https://github.com/socketcan-rs/socketcan-rs/issues/22) Timestamps, including optional hardware timestamps

- Issue[#32](https://github.com/socketcan-rs/socketcan-rs/issues/32)Better coverage ofthe Netlink APItomanipulatetheCAN interfaces programatically.

- Issue[#32](https://github.com/socketcan-rs/socketcan-rs/issues/32)A number ofimportant netlink commands were added in v3.1, particularly the abilitytoset bitrates, resettheinterface, and set control modes. But the implementation is still incomplete, particularly in regard t

- Better documentation. This README will be expanded with basic usage information, along with better doc comments, and perhaps creation of the wiki