Release v0.5.3

Release Notes

🐱 v0.5.3

Migrate the actual travis-ci build pipeline to github actions

• 🕵️ Fixes

  • fix the release description generation.

Release v0.5.2

Release Notes

🐱 v0.5.2

Migrate the actual travis-ci build pipeline to github actions

• 🕵️ Fixes

  • fix the version replacements in the github action.

🐱 v0.5.1

Migrate the actual travis-ci build pipeline to github actions

• 🔧 Maintenance

  Updating the minor version to validate the pipeline config end-2-end

🐱 v0.5.0

Enable the usage of the log crate to be used as generic logger facade in other crates to use the static logger/console in this crate.

• 💡 Features

  • use the log crate to provide a generic logger facade.

🍑 v0.4.1

• 🕵️ Fixes

  • require the actual structure to be used as Console to implement Send and Sync as this is a requirement of the Singleton now.

🍑 v0.4.0

• 🔧 Maintenance

  • using a better pipeline setup for build and release.
  • using the core::fmt::Write as trait bound for anything that might act as a console output instead of a custom trait.
  • as the Write trait requires the structure to be mutable when writing to the output channel the console operations are blocking operations -> thus requiring atomic operations to be possible -> thus requiring the MMU to be activated before using the console abstraction is possible. Otherwise execution will hang as atomics are not able to be processed by the CPU.

🍎 v0.3.1

• 💡 Features

• 🕵️ Fixes

  • writing to the console is no longer a blocking operation. This allows console outputs from within Interrupt handlers without possible deadlocks. However, concurrent console writes may lead to "garbage" on the console output (terminal)

Release v0.5.1

Release Notes

🐱 v0.5.1

Migrate the actual travis-ci build pipeline to github actions

• 🔧 Maintenance

  Updating the minor version to validate the pipeline config end-2-end

🐱 v0.5.0

Enable the usage of the log crate to be used as generic logger facade in other crates to use the static logger/console in this crate.

• 💡 Features

  • use the log crate to provide a generic logger facade.

🍑 v0.4.1

• 🕵️ Fixes

  • require the actual structure to be used as Console to implement Send and Sync as this is a requirement of the Singleton now.

🍑 v0.4.0

• 🔧 Maintenance

  • using a better pipeline setup for build and release.
  • using the core::fmt::Write as trait bound for anything that might act as a console output instead of a custom trait.
  • as the Write trait requires the structure to be mutable when writing to the output channel the console operations are blocking operations -> thus requiring atomic operations to be possible -> thus requiring the MMU to be activated before using the console abstraction is possible. Otherwise execution will hang as atomics are not able to be processed by the CPU.

🍎 v0.3.1

• 💡 Features

• 🕵️ Fixes

  • writing to the console is no longer a blocking operation. This allows console outputs from within Interrupt handlers without possible deadlocks. However, concurrent console writes may lead to "garbage" on the console output (terminal)

Release v0.5.0

Release Notes

🐱 v0.5.0

Enable the usage of the log crate to be used as generic logger facade in other crates to use the static logger/console in this crate.

• 💡 Features

  • use the log crate to provide a generic logger facade.

🍑 v0.4.1

• 🕵️ Fixes

  • require the actual structure to be used as Console to implement Send and Sync as this is a requirement of the Singleton now.

🍑 v0.4.0

• 🔧 Maintenance

  • using a better pipeline setup for build and release.
  • using the core::fmt::Write as trait bound for anything that might act as a console output instead of a custom trait.
  • as the Write trait requires the structure to be mutable when writing to the output channel the console operations are blocking operations -> thus requiring atomic operations to be possible -> thus requiring the MMU to be activated before using the console abstraction is possible. Otherwise execution will hang as atomics are not able to be processed by the CPU.

🍎 v0.3.1

• 💡 Features

• 🕵️ Fixes

  • writing to the console is no longer a blocking operation. This allows console outputs from within Interrupt handlers without possible deadlocks. However, concurrent console writes may lead to "garbage" on the console output (terminal)

v0.4.1

Release Notes

🍑 v0.4.1

• 🕵️ Fixes

  • require the actual structure to be used as Console to implement Send and Sync as this is a requirement of the Singleton now.

v0.4.0

Release Notes

🍑 v0.4.0

• 🔧 Maintenance

  • using a better pipeline setup for build and release.
  • using the core::fmt::Write as trait bound for anything that might act as a console output instead of a custom trait.
  • as the Write trait requires the structure to be mutable when writing to the output channel the console operations are blocking operations -> thus requiring atomic operations to be possible -> thus requiring the MMU to be activated before using the console abstraction is possible. Otherwise execution will hang as atomics are not able to be processed by the CPU.

🍎 v0.3.1

• 💡 Features

• 🕵️ Fixes

  • writing to the console is no longer a blocking operation. This allows console outputs from within Interrupt handlers without possible deadlocks. However, concurrent console writes may lead to "garbage" on the console output (terminal)

v0.3.2

Release Notes

🕵️ Fixes

• use cargo make to stabilize cross-platform builds

v0.3.1

Release Notes

🍎 v0.3.1

• 🕵️ Fixes

  • writing to the console is no longer a blocking operation. This allows console outputs from within
    Interrupt handlers without possible deadlocks. However, concurrent console writes may lead to "garbage"
    on the console output (terminal)

Enable aarch64 build target architecture

Release Notes

• Enable aarch64 build target architecture
• Remove with_allocator feature and the direct dependency to ruspiro_allocator. User of this crate shall provide the custom allocator on their own, even if it is the ruspiro one.

RusPiRo allocator rust_oom fix

Release notes

When using this crate with with_allocator feature the existing function in the used ruspiro-allocator crate rust_oom is now properly exported to successfully link the final binary crate.