mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Way for platforms to alter built-in serial ports
Date: Thu, 30 Sep 2004 10:14:00 -0600	[thread overview]
Message-ID: <200409301014.00725.bjorn.helgaas@hp.com> (raw)

> What I propose is a way for the arch to provide it's own table along
> with the size of it via a function call. It's optional, based on a
> #ifdef defined by the arch in it's asm/serial.h. The only remaining
> tricky point is the fact that you used to size your static array of
> UART's based on the size of the table. So with my path, an arch
> that defines ARCH_HAS_GET_LEGACY_SERIAL_PORTS is supposed to provide
> both the new get_legacy_serial_ports() function, but also to define
> UART_NR to something sensible. I hope one day, we'll be able to
> convert 8250 to more dynamic allocation though.

This looks like a reasonable short-term fix, but I think the whole
serial8250_isa_init_ports() should go away.  I like dwmw2's suggestion
of an 8250_platform.c that could use register_serial() for each port
in some platform-supplied old_serial_port[] table, which is probably
what you mean by moving to a more dynamic allocation.

AFAICS, the only reason for doing serial8250_isa_init_ports() early
is for early serial consoles, and I think those should be done along
the lines of this:
 http://www.ussg.iu.edu/hypermail/linux/kernel/0409.1/1034.html
where the platform can specify a device by its MMIO or IO port address,
and we automatically switch to the corresponding ttyS device later.

             reply	other threads:[~2004-09-30 16:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 16:14 Bjorn Helgaas [this message]
2004-09-30 23:53 ` Benjamin Herrenschmidt
2004-10-01 14:58   ` Bjorn Helgaas
2004-10-02  6:45     ` Benjamin Herrenschmidt
2004-10-06  7:32     ` Russell King
2004-10-06 19:54       ` Bjorn Helgaas
2004-10-08 19:49         ` Bjorn Helgaas
2004-10-06  7:29 ` Russell King
2004-10-06 19:47   ` Bjorn Helgaas
2004-11-01 17:15   ` David Woodhouse
2004-11-02 16:39     ` Bjorn Helgaas
2004-11-03  7:43       ` Russell King
2004-11-03 12:07         ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-09-30  8:50 Benjamin Herrenschmidt
2004-10-06  7:26 ` Russell King
2004-10-06  8:15   ` Benjamin Herrenschmidt
2004-10-06  9:07   ` Benjamin Herrenschmidt

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=200409301014.00725.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=benh@kernel.crashing.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®