On 2008-09-22, Grant Edwards <[EMAIL PROTECTED]> wrote:
> On 2008-09-21, Grant Edwards <[EMAIL PROTECTED]> wrote:
>> On 2008-09-21, Grant Edwards <[EMAIL PROTECTED]> wrote:
>>
>>> Now I'm trying to figure out how to get a serial console
>>> enabled (for both the kernel and a shell once things are
>>> started up)...
>>
>> I'm a bit stumped.
>
> I've done everything I can think of, including adding a line to
> config_BSP() like this:
>
> strncpy(commandp, " console=/dev/ttyS0,115200 ", size);
Doh!
I added the above line in the wrong place. It was being
clobbered by a later
memset(commandp, 0, size);
After moving my strncpy() to the bottom of config_BSP(), I now
get nice kernel startup messages and a sash prompt on ttyS0.
Various userland application stuff is still broken, but I don't
really care about that at this point.
After looking at config_BSP() it's obvious that one can set
CONFIG_BOOTPARAM and CONFIG_BOOTPARAM_STRING to acheive the
same result. Modifying the kernel settings for those
parameters after choosing the target in "make menuconfig"
works.
What I can't quite figure out is how to make ttyS0 the default.
Setting CONFIG_BOOTPARAM and CONFIG_BOOTPARAM_STRING in
vendors/SnapGear/PRO/config.linux-2.4.x appears to have no
effect on the default values when a new configuration is
created from scratch.
--
Grant Edwards grante Yow! I'm having BEAUTIFUL
at THOUGHTS about the INSIPID
visi.com WIVES of smug and wealthy
CORPORATE LAWYERS ...
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
