Merge branch 'for-next/misc'

2 files changed, 3 insertions, 5 deletions

diff --git a/Documentation/user/framebuffer.rst b/Documentation/user/framebuffer.rst
index 8b95ad6b87..d17df822f2 100644
--- a/Documentation/user/framebuffer.rst
+++ b/Documentation/user/framebuffer.rst
@@ -4,9 +4,7 @@ Framebuffer support
 Framebuffer splash screen
 -------------------------
 
-barebox supports BMP and PNG graphics using the :ref:`command_splash` command. barebox
-currently has no support for backlights, so unless there is a board specific enable
-hook for enabling a display it must be done manually with a script. Since barebox
+barebox supports BMP and PNG graphics using the :ref:`command_splash` command. Since barebox
 has nothing useful to show on the framebuffer it doesn't enable it during startup.
 A framebuffer can be enabled with the ``enable`` parameter of the framebuffer device:
 
@@ -39,7 +37,7 @@ A typical script to enable the framebuffer could look like this:
   # wait for signals to become stable
   msleep 100
 
-  # finally enable backlight
+  # finally enable backlight manually if no driver exists
   gpio_direction_output 42 1
 
 Framebuffer console
diff --git a/Documentation/user/virtio.rst b/Documentation/user/virtio.rst
index dde47d5f82..d944fa4821 100644
--- a/Documentation/user/virtio.rst
+++ b/Documentation/user/virtio.rst
@@ -35,7 +35,7 @@ queues configuration and buffer transfers are nearly identical. Both MMIO
 and non-legacy PCI are supported in barebox.
 
 The VirtIO spec defines a lots of VirtIO device types, however at present only
-block, console, input and RNG devices are supported.
+block, network, console, input and RNG devices are supported.
 
 Build Instructions
 ------------------