From: Bastos Fernandez Alexandre <ALEBAS@televes.com>
To: linuxppc-embedded@ozlabs.org
Subject: RE: 2.6.10-rc3 for 8xx booting "load_kernel(...)" function probl em v s configuring and initializing serial console ?
Date: Mon, 27 Dec 2004 09:00:39 +0100 [thread overview]
Message-ID: <51DB8827D393D411BB69003048003F46FDCF8A@tvesntr.televes.com> (raw)
Hi Alex
In mpc8272ads (that's PQ2 board) I use
console=ttyCPM root=/dev/ram0
I don't know if this would help you.
Best regards
Alex ... Bastos :-)
-----Original Message-----
From: Povolotsky, Alexander [SMTP:Alexander.Povolotsky@marconi.com]
Sent: Thursday, December 23, 2004 6:24 PM
To: linuxppc-embedded@ozlabs.org
Subject: 2.6.10-rc3 for 8xx booting "load_kernel(...)" function
problem v s configuring and initializing serial console ?
Hi,
with
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE="console=ttyCPM0 panic=3 root=/dev/ram"
...
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_DIGI is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_N_HDLC is not set
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set
#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_CPM=y
CONFIG_SERIAL_CPM_CONSOLE=y
CONFIG_SERIAL_CPM_SCC1=y
CONFIG_SERIAL_CPM_SCC2=y
# CONFIG_SERIAL_CPM_SCC3 is not set
# CONFIG_SERIAL_CPM_SCC4 is not set
# CONFIG_SERIAL_CPM_SMC1 is not set
# CONFIG_SERIAL_CPM_SMC2 is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256in my .config file,
still somehow in 2.6.10-rc3 (for 8xx) the "load_kernel(...)" function in
the
./arch/ppc/boot/simple/misc-embedded.c is not getting called during the
boot ? (I think ...) ... or serial is not getting initialiazed correctly
within this function
when "serial_init(...)" function is called within it ?...
(no JTAG emulator debugging is available to me on this board ...)
**********On Linux 2.4.26 I used to see during the boot:*********
(M)odify any of this or (C)ontinue? [M] C
Updating parameter storage. This may take a while...
Done writing in Storage Area
Starting Application from bank 1
Done
********(then from load_kernel() I would see)**********
loaded at: 00180000 0035622C
board data at: 0035313C 0035317C
relocated to: 001852CC 0018530C
zimage at: 001857F9 00226057
initrd at: 00227000 00352ADF
avail ram: 00357000 02000000
Linux/PPC load: panic=3 root=/dev/ram
Uncompressing Linux...done.
initrd moved: 00400000 0052BADF
Now booting the kernel
Running from bank 1
Selecting default root device 1f04
Linux version 2.4.26 (apovolot@localhost.localdomain) (gcc version 3.4.1)
#2
Fri Dec 10 13:37:12 EST 2004
.....
On 2.6.10-rc3 nothing "happens" (and then it is just getting reexecuted)
after I see: Done
Any ideas ?
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
reply other threads:[~2004-12-27 8:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51DB8827D393D411BB69003048003F46FDCF8A@tvesntr.televes.com \
--to=alebas@televes.com \
--cc=linuxppc-embedded@ozlabs.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