From: root@mauve.demon.co.uk
To: rddunlap@osdl.org (Randy.Dunlap)
Cc: Valdis.Kletnieks@vt.edu, root@mauve.demon.co.uk,
tmolina@cablespeed.com, linux-kernel@vger.kernel.org,
greg@kroah.com, zwane@linuxpower.ca
Subject: Re: Console on USB
Date: Wed, 20 Aug 2003 20:40:19 +0100 (BST) [thread overview]
Message-ID: <200308201940.UAA23958@mauve.demon.co.uk> (raw)
In-Reply-To: <20030820110742.0cd0160a.rddunlap@osdl.org> from "Randy.Dunlap" at Aug 20, 2003 11:07:42 AM
>
> On Wed, 20 Aug 2003 13:56:18 -0400 Valdis.Kletnieks@vt.edu wrote:
>
> | On Wed, 20 Aug 2003 18:44:58 BST, root@mauve.demon.co.uk said:
> |
> | > For laptops, might console=/dev/irda work?
> |
> | Hmm.... <looks around> Do I have anything handy that will *catch* stuff being
> | spewed out the irda port? Don't think so, or I'd have built that driver....
> |
> | Yes, might work, *if* you have hardware handy.
>
> I don't see any console support in the irda drivers...
> How is it supposed to work?
> or do you just mean that in theory it could be made to work?
I last looked at irda, when my laptop was a 486/745, and thought that
the hardware still looked more or less like a 8250 variant.
I had previously used /dev/ttyS1 (where that was an IR port) to dump
debugging data.
Looking at the documentation for more recent hardware, I find this isn't really
the case any more for all hardware.
next prev parent reply other threads:[~2003-08-20 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 3:20 Console on USB 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 [this message]
[not found] <mailman.1061346549.9440.linux-kernel2news@redhat.com>
2003-08-20 4:46 ` Pete Zaitcev
2003-08-20 4:58 ` Randy.Dunlap
2003-08-20 5:11 ` Pete Zaitcev
2003-08-20 7:15 ` Zwane Mwaikambo
2003-08-20 17:08 John Bradford
2003-08-20 17:08 ` Greg KH
2003-08-20 17:28 John Bradford
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=200308201940.UAA23958@mauve.demon.co.uk \
--to=root@mauve.demon.co.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=tmolina@cablespeed.com \
--cc=zwane@linuxpower.ca \
/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;
as well as URLs for NNTP newsgroup(s).