Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Ryan Bradetich <rbradetich@uswest.net>
To: jsoe0708@tiscali.be
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.4.20-paxx Config problem (follow-up)
Date: 23 Dec 2002 11:18:02 -0700	[thread overview]
Message-ID: <1040667483.24209.57.camel@beavis> (raw)
In-Reply-To: <3DED9BBD00002FDE@ocpmta7.freegates.net>

Joel,

The PDC Console should work for this box as it is really a firmware
console.  The firmware console talks to /dev/ttyB0 instead of
/dev/ttyS0, so that might be your problem?  Also in recent kernels the
major number of /dev/ttyB0 changed from 60 to 11 so make sure the 
device file is correct.

Finally, out of curiosity, why are you trying to use the PDC console? 
The B2k should have a 16550 port (off the suckyio chip???) that should
work for you.

Thanks, and hope this helps!

- Ryan


On Mon, 2002-12-23 at 09:34, jsoe0708@tiscali.be wrote:
> Hi all,
> 
> The problem I met with arch/parisc/32 on my b2k is due to the CONFIG_SERIAL_NONSTANDARD
> (or a subselect ??).
> 
> Is PDC_console does not work on this model or is there a border effect link
> with this selection?
> 
> Can somebody help me to fix it?
> 
> Thanks,
>     Joel
> 
> 
> ********************************************
> Promo Tiscali ADSL: 35 Euros/mois, 1er mois et activation = 0 Euro http://adsl.tiscali.be
> 
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 

  reply	other threads:[~2002-12-23 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23 16:34 [parisc-linux] 2.4.20-paxx Config problem (follow-up) jsoe0708
2002-12-23 18:18 ` Ryan Bradetich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-24  7:27 jsoe0708

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=1040667483.24209.57.camel@beavis \
    --to=rbradetich@uswest.net \
    --cc=jsoe0708@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox