All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: RFC: run-time defining serial ports
Date: Fri, 13 Jul 2001 13:43:25 +0200	[thread overview]
Message-ID: <20010713134324.D1378@bacchus.dhis.org> (raw)
In-Reply-To: <3B4E45D9.8DBE84E7@mvista.com>; from jsun@mvista.com on Thu, Jul 12, 2001 at 05:50:33PM -0700

On Thu, Jul 12, 2001 at 05:50:33PM -0700, Jun Sun wrote:

> 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.

It's needed; I have machines here with upto 11 serial interfaces on a lowly
R4700 box; Origins may have _many_ more.

> A by-product of this arrangement is that you can configure a kernel for
> multiple machines.
> 
> What do you think?

  Ralf

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-13  0:50 RFC: run-time defining serial ports Jun Sun
2001-07-13 11:43 ` Ralf Baechle [this message]
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=20010713134324.D1378@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=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 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.