All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Way for platforms to alter built-in serial ports
Date: Wed, 6 Oct 2004 13:54:15 -0600	[thread overview]
Message-ID: <200410061354.15746.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20041006083249.C18379@flint.arm.linux.org.uk>

On Wednesday 06 October 2004 1:32 am, Russell King wrote:
> On Fri, Oct 01, 2004 at 08:58:27AM -0600, Bjorn Helgaas wrote:
> > My main point is that I think the early init stuff (i.e.,
> > serial8250_isa_init_ports()) should go away, so we don't have the
> > dichotomy of having the compiled-in stuff handled differently than
> > the run-time enumerated stuff.
> 
> You're always going to have this.  For instance, the standard ISA serial
> ports may not show up in any "enumerated stuff" on an x86 box - and x86
> people expect that the port at 0x3f8 is ttyS0, 2f8 is ttyS1 etc.
> 
> Change that order and they'll scream at you.

I don't forsee any order changing.  I would expect to use link
ordering so all the 8250_platform ports are registered first, then
all the 8250_acpi, then all the 8250_pci.

The order WOULD change in some cases on ia64, because we'd get rid
of the current wierdness where the device in the HCDP/PCDP firmware
table always becomes ttyS0, regardless of where it lives.  This
would be an improvement, though, because the devices would stop
changing names just because you selected a different firmware
console.

> See my previous mail why this doesn't work - x86 serial console
> requirements.
> 
> I think you'll do better to discuss this problem with Alan so that
> he can change his (and maybe others) points of view wrt when the
> serial console is initialised.  Until then I'm going to continue
> sitting on the fence on this point.

Yeah, I'll poke him about "console=uart".  I sent it to you because I
think a clean solution requires minor 8250 hooks so we can look up
the ttyS device that corresponds to an MMIO or IO address.

  reply	other threads:[~2004-10-06 19:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 16:14 [RFC][PATCH] Way for platforms to alter built-in serial ports Bjorn Helgaas
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 [this message]
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=200410061354.15746.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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.