From: Alex deVries <adevries@thepuffingroup.com>
To: Kirk Bresniker <kirkb@chrome.rose.hp.com>
Cc: Matthew Wilcox <willy@thepuffingroup.com>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Minutes
Date: Wed, 19 Jan 2000 11:40:28 -0500 [thread overview]
Message-ID: <3885E8FC.5800EA9@thepuffingroup.com> (raw)
In-Reply-To: 200001150016.QAA16991@chrome.rose.hp.com
Kirk Bresniker wrote:
> | 4. Martin has cleaned up the serial and console code. He will commit his
> | changes tomorrow after he's tested it.
>
> In testing the 2.3 kernel on my D320/1 with an Access Port (AP) card as
> the console, printk() appeared to be broken. The mprint() statements in
> the boot loader seem to function correctly, and the pdc_putc('.') at
> the end of realmode_setup() works, but the printk() at the start of
> iodc_con_init() never outputs. The chassis codes sent out in
> realmode_setup() do appear properly on the AP console.
I'm curious as to exactly what's in a D320, could you add this to the
hardware database at http://www.thepuffingroup.com/parisc/hw.html?
The console problems you're having are actually global to every machine,
not just yours. I think we've solved several console problems, so you
may want to try again.
> Now the interesting thing in a D-Class with an AP card installed is that
> the RS-232 connector on the back of the machine is dis-connected from
> the LASI serial hardware and connected to the AP card hardware. Because
> of this, regardless of what console path is stored on the machine, the
> AP card console is what is used, so that there will always be console
> outptu.
That's true of console output, since we can just use PDC calls.
However, it's difficult or impossible to do console input with PDC
because we'd have to poll for new characters using PDC_CIN, which is a
bit of a pain.
- Alex
--
Alex deVries
Director of Professional Services
The Puffins at Linuxcare
next prev parent reply other threads:[~2000-01-21 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-14 22:27 [parisc-linux] Minutes Matthew Wilcox
2000-01-15 0:16 ` Kirk Bresniker
2000-01-17 19:27 ` Matthew Wilcox
2000-01-19 16:40 ` Alex deVries [this message]
2000-01-22 12:33 ` [parisc-linux] Harware database down? Hannu Martikka
2000-01-24 21:36 ` dkennedy
2000-01-25 6:46 ` Hannu Martikka
2000-01-25 17:38 ` [parisc-linux] 715 problem Hannu Martikka
2000-01-25 19:22 ` willy
2000-01-25 18:37 ` Hannu Martikka
2000-01-25 18:41 ` Ross J. Reedstrom
2000-01-25 18:43 ` Martin K. Petersen
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=3885E8FC.5800EA9@thepuffingroup.com \
--to=adevries@thepuffingroup.com \
--cc=kirkb@chrome.rose.hp.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=willy@thepuffingroup.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