summaryrefslogtreecommitdiffstats
path: root/drivers/char/vt.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2009-09-15 17:04:38 -0700
committerDavid S. Miller <davem@davemloft.net>2009-09-15 17:04:38 -0700
commit09d3f3f0e02c8a900d076c302c5c02227f33572d (patch)
tree4114d7de68bc4579b03b8b5ac81483836412fd96 /drivers/char/vt.c
parent0cb583fd2862f19ea88b02eb307d11c09e51e2f8 (diff)
downloadkernel-crypto-09d3f3f0e02c8a900d076c302c5c02227f33572d.tar.gz
kernel-crypto-09d3f3f0e02c8a900d076c302c5c02227f33572d.tar.xz
kernel-crypto-09d3f3f0e02c8a900d076c302c5c02227f33572d.zip
sparc: Kill PROM console driver.
Many years ago when this driver was written, it had a use, but these days it's nothing but trouble and distributions should not enable it in any situation. Pretty much every console device a sparc machine could see has a bonafide real driver, making the PROM console hack unnecessary. If any new device shows up, we should write a driver instead of depending upon this crutch to save us. We've been able to take care of this even when no chip documentation exists (sunxvr500, sunxvr2500) so there are no excuses. Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/char/vt.c')
-rw-r--r--drivers/char/vt.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/char/vt.c b/drivers/char/vt.c
index 404f4c1ee43..6aa88f50b03 100644
--- a/drivers/char/vt.c
+++ b/drivers/char/vt.c
@@ -2948,9 +2948,6 @@ int __init vty_init(const struct file_operations *console_fops)
panic("Couldn't register console driver\n");
kbd_init();
console_map_init();
-#ifdef CONFIG_PROM_CONSOLE
- prom_con_init();
-#endif
#ifdef CONFIG_MDA_CONSOLE
mda_console_init();
#endif