From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org, linux-serial@vger.kernel.org
Subject: Rename Sibyte duart devices?
Date: Mon, 3 Dec 2007 13:08:18 +0000 [thread overview]
Message-ID: <20071203130818.GA6466@linux-mips.org> (raw)
Devices created by udev have been named duart? instead of the common
ttyS?. This is a nuisance because it requires changes to all sorts of
config files such as /etc/inittab, /etc/securetty etc. to work. I
suggest to kill the problem by the root by something like the below
patch. Comments?
Ralf
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
drivers/serial/sb1250-duart.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/serial/sb1250-duart.c b/drivers/serial/sb1250-duart.c
index 2d6c08b..0defbd6 100644
--- a/drivers/serial/sb1250-duart.c
+++ b/drivers/serial/sb1250-duart.c
@@ -897,7 +897,7 @@ static int __init sbd_console_setup(struct console *co, char *options)
static struct uart_driver sbd_reg;
static struct console sbd_console = {
- .name = "duart",
+ .name = "ttyS",
.write = sbd_console_write,
.device = uart_console_device,
.setup = sbd_console_setup,
@@ -925,7 +925,7 @@ console_initcall(sbd_serial_console_init);
static struct uart_driver sbd_reg = {
.owner = THIS_MODULE,
.driver_name = "serial",
- .dev_name = "duart",
+ .dev_name = "ttyS",
.major = TTY_MAJOR,
.minor = SB1250_DUART_MINOR_BASE,
.nr = DUART_MAX_CHIP * DUART_MAX_SIDE,
next reply other threads:[~2007-12-03 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 13:08 Ralf Baechle [this message]
2007-12-03 14:14 ` Rename Sibyte duart devices? Thiemo Seufer
2007-12-03 14:30 ` Maciej W. Rozycki
2007-12-03 21:41 ` Kaz Kylheku
2007-12-03 21:41 ` Kaz Kylheku
-- strict thread matches above, loose matches on Subject: below --
2007-12-03 13:05 Ralf Baechle
2007-12-03 14:18 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071203130818.GA6466@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.