Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Christoph Plattner <christoph.plattner@dot.at>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Christoph Plattner <christoph.plattner@alcatel.at>,
	Richard Hirst <rhirst@linuxcare.com>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
Date: Wed, 04 Apr 2001 22:31:00 +0200	[thread overview]
Message-ID: <3ACB8484.71DE5601@dot.at> (raw)
In-Reply-To: 20010404180518.C11435@parcelfarce.linux.theplanet.co.uk

Matthew Wilcox wrote:
> 
> On Wed, Apr 04, 2001 at 09:08:23AM +0200, Christoph Plattner wrote:
> > > have you looked at all the followups to the esiee announcement noting
> > > the problems with it?  i suspect it's switching to STI console.
> >
> > Although I definitely write
> >
> >       console=ttyS0
> >
> > as kernel parameter ?
> 
> yes.  they symlinked /dev/console to tty0 instead of leaving it as a
> char device.  the kernel can't help you out here, you have to change
> that symlink :-(
> 
> --
> Revolutions do not require corporate support.

No, No !

This problem have I fixed in my tree !
I tried it with both, the correct one
	/dev/console = 5,1
and the hack !
	/dev/console -> /dev/ttyS0

Further I hacked in a test in the kernel. Before it starts `init' or
any other process, it tries to open the console (You know, the warning,
if this fail). After the open I write out a string using `write (1, )'
as check the return value. I see the string on the serial console !!
and return value is ok.

So the device `/dev/console' IS WORKING in my setup, but the rest is 
not !!!....

Cheers
	Christoph P.

-- 
-------------------------------------------------------------------------
private:	christoph.plattner@dot.at
company:	christoph.plattner@alcatel.at

  reply	other threads:[~2001-04-04 20:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 22:51 [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ? Christoph Plattner
2001-04-02 23:17 ` Richard Hirst
2001-04-02 23:27   ` Matthew Wilcox
2001-04-02 23:41     ` Richard Hirst
2001-04-03  6:55   ` Christoph Plattner
2001-04-03  9:12     ` Richard Hirst
2001-04-03  9:23       ` Christoph Plattner
2001-04-03 13:16         ` Richard Hirst
2001-04-03 21:34     ` Matthew Wilcox
2001-04-04  7:08       ` Christoph Plattner
2001-04-04 17:05         ` Matthew Wilcox
2001-04-04 20:31           ` Christoph Plattner [this message]
2001-04-08 17:08           ` [parisc-linux] Many experience done on 720, but `init' fails !! Christoph Plattner
2001-04-08 17:32             ` [parisc-linux] C180 Progress Marc Eisenbarth
2001-04-09 13:36               ` Matt Taggart
2001-04-09 17:05                 ` Marc Eisenbarth
2001-04-08 21:02             ` [parisc-linux] Many experiments on 720, but `init' fails !! Christoph Plattner
2001-04-09 20:52             ` [parisc-linux] Many experience done " Matt Taggart
2001-04-09 21:12               ` Christoph Plattner
2001-04-10  8:46                 ` Richard Hirst

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=3ACB8484.71DE5601@dot.at \
    --to=christoph.plattner@dot.at \
    --cc=christoph.plattner@alcatel.at \
    --cc=matthew@wil.cx \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rhirst@linuxcare.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