From: Pete Zaitcev <zaitcev@redhat.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: zaitcev@redhat.com, tmolina@cablespeed.com, linux-kernel@vger.kernel.org
Subject: Re: Console on USB
Date: Wed, 20 Aug 2003 01:11:09 -0400 [thread overview]
Message-ID: <20030820011109.A24410@devserv.devel.redhat.com> (raw)
In-Reply-To: <32801.4.4.25.4.1061355525.squirrel@www.osdl.org>; from rddunlap@osdl.org on Tue, Aug 19, 2003 at 09:58:45PM -0700
> Date: Tue, 19 Aug 2003 21:58:45 -0700 (PDT)
> From: "Randy.Dunlap" <rddunlap@osdl.org>
> >> Is there any advice I might be able to use to get this going?
> >
> > You'd have to write it. Grep for register_console for starters.
>
> usb/serial/console.c:255: register_console(&usbcons);
Eeek, eating a crow now.
> >> I really want to be able to catch some oops output.
> >
> > If oops happens with interrupts closed, forget about it.
> > USB needs interrupts to work. This is one of the reasons nobody
> > bothered to implement console over USB serial.
>
> The call to register_console() also happens very late in the boot
> sequence, so if your oops is early, USB console won't help.
It's true for many consoles, that's why sparc allows
"-p" in SILO options, for instance. I think either wli or willy
did "early VGA printk" patch.
Interrupts are a major problem. Also, the USB stack is pretty
thick.
-- Pete
next prev parent reply other threads:[~2003-08-20 5:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1061346549.9440.linux-kernel2news@redhat.com>
2003-08-20 4:46 ` Console on USB Pete Zaitcev
2003-08-20 4:58 ` Randy.Dunlap
2003-08-20 5:11 ` Pete Zaitcev [this message]
2003-08-20 7:15 ` Zwane Mwaikambo
2003-08-20 17:28 John Bradford
-- strict thread matches above, loose matches on Subject: below --
2003-08-20 17:08 John Bradford
2003-08-20 17:08 ` Greg KH
2003-08-20 3:20 Thomas Molina
2003-08-20 7:12 ` Zwane Mwaikambo
2003-08-20 7:38 ` stefan.eletzhofer
2003-08-20 16:14 ` Greg KH
2003-08-20 17:44 ` root
2003-08-20 17:56 ` Valdis.Kletnieks
2003-08-20 18:07 ` Randy.Dunlap
2003-08-20 18:46 ` Valdis.Kletnieks
2003-08-20 19:40 ` root
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=20030820011109.A24410@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=tmolina@cablespeed.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