Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: linux-mips@oss.sgi.com
Subject: RFC: run-time defining serial ports
Date: Thu, 12 Jul 2001 17:50:33 -0700	[thread overview]
Message-ID: <3B4E45D9.8DBE84E7@mvista.com> (raw)


As more and more boards are added to Linux-mips tree, many places are getting
crowdier and uglier, including serial.h.  The same thing is true for PPC and
other architectures.

It turns out an easy solution is to let every board sets the serial port
definitions at run-time through calling early_serial_setup() routine.

An easy fix for now is to give a default table size when no serial definition
is given, which at least reserves some slots in the rs_table array.  See the
patch below.

A better solution is probably to provide a config option to define the serial
table size.

A by-product of this arrangement is that you can configure a kernel for
multiple machines.

What do you think?

Jun

diff -Nru include/asm-mips/serial.h.orig include/asm-mips/serial.h
--- include/asm-mips/serial.h.orig      Wed May 16 15:58:29 2001
+++ include/asm-mips/serial.h   Thu Jul 12 17:06:05 2001
@@ -271,3 +271,6 @@
        AU1000_SERIAL_PORT_DEFNS        \
        DDB5477_SERIAL_PORT_DEFNS
 
+#ifnef SERIAL_PORT_DFNS
+#define RS_TABLE_SIZE          4
+#endif

             reply	other threads:[~2001-07-13  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-13  0:50 Jun Sun [this message]
2001-07-13 11:43 ` RFC: run-time defining serial ports Ralf Baechle
2001-07-13 14:20 ` Marc Karasek
2001-07-13 14:48   ` Gleb O. Raiko

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=3B4E45D9.8DBE84E7@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox