From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] B2k and CONFIG_PDC_CONSOLE pb: followup
Date: Sat, 24 Jan 2004 14:03:20 -0700 [thread overview]
Message-ID: <20040124210320.GA16272@colo.lackof.org> (raw)
In-Reply-To: <40125302.5050600@tiscali.be>
On Sat, Jan 24, 2004 at 11:12:02AM +0000, Joel Soete wrote:
> >If the console is the serial port, then we should be able to disable
> >just the USB device and not impact the Serial ports.
>
> hmm afaik usb ports on a b2k (and I presume for the same family) are just
> there (iirc the user guide and spec) to be used only for usb kbd and mouse
I think that's all PDC and HPUX know how to talk to.
That's all HP will support or warrant.
But it's a USB port and if other devices work, use it.
> and so if no usb kbd was found by pdc we could just disable usb at all?
The problem is USB is doing DMA and was enabled by PDC.
I don't care what's connected (Keyboard vs digital camera).
grant
next prev parent reply other threads:[~2004-01-24 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 18:03 [parisc-linux] B2k and CONFIG_PDC_CONSOLE pb: followup Joel Soete
2004-01-22 5:31 ` Grant Grundler
2004-01-22 15:18 ` Joel Soete
2004-01-23 18:54 ` Joel Soete
2004-01-23 19:45 ` Grant Grundler
2004-01-24 11:12 ` Joel Soete
2004-01-24 21:03 ` Grant Grundler [this message]
2004-01-26 17:00 ` [parisc-linux] A fix for B2k and CONFIG_PDC_CONSOLE pb Joel Soete
2004-01-26 17:25 ` Matthew Wilcox
2004-01-26 18:20 ` Joel Soete
2004-01-26 18:38 ` Joel Soete
2004-01-27 17:17 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 18:54 [parisc-linux] B2k and CONFIG_PDC_CONSOLE pb: followup Joel Soete
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=20040124210320.GA16272@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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.