Solving U-boot problem | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
To change boot parameters in U-boot: #setenv bootargs <bootparams> To save the new parameters in flash: #saveenv For example, the kernel command line I use is this: "mem=32M console=tty0 console=ttyS0,115200 initrd=0x10800000,2M root=/dev/ram0 rw" So, to set this, I use: #setenv bootargs mem=32M console=tty0 console=ttyS0,115200 initrd=0x10800000,2M root=/dev/ram0 rw #saveenv To verify the list of parameters, type: #printenv To verify only the boot parameters, type: #printenv bootargs Hope this helps. Original message: Message: 8 Date: Wed, 10 Mar 2004 00:45:00 +0800 From: "Munro Biswal" <munro.biswal@xxxxxxxxxxxxxxxx> Subject: RE: Kernel memory detection problem To: "Russell King - ARM Linux" <linux@xxxxxxxxxxxxxxxx> Cc: linux-arm@xxxxxxxxxxxxxxxxxxxxxx Message-ID: <B2221ABD2C9465418B330C8EB8A8F8262E72C9@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="utf-8" Hi, Russel, How exactly does the bootloader take in the boot parameters. Iam using uboot as the bootloader. Is it through the tagged list on the uboot side i.e the file include/asm/setup.h which i need to modify. tried changing the order of the tagged list putting "ATAG_NONE" at the end of the union .But my uboot dosent boot up in that case , i get a blank screen. Regards, MUNRO. ------------------------------------------------------------------- Subscription options: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm FAQ/Etiquette: http://www.arm.linux.org.uk/armlinux/mailinglists.php
[Site Home] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux ARM Kernel] [Linux MIPS] [ECOS] [Tools] [DDR & Rambus] [Monitors]