diff options
author | Masahiro Yamada <yamada.m@jp.panasonic.com> | 2013-09-24 10:32:04 +0900 |
---|---|---|
committer | Tom Rini <trini@ti.com> | 2013-11-08 15:25:12 -0500 |
commit | 566c6e43700c4f87408488aa7fef28fa37e8d455 (patch) | |
tree | 386a10c1c8f1fd5deb9298efb08fb5d1749f255e /doc/driver-model/UDM-video.txt | |
parent | 39d9abfa23c0d9fa7034c9fd01124be98eb92c4d (diff) |
cosmetic: doc: driver-model: Do not number driver lists
Everytime a dead driver is removed from the list,
we must re-number. This is a painful task.
Try
git show e53232250 -- doc/driver-model/UDM-serial.txt
git show 6f62f4207 -- doc/driver-model/UDM-serial.txt
git show b9f4bc34a -- doc/driver-model/UDM-serial.txt
to see what I mean.
Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Diffstat (limited to 'doc/driver-model/UDM-video.txt')
-rw-r--r-- | doc/driver-model/UDM-video.txt | 24 |
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. |