public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bru <xavier.bru@bull.net>
To: linux-ia64@vger.kernel.org
Subject: HCDP concerns
Date: Wed, 01 Sep 2004 10:25:43 +0000	[thread overview]
Message-ID: <4135A3A7.9000706@bull.net> (raw)

Hello Bjorn and all,

I have some concerns with using kernel 2.6.8.1 (and 2.6.7) with our 
platform that has a new BIOS that provides HCDP.

1) When kernel is configured without h/pcdp support ( CONFIG_EFI_PCDP is 
not set),
the serial console are not initialized (efi.hcdp is not NULL).

A simple fix could be:
--- linux-2.6.8.1-ori/arch/ia64/kernel/setup.c    2004-08-14 
12:54:50.000000000 +0200
+++ linux-2.6.8.1/arch/ia64/kernel/setup.c    2004-08-31 
11:54:02.000000000 +0200
@@ -351,9 +351,9 @@
 #endif
 #ifdef CONFIG_EFI_PCDP
     efi_setup_pcdp_console(*cmdline_p);
+    if (!efi.hcdp)
 #endif
 #ifdef CONFIG_SERIAL_8250_CONSOLE
-    if (!efi.hcdp)
         setup_serial_legacy();
 #endif

2) Our platform has 2 serial ports (let say port 0 at address 3f8, port 
1 at address 2f8). Usually port 0 is seen as ttyS0 & port 1 as ttyS1. 
EFI console redirection is done on port S1 (2f8) & is described through 
HCDP(port 0 is not described).
Using the h/pcdp support ( CONFIG_EFI_PCDP=1), we get some strange 
behaviours:
. "console=ttyS0" boot parameter, as explained in menuconfig takes the 
HCDP table entry as console, but changes the ttyS* order:
ttyS1 for port 0 (3f8) and ttyS0 for port 1 (2f8). Console is OK,  but 
the ttyS0 on port 1 is confusing compared to kernels without hcdp support.
. due to this behaviour, there is no more possibility to have the linux 
console redirection on the port 0 at boot time.
. My understanding was that h/pcdp support should provide some new 
consoleïi (or serial)  option to have the console defined by efi used 
by linux as console, but that this should not change the ttyS order, and 
that we should still be able to use console="ttySx" at boot time to have 
the console on port "x".
. specifying no "console=" provides no console as the Conout variable is 
not exported by EFI at runtime. Should it be ?

Thanks in advance for your clarifications.
Xavier
-- 

 Sincères salutations.
_____________________________________________________________________
 
Xavier BRU                 BULL ISD/R&D/INTEL office:     FREC B1-422
tel : +33 (0)4 76 29 77 45                    http://www-frec.bull.fr
fax : +33 (0)4 76 29 77 70                 mailto:Xavier.Bru@bull.net
addr: BULL, 1 rue de Provence, BP 208, 38432 Echirolles Cedex, FRANCE
_____________________________________________________________________


             reply	other threads:[~2004-09-01 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01 10:25 Xavier Bru [this message]
2004-09-01 15:14 ` HCDP concerns Bjorn Helgaas
2004-09-01 16:36 ` Tolentino, Matthew E
2004-09-02 20:38 ` Bjorn Helgaas
2004-09-03 15:44 ` Xavier Bru

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=4135A3A7.9000706@bull.net \
    --to=xavier.bru@bull.net \
    --cc=linux-ia64@vger.kernel.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