From: Mark Maule <maule@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] set altix preferred console
Date: Tue, 04 Oct 2005 15:04:28 +0000 [thread overview]
Message-ID: <20051004150428.GC27923@sgi.com> (raw)
In-Reply-To: <20050930200422.GD13855@sgi.com>
On Mon, Oct 03, 2005 at 09:44:08AM -0500, Greg Edwards wrote:
> On Fri, Sep 30, 2005 at 03:20:11PM -0600, Bjorn Helgaas wrote:
> | I think what *should* happen is that we should discover VGA
> | devices by PCI enumeration, and the iobase/membase information
> | would come from the ACPI description of the PCI root bridges.
> | Then we could support multiple VGA devices, and the PCDP could
> | point to one of them to be used as the console.
> |
> | The VGA code in the kernel is a long ways from that. But your
> | firmware should provide the vga_console_{iobase,membase} data
> | somewhere besides the PCDP. Can you do something in ia64/sn
> | to dig it out?
>
> Thanks for the info and suggestion, Bjorn. I think we should be able to
> come up with something in sn-specific code. I'll talk to our I/O guys
> and see what we can come up with.
>
> Greg
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.
Out of curiousity, what are the mmio_tra/ioport_tra fields in the PCDP PCI
interface structure intended for if not for this purpose?
Mark
next prev parent reply other threads:[~2005-10-04 15:04 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 [this message]
2005-10-04 19:07 ` Bjorn Helgaas
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=20051004150428.GC27923@sgi.com \
--to=maule@sgi.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