public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: uart_match_port() question
Date: Thu, 08 Dec 2005 11:17:28 +1100	[thread overview]
Message-ID: <1134001049.7168.97.camel@gaston> (raw)
In-Reply-To: <200512071636.33901.bjorn.helgaas@hp.com>

On Wed, 2005-12-07 at 16:36 -0700, Bjorn Helgaas wrote:
> On Wednesday 07 December 2005 4:13 pm, Benjamin Herrenschmidt wrote:
> > ...  Part of the problem here is for example PIO. There is no such
> > thing as PIO on a PowerPC, it's purely a PCI abstraction, thus inX/outX
> > will only work once the PCI host briges have been discovered and their
> > IO space mapped (setup_arch() time, but I definitely want my early
> > console earlier).
> 
> ia64 has a similar problem, but it's a bit easier because firmware
> configures and tells us about the legacy (0-64K) I/O port space.
> So we do have to look up the MMIO base where those I/O ports get
> mapped, but that's basically the first thing in setup_arch().  We
> don't do much before that, so it hasn't been worthwhile to make
> the console work earlier.

Oh, that's what I do too, that is, I have a mecanism now to walk the
firmware device-tree and get the MMIO, my problem was with matching that
MMIO address with the PIO one that 8250 gets later on. It seems that you
solved that problem so it looks like I really need to look more closely
at what you are doing :)

Ben.



  reply	other threads:[~2005-12-08  0:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-27  0:21 uart_match_port() question Benjamin Herrenschmidt
2005-11-28 11:30 ` Russell King
2005-11-28 11:36   ` Benjamin Herrenschmidt
2005-12-07 22:15 ` Bjorn Helgaas
2005-12-07 23:13   ` Benjamin Herrenschmidt
2005-12-07 23:36     ` Bjorn Helgaas
2005-12-08  0:17       ` Benjamin Herrenschmidt [this message]
2005-12-08 16:26         ` Bjorn Helgaas

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