From: Johannes Erdfelt <jerdfelt@valinux.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Andreas Dilger <adilger@turbolinux.com>,
Khalid Aziz <khalid@fc.hp.com>,
Linux kernel development list <linux-kernel@vger.kernel.org>,
greg@kroah.com
Subject: Re: Support for serial console on legacy free machines
Date: Mon, 30 Jul 2001 21:50:02 -0700 [thread overview]
Message-ID: <20010730215002.I1275@valinux.com> (raw)
In-Reply-To: <200107302240.f6UMeWg2001230@webber.adilger.int> <31754.996543218@kao2.melbourne.sgi.com>
In-Reply-To: <31754.996543218@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Tue, Jul 31, 2001 at 11:33:38AM +1000
On Tue, Jul 31, 2001, Keith Owens <kaos@ocs.com.au> wrote:
> On Mon, 30 Jul 2001 16:40:31 -0600 (MDT),
> Andreas Dilger <adilger@turbolinux.com> wrote:
> >What bothers me is that new systems don't have a serial port, and no ISA
> >slots, so there is no hope of getting a "serial console" support without
> >ACPI (which is rather heavyweight AFAIK). USB is far too complex to use
> >for early-boot debugging, so what else is left?
>
> I briefly discussed this with the USB maintainers at the 2.5 kernel
> developers conference. They thought that a stripped down USB serial
> console was possible, without full USB support. Is that still the
> case?
I think so. Keyboards have a nice feature called boot protocol mode
which is a dumbed down version for BIOS' and the like to use.
What would be needed is a driver for UHCI and OHCI does polling
exclusively, which isn't a big problem and only does control and
interrupt pipes.
I think this can be done with a minimal amount of code. It would
probably be smaller than Linus' original USB driver.
JE
next prev parent reply other threads:[~2001-07-31 4:54 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
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 [this message]
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=20010730215002.I1275@valinux.com \
--to=jerdfelt@valinux.com \
--cc=adilger@turbolinux.com \
--cc=greg@kroah.com \
--cc=kaos@ocs.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.