From: "Bjorn Helgaas" <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] set altix preferred console
Date: Tue, 04 Oct 2005 19:07:14 +0000 [thread overview]
Message-ID: <41804.83.175.203.50.1128452834.squirrel@mail.atl.hp.com> (raw)
In-Reply-To: <20050930200422.GD13855@sgi.com>
> Our prom currently does not build up ACPI tables describing PCI (or any
> IO)
> devices. We are working toward that goal, but it is still
> work in progress and will be some time yet before this is done.
>
> It is because of this shortcoming that we have to rely on the PCDP table
> to provide the io addresses needed for VGA console.
>
> Outside of PCDP, our earliest opportunity to get information about VGA
> devices is through the call sequence initiated with
> subsys_initcall(sn_pci_init), which would seem way too late for early boot
> messages.
It's the same for us. We don't find out about our built-in serial
ports until the 8250 driver initializes, which is pretty late. So
we have "8250_early" that uses information from the PCDP to talk
to the serial port before the normal 8250 driver discovers it.
The important thing is that the PCDP doesn't influence the naming
of the device (and there isn't really a "name" for VGA devices,
AFAIK).
> Out of curiousity, what are the mmio_tra/ioport_tra fields in the PCDP PCI
> interface structure intended for if not for this purpose?
You *can* use the _tra fields in the PCDP -- that's what they're
there for. But the PCDP should be *optional*, and I think it's
not for your current setup.
If we don't build pcdp.o on an HP box, the console still works
just fine; it just doesn't work until the 8250 driver discovers
the port, which is fairly late.
So I think all you need to do is add some SN-specific code
somewhere that discovers the VGA device. It sounds like the
only way to do that right now is to get the information from
the PCDP, so I guess that's what you need to do. But having
this duplicated in the SN code means that you won't need the
change to pcdp.c.
next prev parent reply other threads:[~2005-10-04 19:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 20:04 [PATCH] set altix preferred console Greg Edwards
2005-09-30 21:20 ` Bjorn Helgaas
2005-10-03 14:44 ` Greg Edwards
2005-10-04 15:04 ` Mark Maule
2005-10-04 19:07 ` Bjorn Helgaas [this message]
2005-10-04 20:46 ` Mark Maule
2005-10-11 20:00 ` Mark Maule
2005-10-11 21:19 ` Bjorn Helgaas
2005-10-11 21:31 ` Mark Maule
2005-10-11 21:57 ` Bjorn Helgaas
2005-10-12 18:55 ` Mark Maule
2005-10-13 13:10 ` Greg Edwards
2005-10-18 17:06 ` Luck, Tony
2005-10-18 18:33 ` Bjorn Helgaas
2005-10-18 18:39 ` Mark Maule
2005-11-11 17:52 ` Mark Maule
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=41804.83.175.203.50.1128452834.squirrel@mail.atl.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