You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<spanclass="maintainers">Maintained by [@IsaacWoods](https://github.com/IsaacWoods), [@phip1611](https://github.com/phip1611), [@robert-w-gries](https://github.com/robert-w-gries), [@ahmedcharles](https://github.com/ahmedcharles), and [@Caduser2020](https://github.com/Caduser2020)</span>
82
+
81
83
The `multiboot2` crate provides abstraction types for the multiboot information structure (MBI) of multiboot2
82
84
bootloaders. The latest release of the `multiboot2`-crate is now `v.0.13.2` (was `v0.13.1`). It contains minor
83
85
improvements, such as that `TagType` implements `Ord`.
<spanclass="maintainers">Maintained by [@IsaacWoods](https://github.com/IsaacWoods), [@phip1611](https://github.com/phip1611), [@robert-w-gries](https://github.com/robert-w-gries), [@ahmedcharles](https://github.com/ahmedcharles), and [@Caduser2020](https://github.com/Caduser2020)</span>
90
+
88
91
The `multiboot2-header` crate provides abstraction types for Multiboot2 headers and a builder struct to construct such
89
92
headers. The latest release of the `multiboot2-header`-crate is now `v0.2.0` (was `v0.1.0`). The changes include a
90
93
bugfix that prevented the usage in `no_std` contexts. Furthermore, overall code quality was improved. The internal CI
@@ -103,6 +106,8 @@ Thanks to [@hawkw](https://github.com/hawkw) for this contribution!
103
106
104
107
### [`xhci`](https://github.com/rust-osdev/xhci)
105
108
109
+
<spanclass="maintainers">Maintained by [@toku-sa-n](https://github.com/toku-sa-n)</span>
110
+
106
111
The `xhci` crate provides types of xHCI structires, such as Registers and TRBs.
107
112
108
113
In this month, we released a new version 0.8.3 which includes [a bug fix](https://github.com/rust-osdev/xhci/pull/132) reported and committed by [@Yuna-Tomi](https://github.com/Yuna-Tomi). The bug was that `EventRingDequeuePointerRegister::event_ring_dequeue_pointer()` did not return the correct address. Thanks for the contribution!.
0 commit comments