public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] early console registration
Date: Thu, 20 May 2004 15:18:05 +0000	[thread overview]
Message-ID: <200405200918.05821.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200405141425.59867.jbarnes@engr.sgi.com>

On Thursday 20 May 2004 7:03 am, Jesse Barnes wrote:
> On Wednesday, May 19, 2004 9:17 pm, David Mosberger wrote:
> > >>>>> On Fri, 14 May 2004 14:25:59 -0700, Jesse Barnes
> > >>>>> <jbarnes@engr.sgi.com> said:
> >
> >   Jesse> Is this reasonable?  I've tested it on a couple of machines
> >   Jesse> here and it works well.  It's really useful for debugging
> >   Jesse> setup_arch problems.
> >
> > I don't like the #ifdef's very much, but I suppose I can live with
> > them in this case.  IIRC, Bjorn also has been working on some
> > early-printk changes so I'd be interested in his opinion.
> 
> Yeah, me neither, but I like the alternative even less--ia64_platform_is 
> and .weak symbols or something.  I *think* this approach will work for Bjorn 
> too (and any other driver that's ok with being called early), but it would be 
> nice to hear it. :)

Well, you could always implement a PCDP (primary console & debug
port device table -- an extension of HCDP).  That would remove the
need for the ia64_platform_is() in your driver and move the #ifdefs
into the pcdp setup routine.  That wouldn't solve the problem for
legacy firmware, though, so what you've got is probably the best
we can do for now.

The interesting bit to me is setting CPU 0 online early.  We've
already set up I/O port space and the machine vector, so that
should be OK.  We haven't done cpu_init() yet, so the per-CPU
data mapping isn't set up yet.  I guess it's probably reasonable
to prohibit early console drivers from using per-CPU data.

Bjorn

  parent reply	other threads:[~2004-05-20 15:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14 21:25 [PATCH] early console registration Jesse Barnes
2004-05-20  1:17 ` David Mosberger
2004-05-20 13:03 ` Jesse Barnes
2004-05-20 15:18 ` Bjorn Helgaas [this message]
2004-05-20 15:26 ` Jesse Barnes
2004-06-03 21:49 ` Jesse Barnes
2004-06-14 22:27 ` Bjorn Helgaas
2004-06-15 13:12 ` Jesse Barnes
2004-06-16 20:22 ` Bjorn Helgaas
2004-06-16 20:40 ` Jesse Barnes
2004-06-22 17:54 ` Jesse Barnes

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=200405200918.05821.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=linux-ia64@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