From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Hodaszi Date: Tue, 23 Jun 2009 14:45:35 +0200 Subject: [U-Boot] Mips, U-Boot and ramdisk In-Reply-To: <4A40B0C1.3010506@sch.bme.hu> References: <4A3F9B62.5070107@sch.bme.hu> <4A40A63F.6010100@bubblegen.co.uk> <4A40B0C1.3010506@sch.bme.hu> Message-ID: <4A40CE6F.4000700@sch.bme.hu> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de >> This is arch specific in U-Boot but I'd also check that your MIPS kernel has >> support for a) correctly parsing the U-Boot environment provided to it and b) >> providing the required data to other parts of the kernel for utilisation of the >> ram disk, eg initrd_start / initrd_end as an example. >> >> If you're struggling to pass other args to the kernel then it sounds like there >> is more of a fundamental issue somewhere, though. Maybe just double check >> Documentation/kernel-parameters.txt to make sure you're passing syntax in a form >> that the kernel will recognise? >> >> Hope that helps. >> >> Cheers, >> -- Matt >> >> > I don't know yet, if it can or can't pass other arguments. I check only > that one so far. But the command line parameters work well, I tried the > kgdb, the ramdisk, etc. It's only a problem with this environment > variable. But I'm just debugging... > > > I checked, and it seems, that the kernel doesn't check anywhere nor the initrd_start and initrd_size, nor the flash_start and flash_size environment parameters, but checks the memsize and ethaddr parameters. At least I couldn't find it. Is it true, or I'm blind? Did anybody use this U-Boot feature? Best regards, Robert Hodaszi