summaryrefslogtreecommitdiffstats
path: root/doc/driver-model/UDM-video.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/driver-model/UDM-video.txt')
-rw-r--r--doc/driver-model/UDM-video.txt24
1 files changed, 12 insertions, 12 deletions
diff --git a/doc/driver-model/UDM-video.txt b/doc/driver-model/UDM-video.txt
index 342aeee485..e67e9e41b4 100644
--- a/doc/driver-model/UDM-video.txt
+++ b/doc/driver-model/UDM-video.txt
@@ -36,39 +36,39 @@ static struct stdio_device_ops handling the character output.
III) Analysis of in-tree drivers
--------------------------------
- 1) arch/powerpc/cpu/mpc8xx/video.c
- ----------------------------------
+ arch/powerpc/cpu/mpc8xx/video.c
+ -------------------------------
This driver copies the cfb_console [ see drivers/video/cfb_console.c ]
approach and acts only as a STDIO device. Therefore there are currently two
possible approaches, first being the conversion of this driver to usual STDIO
device and second, long-term one, being conversion of this driver to video
driver that provides console.
- 2) arch/x86/lib/video.c
- -----------------------
+ arch/x86/lib/video.c
+ --------------------
This driver registers two separate STDIO devices and should be therefore
converted as such.
- 3) board/bf527-ezkit/video.c
- ----------------------------
+ board/bf527-ezkit/video.c
+ -------------------------
This driver seems bogus as it behaves as STDIO device, but provides no input
or output capabilities. It relies on DEV_EXT_VIDEO, which is no longer in use
or present otherwise than as a dead code/define.
- 4) board/bf533-stamp/video.c
- ----------------------------
+ board/bf533-stamp/video.c
+ -------------------------
This driver seems bogus as it behaves as STDIO device, but provides no input
or output capabilities. It relies on DEV_EXT_VIDEO, which is no longer in use
or present otherwise than as a dead code/define.
- 5) board/bf548-ezkit/video.c
- ----------------------------
+ board/bf548-ezkit/video.c
+ -------------------------
This driver seems bogus as it behaves as STDIO device, but provides no input
or output capabilities. It relies on DEV_EXT_VIDEO, which is no longer in use
or present otherwise than as a dead code/define.
- 6) board/cm-bf548/video.c
- ----------------------------
+ board/cm-bf548/video.c
+ ----------------------
This driver seems bogus as it behaves as STDIO device, but provides no input
or output capabilities. It relies on DEV_EXT_VIDEO, which is no longer in use
or present otherwise than as a dead code/define.
OpenPOWER on IntegriCloud