From: Grant Grundler <grundler@cup.hp.com>
To: herrold <herrold@owlriver.com>
Cc: "Paul J.Y. Lahaie" <pjlahaie@linuxcare.com>,
parisc-linux@thepuffingroup.com, grundler@milano.cup.hp.com
Subject: Re: Serial vs. STI console selector was: Re: [parisc-linux] Beta CD
Date: Mon, 20 Nov 2000 12:59:41 -0800 [thread overview]
Message-ID: <200011202059.MAA18987@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Mon, 20 Nov 2000 15:40:24 PST." <Pine.LNX.4.30.0011201531170.6744-100000@pokey.513erich.iwaynet.net>
"Russ" herrold wrote:
> Is this possible, to allow support of both, with a single kernel?
Yes. I think the issues are code not stomping on each other.
And it's easy than you might think - PDC can tell us what the
primary console is.
grant
Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253
prev parent reply other threads:[~2000-11-20 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 20:43 [parisc-linux] Beta CD Paul J.Y. Lahaie
2000-11-14 21:18 ` Brian Poole
2000-11-20 20:40 ` Serial vs. STI console selector was: " herrold
2000-11-20 20:59 ` Grant Grundler [this message]
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=200011202059.MAA18987@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=grundler@milano.cup.hp.com \
--cc=herrold@owlriver.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=pjlahaie@linuxcare.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