All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Tom Rini <trini@kernel.crashing.org>
Subject: Re: [PATCH] Fix 8250 probe on ppc32
Date: Sat, 19 Nov 2005 08:36:34 +1100	[thread overview]
Message-ID: <1132349794.20016.94.camel@gaston> (raw)
In-Reply-To: <5534EC32-EE72-4019-A5D9-305F8348E4D9@kernel.crashing.org>


> How early on can we use udbg? I'd be interested to see how this is  
> going to work out for 4xx/83xx/85xx w/built-in 8250's.

As soon as you can get something mapped I suppose... On ppc32 with
BootX, I setup a BAT in head.S, thus udbg is available in
machine_init(). On ppc64 with hypervisor console, we can enable hacks
that initialize udbg in real mode.

Ben.

  reply	other threads:[~2005-11-18 21:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 10:04 [PATCH] Fix 8250 probe on ppc32 David Woodhouse
2005-11-07 16:09 ` Tom Rini
2005-11-07 16:20   ` David Woodhouse
2005-11-07 16:31     ` Tom Rini
2005-11-07 17:25       ` Dan Malek
2005-11-07 16:54     ` Christoph Hellwig
2005-11-07 17:02       ` David Woodhouse
2005-11-16  8:51         ` David Woodhouse
2005-11-16  9:12           ` Paul Mackerras
2005-11-16 10:25             ` David Woodhouse
2005-11-16 15:24               ` Kumar Gala
2005-11-18  1:12               ` Paul Mackerras
2005-11-18  3:26                 ` Kumar Gala
2005-11-18  3:50                   ` Benjamin Herrenschmidt
2005-11-18  8:23                     ` Christoph Hellwig
2005-11-18 10:51                       ` Benjamin Herrenschmidt
2005-11-18 14:46                         ` Kumar Gala
2005-11-18 21:36                           ` Benjamin Herrenschmidt [this message]
2005-11-18 21:39                             ` David Woodhouse

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=1132349794.20016.94.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=dwmw2@infradead.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=trini@kernel.crashing.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 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.