In message [off-list ref] you wrote:
But that cannot be the reason why a hello_world does not work and why I
Show us your "hello_world" code. Does it actually open "/dev/console" ?
do not see the sys_write() syscall being called at all. Btw, init on my
other rootfs is busybox init. I suppose I should always see someting
useful when init is starting.
Why do you assume that?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Though a program be but three lines long,
someday it will have to be maintained."
- The Tao of Programming
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
On Tue, Jun 10, 2003 at 06:52:51PM +0200, Wolfgang Denk wrote:
Show us your "hello_world" code. Does it actually open "/dev/console" ?
Attached - source + compiled binary (this one is dynamically linked).
Could you verify that this hello world works with your hardware when
copied to /sbin/init? I would assume it prints out the text and then the
kernel panics because of the return.
quoted
do not see the sys_write() syscall being called at all. Btw, init on my
other rootfs is busybox init. I suppose I should always see someting
useful when init is starting.
Why do you assume that?
Normally init makes some output, something like
message(MAYBE_CONSOLE | LOG, "init started: %s", bb_msg_full_version);
from busybox-init.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Braunschweiger Str. 79, 31134 Hildesheim, Germany
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4