From: "Joel Soete" <soete.joel@tiscali.be>
To: "PARISC list" <parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] B2k and CONFIG_PDC_CONSOLE pb: followup
Date: Wed, 21 Jan 2004 19:03:05 +0100 [thread overview]
Message-ID: <400CB89F00001978@ocpmta2.freegates.net> (raw)
Hi all,
On the my b2k when I add 'CONFIG_PDC_CONSOLE' the system hang just after
"Searching for devices..." leting the led CDROM continuously bright ???
With some printk, I reach to figure out that is at the pdc_suspend_usb()
point where the boot hang. I try to bypass this and so it boot well.
In fact the big difference with a kernel without CONFIG_PDC_CONSOLE is the
early call to pdc_console_init_force() which (before register the pdc_cons
do:
[snip]
/* If the console is duplex then copy the COUT parameters to CIN.*/
if (PAGE0->mem_cons.cl_class == CL_DUPLEX)
memcpy(&PAGE0->mem_kbd, &PAGE0->mem_cons, sizeof(PAGE0->mem_cons));
/* register the pdc console */
register_console(&pdc_cons);
}
I also try to bypass this memcpy (and restore pdc_suspend_usb() call) and
it boot also well.
In sumary, on the b2k, this early memcpy() seems to break something in the
later pdc_suspend_usb() call. My problem is the pdc_suspend_usb()
which results finaly in a call to real32_call_asm(): actualy asm code in
which
it's difficult to insert printk to analyse the difference of behaviour ?)
I also already get a toc but didn't give me any relevant info on what happen
:(
Any idea to help me to get more details about this pb?
Thanks in advance,
Joel
PS:
I added some printk to get some pdc addresses:
static void pdc_console_init_force(void)
{
if (pdc_console_initialized)
return;
++pdc_console_initialized;
if (PAGE0->mem_cons.cl_class == CL_DUPLEX) {
printk(KERN_INFO "pdc_console_init_force() would set a CL_DUP.\n");
printk(KERN_INFO "PAGE0->mem_cons address: %p.\n", &PAGE0->mem_cons);
printk(KERN_INFO "PAGE0->mem_kbd address: %p.\n", &PAGE0->mem_kbd);
printk(KERN_INFO "PAGE0->mem_kbd size: %d.\n", sizeof(PAGE0->mem_cons));
};
/* If the console is duplex then copy the COUT parameters to CON.*/
/*
if (PAGE0->mem_cons.cl_class == CL_DUPLEX)
memcpy(&PAGE0->mem_kbd, &PAGE0->mem_cons, sizeof(PAGE0->mem_cons));
*/
/* register the pdc console */
register_console(&pdc_cons);
}
The 32-bit Kernel has started...
pdc_console_init_force() would set a CL_DUP.
PAGE0->mem_cons address: 100003a0.
PAGE0->mem_kbd address: 10000400.
PAGE0->mem_kbd size: 48.
But that couldn't help more for the moment :(
-------------------------------------------------------------------------
Tiscali ADSL: 12 mois à 29,50 /mois! L'Internet rapide, c'est pour tout
le monde.
http://reg.tiscali.be/default.asp?lg=fr
next reply other threads:[~2004-01-21 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 18:03 Joel Soete [this message]
2004-01-22 5:31 ` [parisc-linux] B2k and CONFIG_PDC_CONSOLE pb: followup Grant Grundler
2004-01-22 15:18 ` Joel Soete
2004-01-23 18:54 ` Joel Soete
2004-01-23 19:45 ` Grant Grundler
2004-01-24 11:12 ` Joel Soete
2004-01-24 21:03 ` Grant Grundler
2004-01-26 17:00 ` [parisc-linux] A fix for B2k and CONFIG_PDC_CONSOLE pb Joel Soete
2004-01-26 17:25 ` Matthew Wilcox
2004-01-26 18:20 ` Joel Soete
2004-01-26 18:38 ` Joel Soete
2004-01-27 17:17 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 18:54 [parisc-linux] B2k and CONFIG_PDC_CONSOLE pb: followup 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=400CB89F00001978@ocpmta2.freegates.net \
--to=soete.joel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.