From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: "Kilau, Scott" <Scott_Kilau@digi.com>, Greg KH <greg@kroah.com>,
Greg.Chandler@wellsfargo.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: kernel oops with extended serial stuff turned on...
Date: Thu, 19 Oct 2006 14:14:16 +0100 [thread overview]
Message-ID: <1161263657.17335.46.camel@localhost.localdomain> (raw)
In-Reply-To: <45373F2F.90906@gmail.com>
Ar Iau, 2006-10-19 am 11:02 +0200, ysgrifennodd Jiri Slaby:
> drivers/char/mxser.c: mxvar_sdriver->name = "ttyM";
> drivers/char/isicom.c: isicom_normal->name = "ttyM";
mxser should be ttyMI 0...127
> drivers/char/amiserial.c: serial_driver->name = "ttyS";
> drivers/char/serial167.c: cy_serial_driver->name = "ttyS";
> drivers/char/vme_scc.c: scc_driver->name = "ttyS";
Different platform specific drivers - OK
> drivers/char/istallion.c:static char *stli_serialname = "ttyE";
> drivers/char/stallion.c: stl_serial->name = "ttyE";
E is assigned to stallion so both seem to share it
> drivers/char/vt.c: console_driver->name = "tty";
> drivers/char/viocons.c: viotty_driver->name = "tty";
These are correct (different platforms)
Alan
next prev parent reply other threads:[~2006-10-19 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 22:35 kernel oops with extended serial stuff turned on Kilau, Scott
2006-10-18 23:09 ` Greg KH
2006-10-19 0:20 ` Kilau, Scott
2006-10-19 9:02 ` Jiri Slaby
2006-10-19 9:42 ` Jiri Slaby
2006-10-19 10:58 ` Kilau, Scott
2006-10-19 11:01 ` Jiri Slaby
2006-10-19 13:14 ` Alan Cox [this message]
2006-10-19 12:00 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 21:16 Kilau, Scott
2006-10-18 21:21 ` Greg KH
2006-10-18 21:07 Greg.Chandler
2006-10-18 20:32 Kilau, Scott
2006-10-18 17:51 Greg.Chandler
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=1161263657.17335.46.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Greg.Chandler@wellsfargo.com \
--cc=Scott_Kilau@digi.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@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.