All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hodaszi <mouse1@sch.bme.hu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Mips, U-Boot and ramdisk
Date: Tue, 23 Jun 2009 14:45:35 +0200	[thread overview]
Message-ID: <4A40CE6F.4000700@sch.bme.hu> (raw)
In-Reply-To: <4A40B0C1.3010506@sch.bme.hu>


>> 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

      reply	other threads:[~2009-06-23 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 14:55 [U-Boot] Mips, U-Boot and ramdisk Robert Hodaszi
2009-06-23  9:25 ` Detlev Zundel
2009-06-23 10:14   ` Robert Hodaszi
2009-06-23  9:54 ` Matthew Lear
2009-06-23 10:38   ` Robert Hodaszi
2009-06-23 12:45     ` Robert Hodaszi [this message]

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=4A40CE6F.4000700@sch.bme.hu \
    --to=mouse1@sch.bme.hu \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.