From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Khalid Aziz <khalid@fc.hp.com>
Cc: Andreas Dilger <adilger@turbolinux.com>,
Linux kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Support for serial console on legacy free machines
Date: Mon, 30 Jul 2001 16:52:16 -0700 [thread overview]
Message-ID: <3B65F330.CD4BE9DB@osdlab.org> (raw)
In-Reply-To: <200107302240.f6UMeWg2001230@webber.adilger.int> <3B65E711.A3828E15@fc.hp.com> <3B65EB21.C1DD8624@osdlab.org> <3B65F02B.53A8880D@fc.hp.com>
Khalid Aziz wrote:
>
> "Randy.Dunlap" wrote:
> >
> > Khalid Aziz wrote:
> > > I am puzzled. How would you get "serial console" support even with ACPI
> > > unless there IS a serial port on the system????? All ACPI can do is tell
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > you where the serial port is.
> >
> > Wait a minute. Aren't you the person who originally proposed this,
> > and you don't know how it's used?
> >
> > Here are 2 possibilities:
> >
> > a. Some pre-production motherboards are built with serial ports on
> > them, only for debugging. Never shipped to customers like this.
> > The documented I/O resources for this serial port are in the
> > special ACPI table that you referred to last Thursday.
> >
>
> And that means system DOES have a serial port. All SPCR table does is
> tell you where it is (in I/O, memory or PCI space). SPCR table does not
> add a serial port. Some kind of serial port has to exist for SPCR table
> to be meaningful. My understanding of Andreas' question was how to get
> serial console support (or same kind of functionality) when the new
> systems do not have a serial port.
OK, thanks for the clarification. I misunderstood Andreas's question.
> If a USB chipset could "emulate" a serial port by doing proper
> translation from read/write into USB protocol transfers, system still
> has a serial port from OS point of view and all ACPI tables will do is
> tell me where to find it.
I agree (mostly).
--
~Randy
next prev parent reply other threads:[~2001-07-30 23:55 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 [this message]
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
[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=3B65F330.CD4BE9DB@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=adilger@turbolinux.com \
--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