From: "Rajat Jain" <rajat.noida.india@gmail.com>
To: Thierry Reding <thierry@gilfi.de>, Thiemo Seufer <ths@networkno.de>
Cc: kernelnewbies@nl.linux.org, newbie <linux-newbie@vger.kernel.org>,
linux-mips@linux-mips.org
Subject: Re: How does boot loader tell the kernel, the location of initrd?
Date: Fri, 16 Mar 2007 10:42:30 +0530 [thread overview]
Message-ID: <b115cb5f0703152212y2e7bd01chf1e7fa7bf8d2f08c@mail.gmail.com> (raw)
In-Reply-To: <20070315161718.GB16545@ba.sec>
> > I am experimenting with initrd and my initrd fails to mount. My
> > bootloader (U-BOOT) coorectly loads the initrd into RAM as I can see.
> >
> > I am wondering how does the kernel get to know the address at which
> > the initrd is loaded by boot loader? How does the boot loader
> > communicate this to the kernel?
> >
> > Any code references will be appreciated.
>
> Perhaps lib_mips/mips_linux.c in the U-Boot tree is what you are looking for.
> That code sets up environment parameters that are parsed by the Linux kernel
> later on (see rd_start_early() and friends in arch/mips/kernel/setup.c in the
> Linux tree).
Thanks! That is exactly what I was looking for. However, I noticed
that U-BOOT passes these parameters in environment variables, where as
Linux kernel expects them as command l ine arguments. It wasn't
working for me untill I made changes in U-BOOT to pass them in command
line arguments.
Why is this discrepancy in U-BOOT and the kernel? Are other people
working on the (linux+U-BOOT) combo making the changes that I did?
Thanks,,
Rajat
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2007-03-16 5:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 6:58 How does boot loader tell the kernel, the location of initrd? Rajat Jain
2007-03-15 8:26 ` Rajendra
[not found] ` <20070315161718.GB16545@ba.sec>
2007-03-16 5:12 ` Rajat Jain [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=b115cb5f0703152212y2e7bd01chf1e7fa7bf8d2f08c@mail.gmail.com \
--to=rajat.noida.india@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-newbie@vger.kernel.org \
--cc=thierry@gilfi.de \
--cc=ths@networkno.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox