From: Khalid Aziz <khalid@fc.hp.com>
To: Stuart MacDonald <stuartm@connecttech.com>
Cc: Linux kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Support for serial console on legacy free machines
Date: Tue, 31 Jul 2001 10:10:28 -0600 [thread overview]
Message-ID: <3B66D873.FA2385FC@fc.hp.com> (raw)
In-Reply-To: <200107302332.f6UNWbxg001791@webber.adilger.int> <3B65F1A2.30708CC1@fc.hp.com> <000701c119cd$ebf0c720$294b82ce@connecttech.com>
Stuart MacDonald wrote:
>
> It seems like pci consoles won't work, now that I think about it. The
> console driver gets an index, which I'm going to assume works thusly:
> lilo console=ttyS1 ends up passing 1 as the index. That index is used
> to pick a serial port out of the array of serial ports that the driver
> knows about. If console init happens early, and serial driver init happens
> late (it would be dependent on pci init) then only hard coded ports
> would work. Those are defined in asm/serial.h, and for i386 include the
> standard ports, and a number of isa ports from various board manufacturers.
>
> Using one of our pci ports would require knowledge of its io address,
> which wouldn't be available until the pci subsystem had inited. Perhaps
> that could be changed to allow pci based consoles?
>
That is precisely the problem with trying to use a PCI serial port as
console. It is not trivial to move the PCI initialization earlier in the
boot sequence.
--
Khalid
====================================================================
Khalid Aziz Linux Systems Operation R&D
(970)898-9214 Hewlett-Packard
khalid@fc.hp.com Fort Collins, CO
next prev parent reply other threads:[~2001-07-31 16:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 21:26 Support for serial console on legacy free machines Andreas Dilger
2001-07-30 21:38 ` Khalid Aziz
2001-07-30 22:40 ` Andreas Dilger
2001-07-30 22:53 ` Jan-Benedict Glaw
2001-07-30 22:53 ` Maciej W. Rozycki
2001-07-30 23:00 ` Khalid Aziz
2001-07-30 23:17 ` Randy.Dunlap
2001-07-30 23:39 ` Khalid Aziz
2001-07-30 23:52 ` Randy.Dunlap
2001-07-30 23:32 ` Andreas Dilger
2001-07-30 23:40 ` Ignacio Vazquez-Abrams
2001-07-30 23:45 ` Khalid Aziz
2001-07-31 14:34 ` Stuart MacDonald
2001-07-31 15:54 ` Miquel van Smoorenburg
2001-07-31 16:00 ` Eric W. Biederman
2001-07-31 16:10 ` Khalid Aziz [this message]
2001-07-31 16:39 ` Andreas Dilger
2001-07-31 18:43 ` Russell King
2001-08-01 2:01 ` Keith Owens
2001-07-31 16:42 ` Russell King
2001-07-31 17:14 ` Stuart MacDonald
2001-07-31 18:46 ` Russell King
2001-08-01 3:21 ` Eric W. Biederman
2001-08-01 3:39 ` Ignacio Vazquez-Abrams
2001-07-31 1:33 ` Keith Owens
2001-07-31 4:50 ` Johannes Erdfelt
2001-07-31 16:15 ` Khalid Aziz
2001-07-29 20:47 ` Alan Cox
2001-07-31 16:20 ` Randy.Dunlap
[not found] <no.id>
2001-07-26 22:20 ` Alan Cox
2001-07-30 17:47 ` Khalid Aziz
-- strict thread matches above, loose matches on Subject: below --
2001-07-26 21:13 Khalid Aziz
2001-07-27 13:28 ` Simon Richter
2001-07-30 17:49 ` Khalid Aziz
2001-07-30 18:21 ` Rik van Riel
2001-07-30 19:39 ` Khalid Aziz
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=3B66D873.FA2385FC@fc.hp.com \
--to=khalid@fc.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stuartm@connecttech.com \
/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;
as well as URLs for NNTP newsgroup(s).