From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Khalid Aziz <khalid@fc.hp.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 09:20:52 -0700 [thread overview]
Message-ID: <3B66DAE4.54937826@osdlab.org> (raw)
In-Reply-To: <200107302240.f6UMeWg2001230@webber.adilger.int> <31754.996543218@kao2.melbourne.sgi.com> <20010730215002.I1275@valinux.com> <3B66D9B9.A01685AB@fc.hp.com>
Khalid Aziz wrote:
>
> We are moving slightly off of my original question which still stands.
> For machines that do have serial ports but not at legacy addresses
> (COM1, COM2,....), is it acceptable to use the description of these
> ports as provided by SPCR and DBGP tables even though Microsoft claims
> copyright on these tables and retains the option to modify these tables
> at any time? Would it be preferable to use a table defined as part of a
> standard like ACPI 2.0 or DIG64 (such a table does not exist at this
> time but with enough votes for it, it may be added)?
We already use other MS-defined tables and specs, like the
$PIR interrupt routing table.
Alan implemented the Simple Boot Flag Protocol in 2.4.5(?)-ac,
which is also from www.microsoft.com.
There are other ACPI-like tables that probably need to be
used for NUMA machines that are defined/specified only at
microsoft.com.
IOW, these represent "de facto" industry specs (I hesitate
to say "standards"), so use them.
--
~Randy
next prev parent reply other threads:[~2001-07-31 16:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 21:26 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
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 [this message]
[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=3B66DAE4.54937826@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=khalid@fc.hp.com \
--cc=linux-kernel@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
Powered by JetHome