Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Christoph Plattner <christoph.plattner@gmx.at>
To: Helge Deller <deller@gmx.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.6 & pdc_console pb on c110: "Warning: unable to	open an initial console."
Date: Tue, 13 Jan 2004 00:23:49 +0100	[thread overview]
Message-ID: <40032C85.3040901@gmx.at> (raw)
In-Reply-To: 200312280019.55830.deller@gmx.de

Anyway, the PDC driver should work for all architectures, independent of
the serial type (this was my concept of this driver).

Is the driver fully ported to the 2.6 kernel ?
In the first log, the line "Warning: unable to open an initial console."
was shown, so the open on this device fails !
Futher there is no PDC driver registered under proc/devices !

I have never tested a 2.6 kernel on a HP.

Christoph


Helge Deller wrote:
> On Saturday 27 December 2003 22:00, Joel Soete wrote:
> 
>>I try to see if pdc_console could be operational on my c110 with kernel 2.6.0-pa5.
>>
>>So I uncheck serial_mux and check pdc_console with make menuconfig (edit also pdc_cons.c to define EARLY_BOOTUP_DEBUG)
>>Then I create the special file "mknod /dev/ttyB0 c 11 0", add "TB0:12345:respawn:/sbin/getty 38400 ttyB0" in /etc/inittab
>>
>>(I also try to apply Richard patch <http://lists.parisc-linux.org/pipermail/parisc-linux/2002-May/016384.html>)
>>
>>But no way to make it works?
>>
>>Linux version 2.6.0-pa5 (root@hpalin) (gcc version 3.3.3 20031206 (prerelease) 3FP[0] enabled: Rev 1 Model 11 
>>                               The 32-bit Kernel has started...
>>Initialized PDC Console for debugging.
>>Determining PDC firmware type: System Map.
>>model 000058e0 00000481 00000000 00000002 77e47570 100000f1 00000004 0000008a 0avers  0000000d
>>CPUID vers 11 rev 13 (0x0000016d)
>>model 9000/777/C110
>>Total Memory: 128 Mb
>>[snip]
>>Soft power switch enabled, polling @ 0xf0140000.
>>Console: switching to colour frame buffer device 128x48
>>pty: 256 Unix98 ptys configured
>>lp: driver loaded but no devices found
>>Generic RTC Driver v1.07
>>Serial: 8250/16550 driver $Revision: 1.90 $ 13 ports, IRQ sharing enabled
>>ttyS0 at MMIO 0xffd05800 (irq = 90) is a 16550A
>>ttyS1 at MMIO 0xffe02800 (irq = 121) is a 16550A
> 
> 
> Your machine has standard serial ports. So why do you want to
> switch on serial_mux stuff when it's not needed (and not possible
> since the device is not present in your machine) ?
> 
> Helge
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 
> 



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

  parent reply	other threads:[~2004-01-12 23:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-27 21:00 [parisc-linux] 2.6 & pdc_console pb on c110: "Warning: unable to open an initial console." Joel Soete
2003-12-27 23:19 ` Helge Deller
2003-12-28 18:02   ` Joel Soete
2003-12-28 20:00     ` Helge Deller
2004-01-12 23:23   ` Christoph Plattner [this message]
2004-01-13  8:39     ` Joel Soete
2004-01-14 23:34       ` Christoph Plattner
2004-01-03  3:28 ` Ryan Bradetich
2004-01-03 10:52   ` 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=40032C85.3040901@gmx.at \
    --to=christoph.plattner@gmx.at \
    --cc=deller@gmx.de \
    --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