Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Naresh <knaresh@india.hp.com>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] PDC console problem.
Date: Tue, 01 Apr 2003 13:08:15 -0600	[thread overview]
Message-ID: <3E89E39F.B544BCFA@india.hp.com> (raw)
In-Reply-To: 1049181423.24319.17.camel@beavis.ybsoft.com

A small correction to the original mail: the kernel source that was compiled
was the one thats listed as latest ( cvs/linux_latest.tar.gz), which I guess
is 2.4.20-pa22. I have booted this very same kernel off an L-Class machine
with the PDC console option off.

Regards
Naresh.

Ryan Bradetich wrote:

> > I was going through some of the FAQ and the mailing list archive and
> > understand that the PDC console is not a full blown console and can only
> > display output. Is is true that the PDC console cannot accept keyboard
> > input? Or am I missing something?
>
> Hmm.. The pdc_console has both read and write capabilities.  We used the
> PDC console for K/E class systems before the SerialMux driver was
> written.  I am not familiar with the PDC simulator, but I would be
> willing to test the pdc console again on K-Class.
>
> Which kernel are you using?
>
> Thanks,
>
> - Ryan
>
> --
> Ryan Bradetich <rbradetich@uswest.net>
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2003-04-01  7:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 18:35 [parisc-linux] PDC console problem Naresh
2003-04-01  7:17 ` Ryan Bradetich
2003-04-01 19:08   ` Naresh [this message]
2003-04-01 19:16   ` Christoph Plattner
2003-04-01 19:27 ` Christoph Plattner

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=3E89E39F.B544BCFA@india.hp.com \
    --to=knaresh@india.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rbradetich@uswest.net \
    /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