From: Jun Sun <jsun@mvista.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Ralf Baechle <ralf@linux-mips.org>,
Linux/MIPS Development <linux-mips@linux-mips.org>,
jsun@mvista.com
Subject: Re: [patch] Incorrect mapping of serial ports to lines
Date: Tue, 29 Jun 2004 15:13:13 -0700 [thread overview]
Message-ID: <20040629151313.E6498@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0406291546480.31801@jurand.ds.pg.gda.pl>; from macro@linux-mips.org on Tue, Jun 29, 2004 at 03:49:11PM +0200
On Tue, Jun 29, 2004 at 03:49:11PM +0200, Maciej W. Rozycki wrote:
> On Tue, 29 Jun 2004, Geert Uytterhoeven wrote:
>
> > The NEC DDB Vrc-5074 (and probably the other DDB variants as well) has one
> > serial port in the Nile 4 host bridge, and 2 serial ports in the Super I/O.
> >
> > To me it sounds the most logical if the one in the Nile 4 is ttyS0.
>
> Then we need to find a way to make the order configurable somehow.
This is why I favor run-time serial port configuration. My view
(maybe a little dramatic) is to remove all static serial port definition
and push them into board setup routine. asm/serial.h only needs
to define the number serial lines, which itself could be configurable.
Jun
next prev parent reply other threads:[~2004-06-29 22:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 13:25 [patch] Incorrect mapping of serial ports to lines Maciej W. Rozycki
2004-06-28 23:59 ` Ralf Baechle
2004-06-29 11:57 ` Maciej W. Rozycki
2004-06-29 12:09 ` Geert Uytterhoeven
2004-06-29 13:49 ` Maciej W. Rozycki
2004-06-29 15:03 ` Ralf Baechle
2004-07-02 15:09 ` Maciej W. Rozycki
2004-06-29 22:13 ` Jun Sun [this message]
2004-06-29 22:43 ` Maciej W. Rozycki
2004-06-30 8:07 ` Geert Uytterhoeven
2004-06-30 12:10 ` Maciej W. Rozycki
2004-06-29 22:49 ` Ralf Baechle
2004-06-30 0:15 ` Jun Sun
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=20040629151313.E6498@mvista.com \
--to=jsun@mvista.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.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.