From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Initial kernel command string (Was: Generating elf kernel ?)
Date: Mon, 20 Sep 2010 16:10:58 +0800 [thread overview]
Message-ID: <4C971712.2020901@windriver.com> (raw)
In-Reply-To: <201009200921.09800.dargaud@lpsc.in2p3.fr>
Guillaume Dargaud wrote:
>> I think you should modify the bootargs on your dts.
>> ------
>> chosen {
>> bootargs = "console=ttyS0 root=/dev/ram";
>> linux,stdout-path = "/plb@0/serial@83e00000";
>> } ;
>
> Thanks, that worked great, I now have a fully bootable not only kernel, but
> full OS as well.
Sounds good :)
>
>>> Also my previous kernel would wait for 2 seconds at the beginning to
>>> allow me to change the initial command string via the serial port, but
>>> now it just runs right through. How can I enable this option ?
>> It's possible on PowerPC kernel :)
>>
>> You can take a look at the file, arch/powerpc/boot/main.c.
>> ------
>> static void prep_cmdline(void *chosen)
>> {
>> if (cmdline[0] == '\0')
>> getprop(chosen, "bootargs", cmdline, COMMAND_LINE_SIZE-1);
>>
>> printf("\n\rLinux/PowerPC load: %s", cmdline);
>> /* If possible, edit the command line */
>> if (console_ops.edit_cmdline)
>> console_ops.edit_cmdline(cmdline, COMMAND_LINE_SIZE);
>> printf("\n\r");
>> .......
>>
>>
>> So you have to define one function, console_ops.edit_cmdline -->
>> serial_edit_cmdline. Or you can try bind this to your boot console ops
>> directly. Please refer to the file, arch/powerpc/boot/serial.c.
>
> So I forced
> console_ops.edit_cmdline = serial_edit_cmdline;
> in serial.c, bu that didn't do the trick...
Where are/how do your way implement? Can you paste your code sections here?
If I remember ML405 properly the serial port should be compliant to ns16550. So
I think the sub-functions, putc()/getc()/tstc(), should be from the file,
arch/powerpc/boot/ns16550.c. If so it's fine.
Maybe you can add some extra printf() into the function, serial_edit_cmdline, to
track this in detail.
Cheers
Tiejun
next prev parent reply other threads:[~2010-09-20 8:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 8:53 Generating elf kernel ? Guillaume Dargaud
2010-09-14 10:08 ` tiejun.chen
2010-09-14 11:27 ` Guillaume Dargaud
2010-09-14 12:57 ` Baurzhan Ismagulov
2010-09-15 8:07 ` Guillaume Dargaud
2010-09-15 8:27 ` tiejun.chen
2010-09-15 14:51 ` Guillaume Dargaud
2010-09-16 3:02 ` tiejun.chen
2010-09-16 7:25 ` Guillaume Dargaud
2010-09-16 7:51 ` tiejun.chen
2010-09-17 9:27 ` Initial kernel command string (Was: Generating elf kernel ?) Guillaume Dargaud
2010-09-17 9:46 ` tiejun.chen
2010-09-20 7:21 ` Guillaume Dargaud
2010-09-20 8:10 ` tiejun.chen [this message]
2010-09-15 16:49 ` Generating elf kernel ? Scott Wood
2010-09-16 2:37 ` tiejun.chen
2010-09-16 17:09 ` Scott Wood
2010-09-17 1:58 ` tiejun.chen
2010-09-17 17:44 ` Scott Wood
2010-09-19 1:40 ` tiejun.chen
2010-09-20 15:43 ` Scott Wood
2010-09-21 1:00 ` Chen, Tiejun
2010-09-21 17:00 ` Scott Wood
2010-09-21 23:35 ` Chen, Tiejun
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=4C971712.2020901@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=dargaud@lpsc.in2p3.fr \
--cc=linuxppc-dev@lists.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;
as well as URLs for NNTP newsgroup(s).