readme: Drop crate feature list

The feature lists are covered in the crate docstrings now, and the crate
READMEs link to that source as well. Drop the list here so we don't have
to worry about keeping them in sync.

Author: nicholasbishop

README.md

@@ -30,23 +30,9 @@ Check out [the UEFI application template](template) for a quick start.
 
 This project contains multiple sub-crates:
 
-- `uefi` (top directory): defines the standard UEFI tables / interfaces.
+- `uefi`: defines the standard UEFI tables / interfaces.
   The objective is to stay unopinionated and safely wrap most interfaces.
 
-  **Optional crate features:**
-
-  - `alloc`: Enables functionality requiring the `alloc` crate from the Rust standard library.
-    - For example, this allows many convenient `uefi-rs` functions to operate on heap data (`Box`).
-    - It is up to the user to provide a `#[global_allocator]`.
-  - `global_allocator`: implements a `#[global_allocator]` using UEFI functions.
-    - This allows you to use all abstractions from the `alloc` crate from the Rust standard library
-      during runtime. Hence, `Vec`, `Box`, etc. will be able to allocate memory.
-      **This is optional**, so you can provide a custom `#[global_allocator]` as well.
-    - There's no guarantee of the efficiency of UEFI's allocator.
-  - `logger`: logging implementation for the standard [`log`] crate.
-    - Prints output to UEFI console.
-    - No buffering is done: this is not a high-performance logger.
-
 - `uefi-macros`: procedural macros that are used to derive some traits in `uefi`.
 
 - `uefi-services`: provides a panic handler, and initializes the `alloc` / `logger` features.