-
Notifications
You must be signed in to change notification settings - Fork 447
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: smoltcp-rs/smoltcp
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 7d54157e77b2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: smoltcp-rs/smoltcp
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 97499ac280cd
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 3 commits
- 13 files changed
- 1 contributor
Commits on Jul 23, 2017
-
Move macros into their own module.
This allows us to use `enum_with_unknown` in `phy`.
Configuration menu - View commit details
-
Copy full SHA for f5a3785 - Browse repository at this point
Copy the full SHA f5a3785View commit details -
Inject the current timestamp into Device::{transmit,receive}.
Various parts of smoltcp require an arrow of time; a monotonically increasing timestamp. Most obviously this is TCP sockets, but the tracer and the pcap writer devices also benefit from having timestamps. There are a few ways this could be implemented: 1. using a static Cell, global for the entire smoltcp crate; 2. using a static method on Device; 3. using an instance method on Device; 4. passing the current timestamp into *Interface::poll. The first two options are undesirable because they create a notion of global clock, and interfere e.g. with mocking. The third option is undesirable because not all devices are inherently tied to a particular clock, e.g. a loopback device isn't. Therefore, the timestamp is injected into both sockets and devices through the *Interface::poll method.
Configuration menu - View commit details
-
Copy full SHA for 3a656c1 - Browse repository at this point
Copy the full SHA 3a656c1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 97499ac - Browse repository at this point
Copy the full SHA 97499acView commit details
There are no files selected for viewing